[protechnocrats]

Skill files:

• WORKFLOW.md, REPORTING.md, DIFFERENTIAL-TESTING.md, BENCHMARKING.md, and ALGORITHM-ARSENAL.md rewritten for clarity: shorter sentences, each instruction stated once, benchmarking bullets grouped by stage. No rule, step, threshold, example, or named section removed; every cross-reference in the skill still resolves.
• BEHAVIOR-TRAPS.md: numeric identity in hash keys, new size limits, and parameterized batched queries, from changes Opus made in rounds 8 and 9.
• WRITING-NEW-CODE.md: cache keys include user, tenant, and permissions; choices that take outside input must hold on hostile input.

Repository documents, now that evals/ and examples/ are gone:

• README: evidence rewritten from the Opus results, with links to the results and examples in the repository history; contributing section points to CONTRIBUTING.md.
• CONTRIBUTING, SECURITY, RELEASING, docs/ARCHITECTURE, PR template: references to evals/ removed; contributors write for coding-tier models.
• CHANGELOG [Unreleased]: what the next release actually contains, including a Removed section.
• docs/EVAL-PLAN.md: notes that the harness is to be rebuilt.
• CI: the token-budget, cross-reference, rule-evidence, and eval-script steps removed; docs/RULE-EVIDENCE.md removed.

What changes for someone using the skill

Checklist

• CHANGELOG.md [Unreleased] has a line for any change to what the skill does
• evals/token-budget.sh passes; any raised budget has its reason in the script
• Generic files stay language-neutral; mandatory rules are in skills/SKILL.md and the file that carries them out
• Behavior changes were measured before and after on a tuning fixture, or this says why not
• For eval changes: evals/selftest.sh passes (and --probes if a probe changed)