[osovv]

Why the change

Four system-prompt sections (working_state, assumption_discipline, editing_workflow, reroute_on_evidence) reached the vv-controller model twice with conflicting wordings — once from the bundled template and once from the plugin's universal injection — because the plugin's includes-based dedup guard cannot collapse differently-worded copies.

Special things to note

• The universal injection versions (September 2026 calibration) win; the template's editing_workflow section was the only one with unique content, and its two lines (read the local contract before editing; stop on unclear or unexpectedly broad edits) were merged into the injected section before the template copy was removed.
• Contract tests on both sides were updated deliberately: template-side assertions now pin the dedup contract (the four tags must be absent from the template), and the plugin side gained an assembled template-plus-injection test that counts each tag exactly once. No wording checks were weakened — the injected editing_workflow wording assertions keep their pinned lines and gain the two merged ones.
• GRACE graph and verification entries (M-CLI-MANAGED-AGENTS, M-PLUGIN-SYSTEM-CONTEXT-INJECTION, V-M-*) were resynced to describe the single-source split; grace lint is clean and grace status reports only the expected unexplained-drift listing of the touched files.

Change outline

  templates/agents/vv-controller.md
- <working_state>…</working_state>        (template copy removed)
- <assumption_discipline>…</assumption_discipline>
- <editing_workflow>…</editing_workflow>
- <reroute_on_evidence>…</reroute_on_evidence>

  src/plugins/system-context-injection/index.ts   UNIVERSAL_PRIMARY_SYSTEM_CONTEXTS
  <editing_workflow>
+   Before editing, understand the relevant local contract, nearby tests, and surrounding code.
    When editing files, prefer the `edit` tool over shell-based rewrites when it is available.
    Read the file first, then use exact `line#hash#anchor` refs from the latest `read` output when present.
    Reserve `bash` for tests, builds, git, and other non-file-edit commands.
+   If direct editing reveals unclear behavior or unexpectedly broad scope, stop and reroute instead of continuing speculatively.
  </editing_workflow>

  src/plugins/system-context-injection.integration.test.ts
+ test("assembled vv-controller template plus injection keeps each universal section once")
+   // each of the four tags: exactly 1 occurrence in template + injection

Module contracts/CHANGE_SUMMARY of both sides and the GRACE graph/verification entries were synced in the same change.