You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
IntegrityCheck: blocking findings that come from the payload itself (hook count in HookSystem.md, a prose budget of 0, optional-file references) #2825
Each finding below traces to payload files rather than to a local edit. How many of them a given install shows depends on its state, as noted per item.
1. dispatcher-parity: the hook count in HookSystem.md.LIFEOS/DOCUMENTATION/Hooks/HookSystem.md says "59 .hook.ts" at :1447 and :1555 (:1555 adds "Public releases ship 49"). The payload's hooks/ holds 50*.hook.ts. The check compares the doc's number with the live count and raises one blocking finding, so a fresh install reads red until someone edits a payload doc. A release-dependent count fits poorly in a hand-written doc: the doc could cite the check, or the release step could write the number.
2. prose-in-code: a budget of 0 against 32 payload hits. On the payload, ProseInCode.ts finds 32 doctrine-prose lines in source comments, and the budget is 0. The result is one blocking finding on every install. Either clear the lines before release, or ship the budget at the payload's own count.
3. references: optional runtime files reported as missing. These payload lines point at files that exist only once a feature is in use:
CLAUDE.template.md:68 and LIFEOS/DOCUMENTATION/LifeosSystemArchitecture.md:608 point at USER/LOCATION/current.json, which exists only after Location is set up (LIFEOS/LOCATION/Here.ts handles its absence).
LIFEOS/DOCUMENTATION/Tools/Tools.md:829 points at ~/.claude/.mcp.json, which the same line calls "runtime config; not shipped".
The references check reports each one as a blocking missing. It could skip paths that a doc marks as optional or not shipped, or the docs could write them in a form the check already skips.
Suggested direction (yours to pick). Before a release, run IntegrityCheck on a clean install of the payload, with and without the optional features, and treat anything blocking there as a release bug.
Activity