v0.1.1

What changed

• Added milestone contract as the hard goal anchor for Orchestrator / Project Manager.
• Added evaluation SOP as the hard evaluation anchor for Test Evaluator and Reviewer.
• Added Test Evaluator packet templates for evaluation SOP consumption and SOP calibration.
• Updated Reviewer standards to audit milestone-contract and evaluation-sop adherence across the workflow.
• Updated target-project bootstrap to generate milestone-contract.md and evaluation-sop.md.
• Updated README, PRD, HTML workflow guide, role standards, source map, and tests.

Validation

• .venv/bin/python -m pytest -q: 60 passed
• git diff --check: pass

Notes

This release keeps Code-role as local workflow assistance for target projects. Target-project code-role/ folders remain outside product release artifacts unless a project explicitly adopts them.

Code-role v0.1.0

Code-role v0.1.0

First public release of Code-role, a discussion-first local role workflow template for Codex-assisted software delivery.

What is included

• Eight role definitions: Workflow Orchestrator, Researcher, Product / PRD, Architect, Code Context, Implementer, Test Evaluator, and Reviewer.
• Lightweight milestone handoff as the default workflow.
• Optional strict packet locking for advanced handoff control.
• Target-project bootstrap script.
• Role output standards and packet templates.
• Public-source network research policy with explicit boundaries for private/authenticated resources.
• MIT License, contribution guide, security policy, CI, README workflow diagram, and minimal target-project example.

Boundary

Code-role is not an automation runner. It is designed to make each professional step discussable, reviewable, and explicitly accepted before the next role acts.

Generated target-project code-role/ folders are local operator assistance by default and should not be committed or shipped unless a project explicitly adopts them.