[bug] skill-usewhen-index.json is never rebuilt (loadIndex has no caller)

Open Beginner friendly
#2,808 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
devtools

Research direction

Start with the writer named in the report: AlgorithmNudge.hook.ts, which runs its index rebuild only via --rebuild-index, and the loadIndex() function that spawns it. Confirm no caller of loadIndex() exists, then check LIFEOS/TOOLS/derived-artifacts.json for the 24-hour max-age entry on MEMORY/STATE/skill-usewhen-index.json. Done means the index is refreshed on the expected schedule, or the dead writer and manifest entry are removed, and the derived-freshness check passes on day two.

Written by the indexing model from the issue text.

Description

What happened

skill-usewhen-index.json is never rebuilt (loadIndex has no caller)

Summary

LifeOS 8.761.0. LIFEOS/TOOLS/derived-artifacts.json declares MEMORY/STATE/skill-usewhen-index.json with a maximum age of 24 hours and the note that it is refreshed per turn. Its only writer is AlgorithmNudge.hook.ts --rebuild-index, which is started only from loadIndex(). Nothing calls loadIndex() (a search finds the definition only), and nothing reads the index.

Seen: the index is built once at install and never again. From the second day the integrity lane derived-freshness reports "MEMORY/STATE/skill-usewhen-index.json: age ... exceeds declared max 24h" as a blocking finding.

Suggested fix: call loadIndex() again where the index is needed, or drop the manifest entry and the dead writer.

Details

  • Kind: bug
  • LifeOS version: 8.761.0

Filed with the LifeOS /feedback command. The reporter approved this exact text before it was sent; paths, secrets and personal details were stripped locally.

Dominant language
TypeScript
Stars
19.8k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from danielmiessler/LifeOS

All issues in danielmiessler/LifeOS

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.