Private
Public Access
docs(harness): Phase 2 makes .warm.md duplicates not in-place edits (per user 2026-07-02)
The 'update role prompts' step in Phase 2 was specified as in-place edits to the 5 .opencode/agents/*.md role prompts. The user clarified 2026-07-02 that this should be making duplicates with a .warm.md suffix so the originals stay as an explicit rollback target. Changed: - spec.md: added a USER DIRECTIVE block above 'The role-prompt bootstrap' section explaining the .warm.md duplicate convention. - plan.md: the Phase 2 preamble references the spec directive; Steps 2.3-2.7 rewritten as 'Create duplicate <name>.warm.md (do NOT modify the original)'. Output paths now include .warm.md suffix. - dispatch_tier3_phase1.md: appended a USER DIRECTIVE section at the end + a NEVER-run-chronology-regenerate note (the script corrupts Unicode, per the 2026-07-02 revert ofbfebb718). Phase 1 work (51 v1.md directives + 11 commits ee36eaed..8162f629) is unaffected. Master is at068411ee(after the chronology revert). This commit brings master to this point.
This commit is contained in:
@@ -85,6 +85,8 @@ tested yet. This preset is the control group for future experiments.
|
||||
|
||||
### The role-prompt bootstrap
|
||||
|
||||
> **USER DIRECTIVE (2026-07-02):** Phase 2's "update role prompts" step is **making duplicates** of the role prompts (e.g., `.opencode/agents/tier3-worker.md.bak`), NOT modifying the originals in place. The duplicates use the `warm with:` bootstrap. The originals stay untouched as the fallback path. This means if a role-prompt regression surfaces, the user can `mv .bak .md` to restore. Do NOT modify the original `.md` role prompts.
|
||||
|
||||
The 5 role prompts (`.opencode/agents/tier1-orchestrator.md`, `tier2-tech-lead.md`, `tier3-worker.md`, `tier4-qa.md`, and `conductor/tier2/agents/tier2-autonomous.md`) have a hardcoded "MANDATORY: Pre-Action Required Reading" section listing ~11 specific files. This is replaced with a single `warm with:` directive.
|
||||
|
||||
```markdown
|
||||
|
||||
Reference in New Issue
Block a user