IntegrityCheck on an installed 8.761.0: identity, references and services-doc findings a user cannot clear
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 34/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bun, typescript
- Domain
- devtools, testing-qa
Research direction
Start by reading the IntegrityCheck rules for code-data-boundary, references, services-doc, rule-duplication, skill-hygiene, and file enumeration, then inspect Services.ts and DOCUMENTATION/Services/BackgroundServices.md. Reproduce the reported findings against an installed 8.761.0 payload and check how optional files and folders are handled. Done means untouched installs no longer receive blocking findings for these reported conditions, while release checks still catch real problems.
Written by the indexing model from the issue text.
Description
Version: LifeOS 8.761.0, Claude Code 2.1.322, macOS, in-place update from 7.40.4. #2683 covers three gates; these are the rest that stay red on files the install did not edit.
1. code-data-boundary [identity-in-code]: 78 findings
"identity term in code is not rewritten by the release sanitizer". The names are there because the updater's identity rendering wrote them into the payload's placeholders. The check guards the maintainer's release cut; an install with no release-rewrites file has no release to guard. The same check also blocks on the install's own files: a user who dates decisions in comments ("2026-11-08, : (a)") gets one blocking finding per such file, though nothing on the install ships. Suggest: run it only where the release-rewrites file exists, or report it as info there.
2. references: 40 doc pointers to files the payload does not ship
Beyond the backup-folder ones in #2683, shipped docs name maintainer-only or never-shipped files. Most-referenced: hooks/ULWorkSync.hook.ts, test/harness.ts, hooks/herdr-agent-state.sh, hooks/TabTitleComposition.test.ts, bunfig.toml, RINGS/policy.ts by relative path, a few test files, skills/_VIDEO/Tools/CardMap.ts, and skills/Fabric/References/PortRanking.tsv, which Fabric's SKILL.md routes to twice but the payload does not ship. A second group names optional USER files a fresh install does not have yet (USER/LOCATION/current.json, also in CLAUDE.template.md; USER/HEALTH/current.json; several USER/CONFIG/*.json; ~/.claude/.mcp.json in Tools.md). Three shipped USER templates are red as installed (7 findings): USER/HEALTH/SHORTCUT_SETUP.md names the iCloud Shortcuts file it asks the user to create (LifeOS/health-export.json, a path outside the tree that the reference pattern reads as a tree path), USER/MEDIA/TasteProfile.md names a MediaTaste skill and Tools/Media.ts that the payload does not ship, and USER/SECURITY/README.md names hooks/Safety.hook.ts and its classifier, which 8.761.0 retired (the "(not in the public release)" note beside them does not exempt them). Suggest: drop or mark the maintainer-only references, ship or unroute PortRanking.tsv, and treat an absent OPTIONAL USER file as info.
3. services-doc: the #2160 table drift is back (19 findings)
#2160 (closed 2026-10-03) fixed the generated services table for 7.40.4. The 8.761.0 payload ships DOCUMENTATION/Services/BackgroundServices.md with a 9-row table while Services.ts registers 28 services, so the services-doc check reads 19 blocking on an untouched install. bun Services.ts doc prints the right table but does not write it. Suggest: regenerate the shipped table at release time, or give doc a --write.
4. Smaller
rule-duplication(2) andskill-hygiene(1) on payload files.- A scan error on an install with no
commands/folder: "file enumeration under /commands failed ... coverage is incomplete". An absent optional folder should not be a scan error.
- Dominant language
- TypeScript
- Stars
- 19.9k
- 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 67/100
danielmiessler/LifeOS#2894 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
danielmiessler/LifeOS#2891 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
danielmiessler/LifeOS#2888 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
danielmiessler/LifeOS#2886 ·
Maintainers usually reply within 5 days
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
danielmiessler/LifeOS#2848 ·
Maintainers usually reply within 5 days
All issues in danielmiessler/LifeOS
Similar issues
-
ready-for-agent
Difficulty 1/5 Under an hour Newbie friendliness 86/100
LucasSantana-Dev/Lucky#3257 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
XiaomiMiMo/MiMo-Code#2849 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement frontend good first issue help wanted testing-infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
obsidian-tasks-group/obsidian-tasks#4155 ·
Maintainers usually reply within 1 day