IntegrityCheck on an installed 8.761.0: identity, references and services-doc findings a user cannot clear
メンテナーはふだん 5 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 34/100
- issue の種類
- バグ
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- bun, typescript
- 領域
- devtools, testing-qa
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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.
- 主要言語
- TypeScript
- スター
- 19.9k
- フォーク
- 2.5k
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
danielmiessler/LifeOS のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
danielmiessler/LifeOS#2894 ·
メンテナーはふだん 5 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
danielmiessler/LifeOS#2891 ·
メンテナーはふだん 5 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
danielmiessler/LifeOS#2888 ·
メンテナーはふだん 5 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
danielmiessler/LifeOS#2886 ·
メンテナーはふだん 5 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 68/100
danielmiessler/LifeOS#2848 ·
メンテナーはふだん 5 日以内に返信
danielmiessler/LifeOS の issue をすべて見る
似ている issue
-
ready-for-agent
難易度 1/5 1時間未満 初心者へのやさしさ 86/100
LucasSantana-Dev/Lucky#3257 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
XiaomiMiMo/MiMo-Code#2849 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
enhancement frontend good first issue help wanted testing-infrastructure
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 2 日以内に返信
-
enhancement follow-up
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
obsidian-tasks-group/obsidian-tasks#4155 ·
メンテナーはふだん 1 日以内に返信