Skip to content

chore(straymark): rebrand DevTrail → StrayMark#10

Merged
montfort merged 3 commits into
mainfrom
chore/migrate-devtrail-to-straymark
May 19, 2026
Merged

chore(straymark): rebrand DevTrail → StrayMark#10
montfort merged 3 commits into
mainfrom
chore/migrate-devtrail-to-straymark

Conversation

@montfort
Copy link
Copy Markdown
Contributor

Summary

  • Mechanical rebrand of the documentation governance framework: CLI is now straymark (was devtrail), canonical folder is .straymark/ (was .devtrail/), and the shipped framework was refreshed to fw-4.17.0 via straymark repair.
  • Touches 212 files (+17,412 / −3,951) but no business logic: paths, comments, manifest entries, regenerated skills (.claude/skills/straymark-* ×11, .gemini/skills/straymark-* ×4), new templates (Charter, CAC, PIPIA, TC260RA, AILABEL), audit prompts, hooks, schemas, and zh-CN i18n. Append-only historical evidence (AILOGs/AIDECs/TES in .straymark/07-ai-audit/ and .straymark/04-testing/) is preserved verbatim with original DevTrail-era wording per governance principle.
  • Two commits, both chore(straymark): d4f90da does the git mv .devtrail .straymark + drops orphan dist files; 0e05de5 lands the framework regeneration, peripheral references (CLAUDE.md, GEMINI.md, .cursorrules, .github/copilot-instructions.md, Cargo.toml exclude, .github/workflows/docs-validation.yml STRAYMARK_DIR, .specify/memory/constitution.md, specs/001-code-metrics-library/spec.md), and deletes legacy DEVTRAIL.md + scripts/devtrail-{new,status}.sh (the straymark CLI now ships those subcommands natively).

Test plan

  • straymark status and straymark validate pass with 0 errors (local)
  • cargo build --all-features succeeds (local)
  • cargo test --all-features green — 177 tests (local)
  • No devtrail / DevTrail references remain outside .straymark/07-ai-audit/ and .straymark/04-testing/ (append-only history) (local)
  • CI docs-validation.yml green with new STRAYMARK_DIR env var and path filters
  • CI cargo build + cargo test green
  • Reviewer spot-checks: STRAYMARK.md is present and replaces DEVTRAIL.md; .devtrail/ no longer exists in tree; .cursorrules markers balanced (3-end → 2-begin/2-end fix)

Follow-up (not in this PR)

Stale framework-shipped content inside .straymark/00-governance/, .straymark/templates/, and .straymark/03-implementation/ will refresh on the next interactive straymark update-framework (currently blocks because config.yml is detected as user-modified after cosmetic rebrand).

🤖 Generated with Claude Code

montfort and others added 2 commits May 19, 2026 13:45
… files

Pre-repair checkpoint. Renames the canonical folder so `straymark repair`
operates on the right path, and removes the orphaned root-level
dist-manifest.yml / dist-templates/ that belonged to the legacy
DevTrail v4.1.1 schema.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Functional migration to the renamed framework (CLI now `straymark`,
canonical folder `.straymark/`). The `git mv .devtrail .straymark` was
done in the previous commit; this commit lands the rest:

* `straymark repair` ran successfully, downloaded fw-4.17.0, planted
  the new skills (`.claude/skills/straymark-*` ×11, `.gemini/skills/
  straymark-*` ×4), and restored `STRAYMARK.md`, new templates, audit
  prompts, hooks, charter scaffolding, and zh-CN i18n.
* Removed the legacy DevTrail surfaces that the new framework no
  longer ships: `DEVTRAIL.md`, `.cursor/rules/devtrail.md`,
  `.claude/skills/devtrail-*`, `.gemini/skills/devtrail-*`, and
  `.agent/workflows/devtrail-*.md` (deprecated surface).
* Updated all peripheral references: `CLAUDE.md`, `GEMINI.md`,
  `.cursorrules`, `.github/copilot-instructions.md`, `Cargo.toml`
  (`exclude` list), `.github/workflows/docs-validation.yml`
  (paths and `STRAYMARK_DIR` env var), `.specify/memory/constitution.md`,
  `specs/001-code-metrics-library/spec.md`.
* Updated `.straymark/config.yml`, `.straymark/dist-manifest.yml`, and
  `.straymark/.checksums.json` to rebrand cosmetic comments and fix the
  path prefix in tracked checksums.
* Deleted `scripts/devtrail-{new,status}.sh` — the `straymark` CLI now
  ships `straymark new` and `straymark status` natively.
* Fixed a pre-existing duplicated-marker bug in `.cursorrules` (had
  3 end markers vs 2 begin from a historical append-during-update).

Historical evidence preserved untouched: AILOGs/AIDECs/TES inside
`.straymark/07-ai-audit/` and `.straymark/04-testing/` keep their
original DevTrail-era wording per the append-only governance principle.

Verification:
* `straymark status` and `straymark validate` pass (0 errors).
* `cargo build --all-features` and `cargo test --all-features` green
  (177 tests).
* No `devtrail` / `DevTrail` references remain outside `.straymark/`.

Remaining stale content lives in framework-shipped files inside
`.straymark/00-governance/`, `.straymark/templates/`, and
`.straymark/03-implementation/` — these will be refreshed on the next
interactive `straymark update-framework` (currently blocks because
`config.yml` is detected as user-modified after the cosmetic rebrand).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented May 19, 2026

CLA assistant check
All committers have signed the CLA.

@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented May 19, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

The docs-validation workflow assumed every `.md` under `.straymark/` was an
instance document and enforced `[TYPE]-YYYY-MM-DD-NNN-*.md` naming on all of
them, with a narrow basename allowlist (PRINCIPLES, AGENT-RULES, TEMPLATE-*,
README, QUICK-REFERENCE, INDEX, GIT-BRANCHING-STRATEGY, DOCUMENTATION-POLICY).

After `straymark repair` brought in fw-4.17.0, the framework now ships ~70
additional reference/governance/template files (`CHARTER-CHAIN-EVOLUTION.md`,
`NIST-AI-RMF-*-GUIDE.md`, `PIPL-PIPIA-GUIDE.md`, `audit-prompt.md`,
`charter-template.md`, plus full zh-CN i18n trees) that don't and won't ever
match the instance-doc naming convention. PR #10 hit 71 naming errors as a
result.

Inverting the filter from name-based to path-based: only the directories that
hold instance documents (01-requirements, 02-design/decisions, 04-testing,
05-operations/{incidents,runbooks}, 06-evolution/technical-debt,
07-ai-audit/{agent-logs,decisions,ethical-reviews}, 08-security, 09-ai-models)
are validated for naming, frontmatter, risk_level/review_required cross-check,
ETH reference, and EU AI Act sections. Everything else under `.straymark/`
(framework-shipped material at any depth, including i18n) is skipped with
"⊘ Framework/reference" so future framework updates don't require maintaining
a basename allowlist.

Markdownlint, sensitive-info detection and internal-link verification continue
to run on every changed file, unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@montfort montfort merged commit 610a5bc into main May 19, 2026
5 checks passed
@montfort montfort deleted the chore/migrate-devtrail-to-straymark branch May 19, 2026 22:21
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.

1 participant