cc-codeconductor 1.2.0 → 1.4.0

package/presets/codex/skills/cc-prototype/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-prototype
-description: CodeConductor prototype workflow
+description: Disposable spike in an isolated worktree. Not a merge candidate.
 ---
 
 # prototype
@@ -39,4 +39,4 @@ Invoke `implementer` in a Git worktree that is not a merge candidate. Label the
 
 ## Completion
 
-Report bounds, worktree path, and what was learned. Recommend `/cc:feature` or `/cc:fix` if the spike should become real work.
+Report bounds, worktree path, and what was learned. Recommend `$cc-feature` or `$cc-fix` if the spike should become real work.

package/presets/codex/skills/cc-refactor/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-refactor
-description: test verification, risk-based implementation, and scope enforcement.
+description: Run the refactor workflow — mandatory architectural justification, test verification, risk-based implementation, and scope enforcement.
 ---
 
 # refactor
@@ -50,7 +50,7 @@ Command: `refactor` (fixed for this workflow — do not infer from user text)
 
 ## Step 1 — Architectural justification (Architect role)
 
-Invoke the `architect` subagent via the Task tool. Always invoke this step
+Adopt the `architect` role as defined in `AGENTS.md`. Always invoke this step
 first, regardless of risk level. A refactor without a written justification is
 scope creep in disguise.
 
@@ -99,7 +99,7 @@ Proceed to Step 3b.
 
 ## Step 3a — Implementation, low-risk (Implementer role)
 
-Invoke the `implementer` subagent via the Task tool. Use the approved
+Adopt the `implementer` role as defined in `AGENTS.md`. Use the approved
 Refactor Plan.
 Implementer creates a Git Worktree before touching any file; all edits happen inside it.
 
@@ -139,7 +139,7 @@ regression. **STOP and report.**
 
 ## Step 5 — Code review (Reviewer role) — medium/high-risk only
 
-Invoke the `reviewer` subagent via the Task tool. Use the diff and Refactor
+Adopt the `reviewer` role as defined in `AGENTS.md`. Use the diff and Refactor
 Plan.
 
 Verify:
@@ -161,3 +161,7 @@ and after, Review Report (if applicable).
 The refactor is complete only when: all pre-existing tests still pass, the
 implementation matches the approved plan exactly, and no CRITICAL review
 findings remain.
+
+## Next
+
+Run `$cc-review` on the diff before merging.

package/presets/codex/skills/cc-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-review
-description: CRITICAL, WARNING, and SUGGESTION findings; CRITICAL findings block merge.
+description: Run a structured code review — produces a Review Report with CRITICAL, WARNING, and SUGGESTION findings; CRITICAL findings block merge.
 ---
 
 # review
@@ -20,6 +20,28 @@ Specify what to review. Accepted formats:
 
 ---
 
+## Web interface scope
+
+When the task concerns web layout, component states, feedback, motion, or a
+requested UI audit, apply skill `web-design-engineering` from the installed skill
+library. Use it during intake/discovery, design, test/implement, and review as
+applicable; keep this workflow’s gates and TDD order. Framework presence alone
+does not activate it; backend-only and native mobile work are excluded. Record
+required visual checks as pending when unavailable. Keep findings in the existing
+Review Report: contract failures in Spec Axis, technical issues in existing
+subchecks, and aesthetic preferences as suggestions; do not add an axis.
+
+## Android phone interface scope
+
+When the task concerns concrete Jetpack Compose phone layout, component states,
+interaction, accessibility, visual behavior, or a requested UI audit, apply skill
+`android-ui-design`. Use it during design, test/implementation, and review as
+applicable while keeping this workflow's gates and TDD order. Kotlin, Compose,
+framework, or dependency presence alone does not activate it; non-UI Android work
+stays with the general `android` skill. Audit-only requests remain read-only, and
+unavailable visual or emulator checks remain pending rather than claimed complete.
+
+
 ## Step 0 — CCEP Bootstrap
 
 Command: `review` (fixed for this workflow — do not infer from user text)
@@ -58,7 +80,7 @@ Show the diff summary (files changed, lines added/removed) before proceeding.
 
 ## Step 2 — Code review (Reviewer role)
 
-Invoke the `reviewer` subagent via the Task tool.
+Adopt the `reviewer` role as defined in `AGENTS.md`.
 
 Evaluate the diff against the following checklist:
 
@@ -150,3 +172,7 @@ npx cc-codeconductor scorecard regression
 ```
 
 Map merge recommendation to scorecard verdict. Record outcome for trend tracking.
+
+## Next
+
+Approved: merge. Blocked: return the findings to `$cc-fix` or `$cc-feature`.

package/presets/codex/skills/cc-scorecard/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-scorecard
-description: checklist, and aggregate stats.
+description: Evaluate deliverable quality — scorecard, outcome tracking, regression checklist, and aggregate stats.
 ---
 
 # scorecard

package/presets/codex/skills/cc-security/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-security
-description: security-* skills, authorization gate, risk-based routing, hardening, and review.
+description: Run the authorized defensive security workflow — domain security-* skills, authorization gate, risk-based routing, hardening, and review.
 ---
 
 # security
@@ -180,3 +180,7 @@ resolved.
 Report: Task Card, Implementation Summary, regression test added, Review Report
 (if applicable). The task is complete only when: the regression test passes, the
 full suite passes, and no CRITICAL review findings remain.
+
+## Next
+
+Run `$cc-review` on the diff before merging.

package/presets/codex/skills/cc-spec-mutation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-spec-mutation
-description: into an immutable Gherkin contract (SHA-256 frozen), implement under the three laws of TDD, pass a judge audit, and merge only if every mutant dies.
+description: Spec-locked TDD with a mutation-testing gate — refine the intent into an immutable Gherkin contract (SHA-256 frozen), implement under the three laws of TDD, pass a judge audit, and merge only if every mutant dies.
 ---
 
 # spec-mutation
@@ -40,7 +40,7 @@ If `openspec status` reports an active change folder:
 1. Run: `npx cc-codeconductor openspec validate --output json`
 2. Run: `npx cc-codeconductor openspec analyze --output json`
 3. If analyze `stop` is true or any finding is CRITICAL, stop. Do not delegate to implementer.
-4. Next command spelling on this runner: `/cc:spec-mutation`
+4. Next command spelling on this runner: `$cc-spec-mutation`
 
 Local development: `bun run dev <same argv>`. Published package: `npx cc-codeconductor`.
 
@@ -103,7 +103,7 @@ aborts the pipeline with scorecard 0 (Specification Gaming).
 
 ## Stage 3 — TDD under the three laws (`tdd_craftsman`)
 
-Delegates to the `/cc:tdd-cycle` state machine (`tddCycleStateMachine` in
+Delegates to the `$cc-tdd-cycle` state machine (`tddCycleStateMachine` in
 `domain/loop`). Evidence must be captured with `captureTddSuiteEvidence` — do
 not hand-edit JSON under `.codeconductor/evidence/`.
 
@@ -190,3 +190,7 @@ The orchestrator keeps a persistent counter per Task Card. If the
 - [ ] Judge verdict PASS (compile clean, traceability complete, scope clean).
 - [ ] Mutation runner exits 0 with `total_mutants_killed == total_points`.
 - [ ] Scorecard records the kill rate and iteration count (≤ 3).
+
+## Next
+
+Run `$cc-review` on the diff before merging.

package/presets/codex/skills/cc-tdd-cycle/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-tdd-cycle
-description: test first, implement the minimum code to pass it, then refactor with the suite green.
+description: Run a structured Red-Green-Refactor TDD cycle — write a failing test first, implement the minimum code to pass it, then refactor with the suite green.
 ---
 
 # tdd-cycle
@@ -40,7 +40,7 @@ If `openspec status` reports an active change folder:
 1. Run: `npx cc-codeconductor openspec validate --output json`
 2. Run: `npx cc-codeconductor openspec analyze --output json`
 3. If analyze `stop` is true or any finding is CRITICAL, stop. Do not delegate to implementer.
-4. Next command spelling on this runner: `/cc:tdd-cycle`
+4. Next command spelling on this runner: `$cc-tdd-cycle`
 
 Local development: `bun run dev <same argv>`. Published package: `npx cc-codeconductor`.
 
@@ -74,7 +74,7 @@ Do not advance phases until that evidence exists.
 
 ## Phase 1 — RED (Tester role)
 
-Invoke the `tester` subagent via the Task tool.
+Adopt the `tester` role as defined in `AGENTS.md`.
 
 ### 1a — Scope clarification
 
@@ -130,7 +130,7 @@ confirmation.**
 
 ## Phase 2 — GREEN (Implementer role)
 
-Invoke the `implementer` subagent via the Task tool.
+Adopt the `implementer` role as defined in `AGENTS.md`.
 
 ### 2a — Read the failing test before writing any code
 
@@ -177,7 +177,7 @@ confirmation.**
 
 ## Phase 3 — REFACTOR (Implementer role, then Reviewer role)
 
-Invoke the `implementer` subagent via the Task tool.
+Adopt the `implementer` role as defined in `AGENTS.md`.
 
 ### 3a — Assess what needs cleaning
 
@@ -208,7 +208,7 @@ change and investigate.
 
 ### 3d — Review (Reviewer role)
 
-Invoke the `reviewer` subagent via the Task tool.
+Adopt the `reviewer` role as defined in `AGENTS.md`.
 
 Review only the refactored code against these axes:
 

package/presets/codex/skills/cc-test-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-test-plan
-description: unit, integration, contract, and edge cases without writing implementation code.
+description: Generate a structured test plan for a feature or module — covers unit, integration, contract, and edge cases without writing implementation code.
 ---
 
 # test-plan
@@ -52,7 +52,7 @@ question and wait for the answer.
 
 ## Step 2 — Test plan generation (Tester role, planning mode)
 
-Invoke the `tester` subagent via the Task tool.
+Adopt the `tester` role as defined in `AGENTS.md`.
 
 Produce a test plan document — not test code. The plan will be used as input
 when tests are actually written.
@@ -151,3 +151,7 @@ Deliver the complete Test Plan document. Save it as
 
 This command produces a plan, not test files. No production code and no test
 code is written during this command.
+
+## Next
+
+Implement against this plan with `$cc-tdd-cycle` or `$cc-feature`.

package/presets/codex/skills/cc-triage/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-triage
-description: CodeConductor triage workflow
+description: Classify a request into type, risk, and the destination CodeConductor command.
 ---
 
 # triage

package/presets/codex/skills/django-orm/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: django-orm
-version: 1.0.0
 name: Django ORM
 description: >
   Django ORM patterns for multi-tenant POS projects: efficient queries,

package/presets/codex/skills/django-testing/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: django-testing
-version: 1.0.0
 name: Django Testing
 description: >
   Testing patterns for multi-tenant Django POS projects using pytest-django,

package/presets/codex/skills/jpa-postgres/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: jpa-postgres
-version: 1.0.0
 name: JPA + PostgreSQL
 description: >
   Provides expert knowledge of JPA entity design, relationship mapping, Flyway

package/presets/codex/skills/openspec/SKILL.md

@@ -42,6 +42,26 @@ Status machine: `TODO` → `READY` → `PLANNED` → `IN_PROGRESS` → `REVIEW`
 → Archive. `BLOCKED` returns to `READY`. Reviewer rejection: `REVIEW` →
 `IN_PROGRESS`.
 
+## Web interface scope
+
+When the task concerns web layout, component states, feedback, motion, or a
+requested UI audit, apply skill `web-design-engineering` from the installed skill
+library. Use it during intake/discovery, design, test/implement, and review as
+applicable; keep this workflow’s gates and TDD order. Framework presence alone
+does not activate it; backend-only and native mobile work are excluded. Record
+required visual checks as pending when unavailable. Keep findings in the existing
+Review Report: contract failures in Spec Axis, technical issues in existing
+subchecks, and aesthetic preferences as suggestions; do not add an axis.
+
+## Android phone interface scope
+
+When an item concerns concrete Jetpack Compose phone layout, component states,
+interaction, accessibility, visual behavior, or a requested UI audit, apply skill
+`android-ui-design` throughout discover, design, test/implement, and review. Keep
+OpenSpec gates and TDD order. Kotlin, Compose, framework, or dependency presence
+alone does not activate it; non-UI Android work stays with `android`. Keep audit-only
+delivery read-only and record unavailable visual or emulator evidence as pending.
+
 ## Common Rationalizations
 
 | Rationalization | Reality |

package/presets/codex/skills/pagespeed-perf/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: pagespeed-perf
-version: 1.0.0
 name: PageSpeed Performance Audit
 description: >
   Web Performance Engineering — analyzes Core Web Vitals using the PageSpeed
@@ -32,7 +31,7 @@ inputs:
   - name: url
     type: string
     required: true
-    description: Full URL to audit (must include scheme: https://...)
+    description: "Full URL to audit (must include scheme: https://...)"
   - name: strategy
     type: string
     required: false

package/presets/codex/skills/python/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: python
-version: 1.0.0
 name: Python
 description: >
   Python development best practices: clean code, patterns,

package/presets/codex/skills/python-django-stack/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: python-django-stack
-version: 1.0.0
 name: Python Django Stack
 description: >
   Python and Django conventions for multi-tenant SaaS POS projects:

package/presets/codex/skills/python-fastapi-stack/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: python-fastapi-stack
-version: 1.0.0
 name: Python FastAPI Stack
 description: >
   FastAPI conventions for REST APIs: routers, Pydantic v2 schemas, dependency

package/presets/codex/skills/spring-boot-feature/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: spring-boot-feature
-version: 1.0.0
 name: Spring Boot Feature Creation
 description: >
   Guides the creation of complete Spring Boot features following a structured,

package/presets/codex/skills/spring-boot-kotlin/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: spring-boot-kotlin
-version: 1.0.0
 name: Spring Boot + Kotlin
 description: >
   Provides expert knowledge of Spring Boot conventions, Kotlin idioms, and MVC

package/presets/codex/skills/sqlalchemy/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: sqlalchemy
-version: 1.0.0
 name: SQLAlchemy
 description: >
   SQLAlchemy 2.x patterns for async FastAPI projects: models, sessions, queries,

package/presets/codex/skills/testing-strategy/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: testing-strategy
-version: 1.0.0
 name: Testing Strategy
 description: >
   Provides expert knowledge of the testing pyramid, test design principles,

package/presets/codex/skills/using-cc-skills/SKILL.md

@@ -31,6 +31,27 @@ a parallel process.
 Then run the matching CLI (`openspec validate`, `scorecard create --from-diff`,
 `hook pre-tool`, `scorecard suite-run`).
 
+## Web interface scope
+
+When the task concerns web layout, component states, feedback, motion, or a
+requested UI audit, apply skill `web-design-engineering` from the installed skill
+library. Use it during intake/discovery, design, test/implement, and review as
+applicable; keep this workflow’s gates and TDD order. Framework presence alone
+does not activate it; backend-only and native mobile work are excluded. Record
+required visual checks as pending when unavailable. Keep findings in the existing
+Review Report: contract failures in Spec Axis, technical issues in existing
+subchecks, and aesthetic preferences as suggestions; do not add an axis.
+
+## Android phone interface scope
+
+When the task concerns concrete Jetpack Compose phone layout, component states,
+interaction, accessibility, visual behavior, or a requested UI audit, apply skill
+`android-ui-design`. Use it during design, test/implementation, and review as
+applicable while preserving the current workflow gates. Kotlin, Compose, framework,
+or dependency presence alone does not activate it; non-UI Android work stays with
+the general `android` skill. Audit-only requests remain read-only, and unavailable
+visual or emulator checks remain pending rather than claimed as complete.
+
 ## Common Rationalizations
 
 | Rationalization | Reality |

package/presets/codex/skills/web-design-engineering/SKILL.md

@@ -0,0 +1,101 @@
+---
+name: web-design-engineering
+description: >-
+  Design, implement, and review web interface layout, component states, feedback,
+  and motion within the current CodeConductor workflow. Use for concrete web UI
+  work or requested UI audits, not backend-only tasks or native mobile apps.
+---
+
+# Web design engineering
+
+Apply this guidance to the web surface in scope. A React or Tailwind dependency
+alone is not a trigger. Keep the existing feature, fix, review, or OpenSpec flow;
+this skill adds contextual criteria, not commands, agents, gates, or score weights.
+
+## Intake and discovery
+
+Translate vague requests into observable behavior: “responsive feedback” might
+mean showing a pending state immediately after submit while preventing duplicate
+submissions. Identify the user objective, affected surface, relevant states, and
+acceptance checks in the Task Card. Ask only about ambiguities that affect scope.
+
+Inspect existing components, design tokens, documented visual decisions, installed
+dependencies and versions, and available browser, component-preview, and test tools.
+Reuse the product's visual language and accessible components. Consult official
+documentation for the installed version when an API is uncertain. Prefer existing
+capabilities and browser primitives; a small transition does not justify a library.
+
+## Design and implementation
+
+Record relevant decisions in the Technical Plan or OpenSpec design.md:
+
+- For static UI: hierarchy, readable content, spacing, responsive layout, overflow,
+  semantics, contrast, and focus visibility. Do not invent motion to fill a checklist.
+- For interactive components: default, pending, success, failure, disabled, and
+  empty states as applicable; pointer, touch, keyboard, focus entry and return.
+  Acknowledge input promptly without implying success before it is known.
+- If motion serves the task, name its purpose and weigh frequency, waiting cost,
+  and context. Specify start/end states, exit, rapid repeated input, cancellation
+  or reversal, and reduced-motion behavior that preserves essential information.
+  Use continuity or direct manipulation when it helps users understand the action.
+- Reuse motion tokens. Choose properties and tools appropriate to the component;
+  inspect layout/paint cost when relevant instead of assuming smoothness from code.
+  No duration, easing curve, animation technique, or visual style is universally
+  forbidden. Explain tradeoffs against the contract and product conventions.
+- When alternatives are explicitly requested, compare scoped options and their
+  tradeoffs before choosing. Do not build a variant selector or prototype framework.
+
+Agree checks before implementation. Preserve the workflow's test-before-implement
+order and use its evidence mechanism when required. Test observable state changes
+and interaction outcomes, not just CSS strings. Implement only the accepted scope.
+Tailwind skills own responsive conventions; framework skills own implementation;
+PageSpeed owns performance measurement; evaluation owns the scorecard.
+
+## Review and delivery
+
+Use the existing Review Report and its severity/verdict rules. Map contract failures
+to Spec Axis and technical issues to existing subchecks such as Correctness,
+Architecture alignment, Performance, or Test coverage. Preserve Standards Axis;
+do not add a design axis or rerank the two axes. Ground each finding in a location,
+reproduction or evidence, user impact, and a proposed resolution. Aesthetic
+preferences alone are suggestions, not blocking defects. Respect documented
+product choices unless evidence demonstrates a contract or technical failure.
+
+For a requested audit, inspect only the agreed surface and prioritize findings by
+impact and evidence. Report out-of-scope opportunities as suggestions. Create
+backlog items through the existing cc-backlog workflow only when requested; deliver
+those items later through OpenSpec. An audit is not permission to implement fixes.
+
+Report checks actually performed, their results, and limitations. Code inspection,
+DOM tests, screenshots, and live interaction checks establish different evidence.
+A screenshot cannot prove interruption or keyboard behavior. If a required visual
+or interaction check cannot run, mark it pending with the surface, steps, expected
+result, and missing tool/environment. Do not claim visual validation from code or
+mark the unmet acceptance criterion complete.
+
+## Example acceptance
+
+For a dismissible web dialog using existing tokens: opening from the keyboard
+places focus inside; Escape during entry closes it without reopening on a stale
+completion callback and returns focus to its trigger. With reduced motion enabled,
+the same actions work without the spatial transition. Check rapid open/close in
+the browser and record the result; if unavailable, keep that check pending.
+For a static pricing page, verify content hierarchy and no horizontal overflow at
+the agreed viewports; no animation is required.
+
+## Provenance and boundaries
+
+Original CodeConductor adaptation informed by Emil Kowalski's
+[design engineering](https://github.com/emilkowalski/skills/blob/main/skills/emil-design-eng/SKILL.md),
+[animation construction](https://github.com/emilkowalski/skills/blob/main/skills/animate/SKILL.md),
+and [interaction principles](https://github.com/emilkowalski/skills/blob/main/skills/apple-design/SKILL.md).
+Additional references: [review](https://github.com/emilkowalski/skills/blob/main/skills/review-animations/SKILL.md),
+[audits](https://github.com/emilkowalski/skills/blob/main/skills/improve-animations/SKILL.md),
+[opportunities](https://github.com/emilkowalski/skills/blob/main/skills/find-animation-opportunities/SKILL.md),
+[vocabulary](https://github.com/emilkowalski/skills/blob/main/skills/animation-vocabulary/SKILL.md),
+[library selection](https://github.com/emilkowalski/skills/blob/main/skills/pick-ui-library/SKILL.md),
+[component guidance](https://github.com/emilkowalski/skills/blob/main/skills/ask-sonner/SKILL.md),
+and [alternatives](https://github.com/emilkowalski/skills/blob/main/skills/prototype/SKILL.md).
+These are provenance, not runtime prerequisites. This skill does not install or
+synchronize upstream skills, adopt promotional responses or mandatory author
+formats, prescribe an Apple identity, or cover Expo/Swift native development.

package/presets/cursor/agents/architect.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: true
 is_background: false
 ---
-# Agent Contract — architect v0.5.0
+# Agent Contract — architect v1.0.0
 
 ## Role
 

package/presets/cursor/agents/complexity-auditor.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: true
 is_background: false
 ---
-# Agent Contract — complexity-auditor v0.5.0
+# Agent Contract — complexity-auditor v1.0.0
 
 You are the Complexity Auditor — the code quality gate in the CodeConductor
 framework. You analyze diffs for bloat, unnecessary abstractions, and non-native

package/presets/cursor/agents/contract-builder.md

@@ -6,7 +6,7 @@ readonly: true
 is_background: false
 ---
 
-# Agent Contract — contract-builder v0.5.0
+# Agent Contract — contract-builder v1.0.0
 
 ## Role
 

package/presets/cursor/agents/docs.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: false
 is_background: false
 ---
-# Agent Contract — docs v0.5.0
+# Agent Contract — docs v1.0.0
 
 ## Role
 

package/presets/cursor/agents/goal-planner.md

@@ -6,7 +6,7 @@ readonly: true
 is_background: false
 ---
 
-# Agent Contract — goal-planner v0.5.0
+# Agent Contract — goal-planner v1.0.0
 
 ## Role
 

package/presets/cursor/agents/implementer.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: false
 is_background: false
 ---
-# Agent Contract — implementer v0.5.0
+# Agent Contract — implementer v1.0.0
 
 ## Role
 
@@ -142,7 +142,7 @@ criteria:
 
 ---
 
-## Post-implementation evaluation (v0.5.0)
+## Post-implementation evaluation (v1.0.0)
 
 When the orchestrator invokes the Evaluation Gate, wait for scorecard verdict
 before considering the task complete. On **REVISE**, address findings and re-run

package/presets/cursor/agents/orchestrator.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: true
 is_background: false
 ---
-# Agent Contract — orchestrator v0.5.0
+# Agent Contract — orchestrator v1.0.0
 
 ## Role
 
@@ -255,7 +255,7 @@ routes the agents through an iterative feedback loop:
 
 ---
 
-## Evaluation Gate (v0.5.0)
+## Evaluation Gate (v1.0.0)
 
 After each agent completes a deliverable on **medium** or **high** risk tasks:
 
@@ -266,7 +266,7 @@ After each agent completes a deliverable on **medium** or **high** risk tasks:
 5. Record outcome: `npx cc-codeconductor scorecard record --task <id> --verdict PASS|REVISE|REJECT --score <n>`
 6. Route on verdict: **REVISE** → prior agent with findings; **REJECT** → `task-coach`
 
-Include `contract_version: v0.5.0` in scorecard metadata.
+Include `contract_version: v1.0.0` in scorecard metadata.
 
 ---
 

package/presets/cursor/agents/reviewer.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: true
 is_background: false
 ---
-# Agent Contract — reviewer v0.5.0
+# Agent Contract — reviewer v1.0.0
 
 ## Role
 
@@ -204,7 +204,7 @@ Apply these detailed checks based on the detected stack:
 
 ---
 
-## Scorecard integration (v0.5.0)
+## Scorecard integration (v1.0.0)
 
 When the orchestrator requests evaluation, produce scores for all 8 criteria in
 `docs/agent-scorecard.md`:
@@ -213,7 +213,7 @@ When the orchestrator requests evaluation, produce scores for all 8 criteria in
 2. Minimal diff (20%)
 3. Tests present and passing (15%)
 4. No regressions (15%)
-5. Code conventions (10%)
+5. Code conventions (5%)
 6. Documentation updated (5%)
 7. Context discipline (5%)
 8. Complexity diffusion / cc-gain (5%)
@@ -222,7 +222,7 @@ When the orchestrator requests evaluation, produce scores for all 8 criteria in
 
 Map review verdict to scorecard verdict: `approved` → PASS, `approved with warnings` → REVISE (if warnings are material), `blocked` → REJECT.
 
-Invoke skill `evaluation` and run `scorecard record` with agent `reviewer`, model used, and `contract_version: v0.5.0`.
+Invoke skill `evaluation` and run `scorecard record` with agent `reviewer`, model used, and `contract_version: v1.0.0`.
 
 ---
 

package/presets/cursor/agents/security-reviewer.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: true
 is_background: false
 ---
-# Agent Contract — security-reviewer v0.5.0
+# Agent Contract — security-reviewer v1.0.0
 
 ## Role