feat(framework+cli): fw-4.15.0 / cli-3.13.2 — inject AGENTS.md universal standard

[montfort]

Summary

Adds AGENTS.md as a first-class injection target. AGENTS.md is the open standard for AI coding agents, donated to the Agentic AI Foundation (Linux Foundation, December 2025) and read by Claude Code, OpenAI Codex CLI, Cursor, Aider, Devin, Sourcegraph Amp, Google Jules, Zed AI, Continue, Roo Code, Factory Droids, GitHub Copilot, Gemini CLI, Windsurf, Amazon Q and others.

Before fw-4.15.0, StrayMark injected directives only into platform-specific files (CLAUDE.md, GEMINI.md, .github/copilot-instructions.md, .cursorrules, .cursor/rules/straymark.md); adopters using any of the other 15+ CLIs that read AGENTS.md had to copy directives by hand. From this release, straymark init and straymark update-framework keep AGENTS.md in sync with STRAYMARK.md automatically.

Why this matters

AGENTS.md consolidates a fragmented configuration surface that emerged during 2024-2026 as each CLI invented its own directive format. By injecting there from day 1 of the adopter's project, StrayMark covers every current and future CLI that adopts the standard without per-CLI bumps.

What changed

Framework (fw-4.15.0)

• New template dist/dist-templates/directives/AGENTS.md — reference shape (pointer to STRAYMARK.md + minimum-viable body for agents that cannot follow relative links).
• New injection entry in dist/dist-manifest.yml, placed first as the universal entry point.
• STRAYMARK.md § Directive Injection Markers documents AGENTS.md coexistence with CLI-specific files.
• Governance footers bumped to v4.15.0 across EN + i18n/es + i18n/zh-CN (QUICK-REFERENCE, AGENT-RULES, DOCUMENTATION-POLICY, C4-DIAGRAM-GUIDE, FOLLOW-UPS-BACKLOG-PATTERN).
• README and ADOPTION-GUIDE (EN + ES + zh-CN) list AGENTS.md as the universal entry point with the full reader-CLI inventory.

CLI (cli-3.13.2)

• AGENTS.md in LEGACY_DIRECTIVE_TARGETS (cli/src/commands/remove.rs:13). The data-driven cleanup path (manifest-aware) already handles the common case; this defensive extension covers the edge case where .straymark/dist-manifest.yml is missing or fails to parse, so remove doesn't leave AGENTS.md orphaned. Follows the existing convention of keeping LEGACY_DIRECTIVE_TARGETS in sync with the manifest's injections:.
• Cargo.toml + Cargo.lock bumped to 3.13.2. Version tables and example outputs in README + CLI-REFERENCE (EN + ES + zh-CN) follow.

Tests

Three new integration tests in cli/tests/inject_test.rs:

• test_agents_md_template_has_markers — verifies the shipped template's marker shape and STRAYMARK.md pointer.
• test_manifest_declares_agents_md_injection — pins the manifest entry so init/update/remove all pick AGENTS.md via the data-driven path.
• test_agents_md_coexists_with_preexisting_file — append-when-no-markers behavior against the very common case of an adopter who already maintains an AGENTS.md.

Design notes

Reference shape, not embed. Parallel to CLAUDE.md / GEMINI.md: marker block points to STRAYMARK.md, with a minimum-viable body below for readers that cannot follow relative links. Rationale: the AGENTS.md convention emphasizes conciseness; .cursorrules already embeds the full content for the one CLI that needs it.

Position: root of the repo. AGENTS.md has a "nearest in the tree" reading convention, so root coverage is enough.

Coexistence with pre-existing AGENTS.md. Many adopters already maintain a hand-written AGENTS.md. The existing inject_directive flow appends the marker block when no markers are present — pre-existing custom content is preserved. Test test_agents_md_coexists_with_preexisting_file pins this behavior.

Why bump CLI to 3.13.2. The remove.rs change modifies the released binary's behavior in the edge case where the local manifest is missing. Per the project's versioning policy, any behavior change in the binary warrants a matching CLI bump. The framework manifest path covers the common case; the CLI bump covers the legacy fallback. Both framework and CLI tags should be pushed together once merged.

Test plan

• cargo test --quiet — all suites pass (including the three new AGENTS.md tests)
• cargo check — Cargo.lock reflects 3.13.2
• Manifest declares AGENTS.md injection
• Template marker shape verified
• Append-when-no-markers behavior pinned
• After merge: tag both fw-4.15.0 and cli-3.13.2 on main HEAD and push together (git push origin fw-4.15.0 cli-3.13.2).
• Post-release: run straymark update in a pilot adopter; confirm AGENTS.md lands at root with markers and the new CLI binary is in place.
• Cross-CLI smoke: open the pilot repo in Claude Code, Cursor, and Codex CLI; confirm each picks up the directives via AGENTS.md.

Risks

#	Risk	Mitigation
1	AGENTS.md pre-existing with custom content in adopter repos	Inject appends when no markers present (test-pinned).
2	.gitignore excluding AGENTS.md (rare but possible)	Documented in the CHANGELOG adopter guidance.
3	Confusion: does AGENTS.md replace CLAUDE.md?	No — both coexist (same source via STRAYMARK.md, different identity strings). STRAYMARK.md and CHANGELOG both make this explicit.
4	Adopter on cli-3.13.1 with fw-4.15.0 and corrupted manifest runs remove	Edge case; cli-3.13.2 fixes it. Common path (manifest present) works on both binaries.

Related

Closes the position raised in the project's "Estado del arte" analysis (R5: "el sitio no reconoce AGENTS.md como estándar dominante"). The website narrative for fw-4.15.0 can now claim multi-CLI coverage as a first-class feature, not an aspiration.