Skip to content

feat: add devtrail repair command to restore broken structure#12

Merged
montfort merged 1 commit intomainfrom
feat/repair-command
Mar 23, 2026
Merged

feat: add devtrail repair command to restore broken structure#12
montfort merged 1 commit intomainfrom
feat/repair-command

Conversation

@montfort
Copy link
Copy Markdown
Contributor

Summary

  • Add devtrail repair command that detects and fixes missing directories and framework files
  • Restores missing directories with .gitkeep (no download needed)
  • Downloads framework release once only if files need restoration (templates, governance docs, config)
  • Re-injects directives if DEVTRAIL.md is missing
  • Recalculates checksums after repair
  • Never touches user-generated documents
  • Reports "healthy" if nothing needs fixing

Test plan

  • devtrail repair on healthy project shows "nothing to repair"
  • Delete a directory (e.g., templates/) → repair restores it
  • Delete config.yml → repair downloads and restores it
  • User documents are never modified or deleted
  • cargo test passes all 26 tests

🤖 Generated with Claude Code

Add a repair command that detects and fixes missing directories and
framework files in a DevTrail installation without affecting user documents.

- Checks for missing directories and restores them with .gitkeep
- Downloads framework release only once if files need restoration
- Restores missing templates, governance docs, config, and manifest
- Re-injects directives if DEVTRAIL.md is missing
- Recalculates checksums after repair
- Reports "healthy" if nothing needs fixing

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@montfort montfort merged commit f1bb1e6 into main Mar 23, 2026
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Mar 23, 2026

CLA assistant check
All committers have signed the CLA.

montfort added a commit that referenced this pull request May 2, 2026
Editorial-only pass on Propuesta/devtrail-design-principles.md to remove
internal-language phrases that confuse readers who don't know Sentinel
(the project that produced the empirical evidence). All decisions and
commitments preserved; only language generalized.

Specific changes:
- Version metadata now names the editorial pass and dates it.
- v0.2 anotaciones intro: glosses Sentinel as "un sistema Go backend"
  on first mention, drops references to /plan-audit and PLAN-NN that
  cold readers can't anchor to anything.
- Principle #6 anotación (virtud-vs-ceremonia): replaces specific
  artifact IDs (AILOG-020, AILOG-022, PLAN-05.telemetry.yaml) with
  abstracted descriptions of the empirical findings. The decisions
  about what counts as virtud vs ceremonia stay identical.
- Principle #9 anotación (bash before framework): drops the script
  filename and AILOG ref, keeps the ~145-line metric and the
  three-property justification (zero-build, no deps, in-situ
  inspection).
- Principle #12 anotación (N≥3 spirit): "Sentinel es un solo
  proyecto..." → "La evidencia empírica disponible proviene de un
  solo proyecto adoptante..."; specific scores (9.25/9.5) generalized
  to "scores similares"; supuesto #4 named as "supuesto de
  aprobaciones condicionales" instead of by number alone.
- Meta-meta paragraph: drops Sentinel-specific framing while keeping
  the auto-evolución insight intact.

Prerequisite for D4 of the README repositioning plan: link the design
principles from the public README. Cold readers (a developer landing
on GitHub, not someone who read all the propuesta docs) need to grasp
each principle without first decoding internal artifacts.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants