[bug] skill-usewhen-index.json is never rebuilt (loadIndex has no caller)
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from danielmiessler/LifeOS
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
danielmiessler/LifeOS#2830 ·
Maintainers usually reply within 6 days
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
danielmiessler/LifeOS#2824 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
danielmiessler/LifeOS#2822 ·
Maintainers usually reply within 6 days
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
danielmiessler/LifeOS#2818 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
danielmiessler/LifeOS#2817 ·
Maintainers usually reply within 6 days
All issues in danielmiessler/LifeOS
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tintinweb/pi-subagents#459 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
freshframework/fresh#3920 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day