fix: consistent fw-/cli- version display across all commands#6
Merged
Conversation
Standardize version display across update, about, and status commands to always use the fw-X.Y.Z and cli-X.Y.Z format instead of mixing v-prefix and bare versions. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
|
2 tasks
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>
3 tasks
montfort
added a commit
that referenced
this pull request
May 3, 2026
…ks (#79) Adds the opt-in friction layer that runs `devtrail charter drift` before `git push`. Per principle #6 (cognitive discipline > raw productivity), the hook is virtuous when consented to — and never installed by default. Framework: - dist/.devtrail/hooks/pre-pr.sh: bash hook that scans docs/charters/*.md for status: in-progress, runs `devtrail charter drift <id> --range $UPSTREAM..HEAD` for each, exits non-zero if any reports unaccounted drift. AILOG-suppression in the CLI (PR 3) silences alerts on paths already documented as risks. Default upstream is origin/main; override via DEVTRAIL_UPSTREAM env var. Manual install: cp .devtrail/hooks/pre-pr.sh .git/hooks/pre-push. CLI: - New --hooks flag on `devtrail init` (default: false). After init succeeds, copies .devtrail/hooks/pre-pr.sh to .git/hooks/pre-push and makes it executable. Refuses to overwrite an existing pre-push hook (warns and continues without). Skips silently if the project isn't a git repository. Behavior tradeoffs: - The hook short-circuits when devtrail is not in PATH, so adopters who haven't installed the CLI yet can still push without friction. - The hook respects --no-verify (standard git escape hatch); the documented use case is "drift was intentional, captured in AILOG, push anyway". Tests: - 4 unit tests in init::hook_tests: * install_pre_pr_hook_copies_and_makes_executable (happy path) * install_pre_pr_hook_skips_when_not_a_git_repo * install_pre_pr_hook_refuses_to_overwrite_existing * install_pre_pr_hook_errors_when_source_missing 382/382 tests pass. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
fw-X.Y.Zandcli-X.Y.Zformatupdate,update-framework,update-cli,about, andstatuscommandsv-prefix formatting that was inconsistent with the split versioning schemeTest plan
cargo build— compiles cleancargo test— 25 tests passing"v{display patterns in CLI source (only instrip_tag_prefixfor legacy compat)🤖 Generated with Claude Code