Require plain English in Planner and Architect work

[taras]

Why

Planner and Architect outputs need to remain decision-complete without making readers translate dense planning or architecture language before they can understand the result.

What changes

Before:

• Both role contracts required exact decisions and evidence but did not state how clearly those results should be communicated.

After:

• Planner work leads with the user or system outcome, uses short familiar language, and still states exact files, contracts, ownership, failures, and evidence.
• Architect work leads with the practical result, explains necessary project terms where they first matter, and still states exact identities, ownership, failures, and evidence.

Review guide

Start with: .agents/planner.md

Then review:

1. .agents/architect.md
2. The unchanged responsibilities and review boundaries surrounding each new Language section

What must stay true

• Plain language does not weaken decision completeness or architecture precision.
• Planner and Architect permissions, responsibilities, evidence thresholds, and handoff contracts remain unchanged.
• Experimental AGENTS.md role launch wiring remains uncommitted and is not part of this PR.

How to verify it

• git diff --check origin/main...HEAD checks the complete patch for whitespace errors.
• deno task test --changed=origin/main reports that no runtime test modules are affected by these role-document changes.

Scope

Included

• Plain-English communication requirements for Planner and Architect work.

Intentionally unchanged

• AGENTS.md, including the local experimental launcher edits.
• Issue-writing guidance, product implementation, specifications, tests, dependencies, and generated artifacts.

Scope confirmation

• Every changed file supports the purpose described above.
• Unrelated cleanup and formatting changes are excluded.
• Generated or mechanical changes are clearly identified.
• The description matches the final diff and test results.

[github-actions]

PR #712: Require plain English in Planner and Architect work

2 files, +26 / -0

Scope

✅ PR scope looks good.

Structural

✅ No structural bloat detected.

Slop

✅ Slop indicators look low.

Static Analysis

✅ Oxlint found no issues.

Correctness

No extraneous code patterns detected.