IntegrityCheck on an installed 8.761.0: identity, references and services-doc findings a user cannot clear
Los mantenedores suelen responder en 5 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 34/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- bun, typescript
- Área
- devtools, testing-qa
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 19.9k
- Forks
- 2.5k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de danielmiessler/LifeOS
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
danielmiessler/LifeOS#2894 ·
Los mantenedores suelen responder en 5 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
danielmiessler/LifeOS#2891 ·
Los mantenedores suelen responder en 5 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
danielmiessler/LifeOS#2888 ·
Los mantenedores suelen responder en 5 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
danielmiessler/LifeOS#2886 ·
Los mantenedores suelen responder en 5 días
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
danielmiessler/LifeOS#2848 ·
Los mantenedores suelen responder en 5 días
Todos los issues de danielmiessler/LifeOS
Issues similares
-
ready-for-agent
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
LucasSantana-Dev/Lucky#3257 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
XiaomiMiMo/MiMo-Code#2849 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
enhancement frontend good first issue help wanted testing-infrastructure
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 2 días
-
enhancement follow-up
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
obsidian-tasks-group/obsidian-tasks#4155 ·
Los mantenedores suelen responder en 1 día