feat(framework): fw-4.17.0 — emergent-observation design meta-pattern

[montfort]

Summary

• Names a design property of StrayMark that was already present but unnamed: formal cross-referencing (frontmatter linkage, canonical sections, stable IDs) composed with cultural permission to surface beyond the asked task produces agents that, while reading only framework documentation, surface dissonance between canonical sources. This composition produced the Sentinel observation that crystallized as CHARTER-CHAIN-EVOLUTION.md Pattern 1 in fw-4.16.0 (Issue RFC/discussion: spec-refresh discipline in SPECKIT-CHARTER-BRIDGE — empirical staleness across multi-Charter execution #150 → RFC: Pre-declare SpecKit refresh + post-close Batch 7.4 — two patterns surfaced in Sentinel CHARTER-18 #156). Naming the meta protects it under framework evolution.
• Adds dist/.straymark/00-governance/EMERGENT-OBSERVATION-DESIGN.md (EN + ES + zh-CN) with the meta property, an empirical case (RFC/discussion: spec-refresh discipline in SPECKIT-CHARTER-BRIDGE — empirical staleness across multi-Charter execution #150 → RFC: Pre-declare SpecKit refresh + post-close Batch 7.4 — two patterns surfaced in Sentinel CHARTER-18 #156), a pyramid of existing applications (Pattern 1, Pattern 2, charter drift, follow-ups backlog drift, TDE-vs-`R` escalation, external audit checkpoint), anti-patterns, and four open application axes (MCARD ↔ deployed model, SBOM ↔ lockfiles, ADR ↔ contradicting implementation, Constitution Check ↔ framework bump) for future N=1 adopter validation.
• Adds PRINCIPLES.md §8 — Cross-Source Dissonance Surfacing (EN + ES + zh-CN) as the condensed cultural rule.
• Expands AGENT-RULES.md §6 "Be Proactive" (EN + ES + zh-CN) with a sub-bullet citing Principle fix: remove redundant header from framework update output #8 + concrete dissonance examples to watch for.
• Cross-links added in CHARTER-CHAIN-EVOLUTION.md (`## Related` — 3 langs), SPECKIT-CHARTER-BRIDGE.md (`## See also` / `## Ver también` / `## 另请参阅` — 3 langs), FOLLOW-UPS-BACKLOG-PATTERN.md (new `## Related` section — 3 langs), STRAYMARK.md §11 (new row in "When to Load Additional Documents" table — EN only; no i18n exists for STRAYMARK.md).
• Governance footers bumped to `fw-4.17.0` (PRINCIPLES, AGENT-RULES, DOCUMENTATION-POLICY, C4-DIAGRAM-GUIDE, QUICK-REFERENCE, CHARTER-CHAIN-EVOLUTION, FOLLOW-UPS-BACKLOG-PATTERN — all 3 languages — plus root dist/.straymark/QUICK-REFERENCE.md). PRINCIPLES migrated from legacy `v1.0.0` to `fw-X.Y.Z` convention.
• Versioning tables in `README.md` + i18n and `docs/adopters/CLI-REFERENCE.md` + i18n bumped to `fw-4.17.0`. No CLI bump — `cli-3.14.1` from the `fw-4.16.2` cycle remains current.

Motivation

Issue #150 → #156 documented how a Sentinel agent surfaced spec-drift across 7 Charters without trigger and without operator request. The pattern was empirically reproducible. fw-4.16.0 codified one application of this behaviour (Pattern 1: pre-declare SpecKit refresh). This PR codifies the meta: the property of the framework's documentation aparatus that produces emergent observations across multiple application axes — so that:

1. Framework evolution preserves the property deliberately (anti-patterns section calls out what regresses it).
2. Adopters have vocabulary to recognize the pattern when they experience it.
3. Future application axes (MCARD/SBOM/ADR/Constitution) can be canonicalized via the same upstream-acceptance flow.

The N=1-domain caveat (Principle #12) is declared explicitly in the new doc. Graduation to v1 awaits a second domain validating an additional axis.

Test plan

• Cross-link integrity: `grep -rln EMERGENT-OBSERVATION-DESIGN dist/ docs/ CHANGELOG.md` returns all 20 expected files (3 new + 17 cross-linkers, including STRAYMARK.md and CHANGELOG.md).
• i18n header-count parity: EN/ES/zh-CN of the new doc all have 14 headers (`grep -c '^##\|^# '`).
• Footer fw-4.17.0 present in all three language variants of the new doc and in all bumped governance footers.
• No leftover `v4.16.2` / `v4.15.0` references in governance docs (the lone `fw-4.16.2 / cli-3.14.1` mention in `STRAYMARK.md` line 470 is historical/provenance text and intentional).
• `dist/dist-manifest.yml` reads `version: "4.17.0"` — required by `release-framework.yml` tag-version gate.
• Manual reading pass of EN canonical doc as if onboarding fresh — confirms doc explains why the emergent behaviour arises and what to preserve.
• Post-merge: tag `fw-4.17.0` on `main` HEAD and push (CI does the rest).
• Post-merge: open follow-up RFC issue tracking the four open application axes (MCARD/SBOM/ADR/Constitution) with N=1-domain caveat per Principle feat: add devtrail repair command to restore broken structure #12.

🤖 Generated with Claude Code