Skip to content

refactor: rebrand DevTrail → StrayMark and migrate to fw-4.17.0#15

Merged
montfort merged 2 commits into
mainfrom
feat/straymark-rebrand
May 20, 2026
Merged

refactor: rebrand DevTrail → StrayMark and migrate to fw-4.17.0#15
montfort merged 2 commits into
mainfrom
feat/straymark-rebrand

Conversation

@montfort
Copy link
Copy Markdown
Contributor

Summary

  • Renames .devtrail/.straymark/ (preserves history via git mv) and migrates the governance framework from fw-4.1.0 to fw-4.17.0 via straymark repair + straymark update-framework.
  • Replaces all DEVTRAIL.md / devtrail-* skills, workflows, and rules with their STRAYMARK.md / straymark-* equivalents installed by the new framework; deletes the orphans.
  • Updates project-level references in CLAUDE.md, .cursorrules, Cargo.toml, GEMINI.md, .github/copilot-instructions.md, .specify/memory/constitution.md, and .specify/starter/IDEA.md to the new brand and paths.
  • No code in src/ is touched; build and tests are unaffected.
  • The new framework introduces Charters (bounded units of work with telemetry), GB 45438 AI labeling, multi-batch ledgers, external audit pipelines, and optional China regulatory scope (opt-in via .straymark/config.yml).
  • Adds AILOG-2026-05-19-001-rebrand-devtrail-to-straymark.md to the audit trail (risk_level: medium, review_required: true).

Why bundled with the framework upgrade?

straymark repair and straymark update-framework regenerate the new content in one pass, so a rebrand-only PR followed by an upgrade PR would mostly churn the same files twice. Commit history within the branch is still segmented:

  • 495c917 — refactor: rebrand + framework migration
  • 999a024 — docs: AILOG for the rebrand

What's preserved as-is

  • Historical AILOGs/TES/AIDEC/SBOM under .straymark/07-ai-audit/ and .straymark/04-testing/ keep their original "DevTrail" mentions — they are point-in-time records.
  • One explicit "formerly DevTrail" clarifier remains in .specify/starter/IDEA.md as origin-story context.

Test plan

  • cargo check — clean
  • cargo test — 29/29 passing
  • straymark status — Framework fw-4.17.0, CLI cli-3.15.0, all 17 structure items OK
  • straymark validate — 0 errors, 1 preexisting unrelated warning
  • grep -r "devtrail\|DevTrail" over tracked non-historical files — only the intentional "formerly DevTrail" remains
  • Reviewer: confirm the AILOG (review_required: true) is accurate and complete

🤖 Generated with Claude Code

montfort and others added 2 commits May 19, 2026 18:02
…17.0

DevTrail tool was renamed to StrayMark upstream. This change migrates the
repo from the DevTrail framework (fw-4.1.0) to the StrayMark framework
(fw-4.17.0), introducing Charters, GB 45438 labeling, multi-batch ledgers,
and audit pipelines. No code in src/ is touched.

- git mv .devtrail/ → .straymark/ (preserves history)
- straymark repair + straymark update-framework (190 files updated to fw-4.17.0)
- Delete orphans: DEVTRAIL.md, 7× devtrail-* skills in .claude/ and .gemini/,
  7× .agent/workflows/devtrail-*.md, .cursor/rules/devtrail.md
- Install new straymark-* skills/workflows/rules + STRAYMARK.md + AGENTS.md
- Update CLAUDE.md, .cursorrules, Cargo.toml, GEMINI.md,
  .github/copilot-instructions.md, .specify/memory/constitution.md,
  .specify/starter/IDEA.md to point at new paths and brand
- Discard untracked DevTrail residue (dist-manifest.yml, dist-templates/)
- Historical AILOGs/TES/AIDEC/SBOM in .straymark/07-ai-audit/ keep their
  DevTrail mentions intact (point-in-time records)

Validation: cargo check clean, cargo test 29/29 pass, straymark validate
0 errors, straymark status reports framework fw-4.17.0 OK.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Records the rebrand and fw-4.17.0 migration in the audit trail per
StrayMark governance rules (risk_level: medium, review_required: true).

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

cla-assistant Bot commented May 20, 2026

CLA assistant check
All committers have signed the CLA.

@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented May 20, 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.

@montfort montfort merged commit b58f05e into main May 20, 2026
9 of 13 checks passed
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