@azure-id/orc 0.56.1 → 1.1.0

package/templates/skills/orc-diy/references/blocks/mock-example.md

@@ -1,22 +0,0 @@
-## Phase: Mock example (after a green verify, before ship)
-
-<!-- diy:when mock_example=off -->
-The mock-example phase is DISABLED in this flow. Skip silently.
-<!-- /diy:when -->
-<!-- diy:when mock_example=ask -->
-After the verify/smoke gate is GREEN and BEFORE any ship action, the offer is
-MANDATORY (never silently skipped, never silently run): follow
-`.claude/skills/_shared/drift-recovery.md` — build
-`mock-examples/<change-slug>/` (EXAMPLE.md + one minimal runnable mocked
-artifact) only on a yes. After the user runs it, ask the one drift question;
-on drift run the `DRIFT-FROM` recovery loop (hard cap 2, then an honest
-unresolved report). `mock-examples/` is NEVER staged by the ship phase.
-<!-- /diy:when -->
-<!-- diy:when mock_example=on -->
-After the verify/smoke gate is GREEN and BEFORE any ship action, build the
-mocked example without asking, per
-`.claude/skills/_shared/drift-recovery.md`: `mock-examples/<change-slug>/`
-(EXAMPLE.md + one minimal runnable mocked artifact; mocked inputs only). Then
-ask the one drift question; on drift run the `DRIFT-FROM` recovery loop (hard
-cap 2). `mock-examples/` is NEVER staged by the ship phase.
-<!-- /diy:when -->

package/templates/skills/orc-diy/references/blocks/planning.md

@@ -1,34 +0,0 @@
-## Phase: Planning
-
-<!-- diy:when planning=auto -->
-Route planning exactly as the full lane does — Superpowers plan, OpenSpec
-change, or ORC's own planner, chosen by what exists in the project. Follow
-`.claude/skills/orc/subskills/orc-planner/SKILL.md` for the own-planner path
-and validate the planning output against
-`.claude/skills/orc/schemas/planning-output.md`.
-<!-- /diy:when -->
-<!-- diy:when planning=own-planner -->
-Always use ORC's own Requirement Planner, even when Superpowers/OpenSpec
-artifacts exist: follow `.claude/skills/orc/subskills/orc-planner/SKILL.md`
-and validate the planning output against
-`.claude/skills/orc/schemas/planning-output.md`.
-<!-- /diy:when -->
-<!-- diy:when planning=superpowers -->
-Plan via Superpowers: require a Superpowers-written plan as planning input
-(ask the user to produce one if absent), then convert it to ORC planning
-output validated against `.claude/skills/orc/schemas/planning-output.md` —
-same conversion the full lane applies on its Superpowers route.
-<!-- /diy:when -->
-<!-- diy:when planning=openspec -->
-Plan via OpenSpec: require an OpenSpec change as planning input (ask the user
-to produce one if absent), then convert it to ORC planning output validated
-against `.claude/skills/orc/schemas/planning-output.md` — same conversion the
-full lane applies on its OpenSpec route.
-<!-- /diy:when -->
-<!-- diy:when tdd=on -->
-TDD is ON for this flow: the plan must carry a `tdd_spec` per requirement
-(given/when/then + a runnable skeleton in the project's test framework, or
-`tdd: exempt — <reason>`; schema in
-`.claude/skills/orc/schemas/planning-output.md`). No test runner in the
-project → whole-run exemption, stated once at preflight.
-<!-- /diy:when -->

package/templates/skills/orc-diy/references/blocks/review.md

@@ -1,18 +0,0 @@
-## Phase: Review
-
-<!-- diy:when review=off -->
-Code review is DISABLED in this flow. Say so in the run summary line ("review
-skipped by flow config") — never imply the work was reviewed.
-<!-- /diy:when -->
-<!-- diy:when review=on -->
-Dispatch the reviewer exactly as the full lane does — follow the review half
-of `.claude/skills/orc/subskills/orc-review-verify/SKILL.md` (reviewer agent
-`orc-reviewer-opus-5-med`; findings ride the severity ladder from the
-locked rules, blocking and advisory findings both surfaced).
-<!-- /diy:when -->
-<!-- diy:when review=blocking-only -->
-Dispatch the reviewer exactly as the full lane does — follow the review half
-of `.claude/skills/orc/subskills/orc-review-verify/SKILL.md` — but only
-P0/P1 findings gate anything; P2/P3 findings are listed once in the summary
-and never re-offered as fix-up tasks.
-<!-- /diy:when -->

package/templates/skills/orc-diy/references/blocks/scoring.md

@@ -1,16 +0,0 @@
-## Phase: Task scoring → executor selection
-
-<!-- diy:when scoring=on -->
-Score each task 0–100 with the full lane's rubric (see the scoring section of
-`.claude/skills/orc/SKILL.md`), then dispatch the executor agent from THIS
-compiled table — it is already clipped to this flow's session tier; never
-substitute a preset from `config.md`:
-
-{{score_table}}
-<!-- /diy:when -->
-<!-- diy:when scoring=off -->
-Scoring is DISABLED in this flow. Skip the rubric entirely: EVERY execution
-task dispatches to **{{fixed_executor}}**. Wave grouping, declared-files
-conflict rules, and slice construction are unchanged — scoring off changes
-model selection only, never scheduling.
-<!-- /diy:when -->

package/templates/skills/orc-diy/references/blocks/security.md

@@ -1,25 +0,0 @@
-## Phase: Security pass
-
-<!-- diy:when security=off -->
-The security pass is OFF in this flow — skip silently.
-<!-- /diy:when -->
-<!-- diy:when security=ask -->
-When at least one task scored at or above the risk floor (70), ask the user
-once after review whether to run the security pass; on yes, run it exactly as
-the full lane's Phase 5.5 (reviewer re-dispatched with the checklist from
-`.claude/skills/orc/references/security-checklist.md`, sweeping only the
-run's changed files).
-<!-- /diy:when -->
-<!-- diy:when security=on -->
-When at least one task scored at or above the risk floor (70), dispatch the
-security pass without asking — the full lane's Phase 5.5 with the checklist
-from `.claude/skills/orc/references/security-checklist.md`, sweeping only the
-run's changed files.
-<!-- /diy:when -->
-<!-- diy:when security=always -->
-Dispatch the security pass on EVERY run of this flow, regardless of task
-scores — the full lane's Phase 5.5 with the checklist from
-`.claude/skills/orc/references/security-checklist.md`, sweeping only the
-run's changed files. (This flow removes the risk-floor trigger, not the
-pass's mechanics.)
-<!-- /diy:when -->

package/templates/skills/orc-diy/references/blocks/ship.md

@@ -1,25 +0,0 @@
-## Phase: Ship
-
-State the current branch and the change summary BEFORE any git action, and
-never ship on a red build (locked rule).
-
-<!-- diy:when ship_mode=ask -->
-Ask the user how to ship: commit, PR (via
-`.claude/skills/orc/subskills/orc-pr/SKILL.md`), or leave the working tree
-as-is. Default when auto-accepted by autonomy: leave as-is and report.
-<!-- /diy:when -->
-<!-- diy:when ship_mode=commit -->
-Commit the run's changes on a green gate without asking (branch first if on
-the default branch; conventional message from the intent). PRs only if the
-user asks afterwards.
-<!-- /diy:when -->
-<!-- diy:when ship_mode=pr -->
-On a green gate, create the PR without asking via
-`.claude/skills/orc/subskills/orc-pr/SKILL.md` (branch + commit + push + PR
-body from the run artifacts).
-<!-- /diy:when -->
-<!-- diy:when ship_mode=report-only -->
-NEVER commit or push in this flow. Leave the working tree modified, and end
-with the change report + suggested commit message the user can apply
-themselves.
-<!-- /diy:when -->

package/templates/skills/orc-diy/references/blocks/summary.md

@@ -1,18 +0,0 @@
-## Phase: Summary
-
-<!-- diy:when summary=off -->
-No summary phase: end after ship with a single line (tasks done / gate color
-/ ship action taken) plus usage, and note which phases this flow skipped.
-<!-- /diy:when -->
-<!-- diy:when summary=short -->
-Short summary: one paragraph — what was built, gate results, ship action,
-skipped phases, and usage. No per-task breakdown.
-<!-- /diy:when -->
-<!-- diy:when summary=full -->
-Full summary exactly as the full lane's final phase: per-task outcomes with
-models used, findings outcomes, verify results, ship action, skipped
-phases, and usage.
-<!-- /diy:when -->
-
-Always name the phases this flow skipped by config — the user must never
-mistake a DIY run for a full-lane run.

package/templates/skills/orc-diy/references/blocks/testgen.md

@@ -1,17 +0,0 @@
-## Phase: Test authoring
-
-<!-- diy:when testgen=off -->
-Test authoring is OFF in this flow — skip silently.
-<!-- /diy:when -->
-<!-- diy:when testgen=ask -->
-After verify (or after execution when verify is off), offer test authoring
-once; on yes, run the full lane's Phase 6.5 via
-`.claude/skills/orc/subskills/orc-testgen/SKILL.md` — it WRITES test cases
-and a test plan, never runs them, and never gates the ship.
-<!-- /diy:when -->
-<!-- diy:when testgen=on -->
-After verify (or after execution when verify is off), run the full lane's
-Phase 6.5 without asking via
-`.claude/skills/orc/subskills/orc-testgen/SKILL.md` — it WRITES test cases
-and a test plan, never runs them, and never gates the ship.
-<!-- /diy:when -->

package/templates/skills/orc-diy/references/blocks/trace.md

@@ -1,28 +0,0 @@
-<!-- GENERATED SOURCE BLOCK — stitched by `orc diy compile`. Edit the block
-     template in skills/orc-diy/references/blocks/, never the compiled file. -->
-## Behavior trace (PERMANENT — always on, no flow key)
-
-Tracing is NOT composable: every ORC run traces, this one included. Follow
-`.claude/skills/orc/references/trace-protocol.md` (load it at run start) — this
-block is stitched into every compiled flow so a user-composed pipeline can never
-be the one lane that runs blind.
-
-**Run start:** create `log_dir`, write `log_dir/.current` =
-`run-diy-<slug>-<DDMMYY>-<HHMMSS>.txt` AND `touch the trace file` of that name
-in the SAME step (a pointer naming a file that does not exist reads as dangling —
-the hook rotates away from it and the run splits across two files), then store
-`trace_path` in the checkpoint. The lane token is `diy`, whatever the flow is
-named.
-
-**Narration is dispatched, never remembered:** record each event with its REAL
-timestamp into a phase packet (`PHASE`, `DISPATCH`/`VERIFY` per spawn —
-`actual_model`/`actual_effort` vs expected, surface any ⛔ DOWNGRADE to the user
-— `SCORE`, `OUTCOME`, `GATE`, `FINDING`/`VERDICT` for whichever gates this flow
-enabled, `FINISH`, plus `decisions` = the WHY), then dispatch
-`orc-trace-writer-haiku-4-5` with it, PAIRED with the next phase's first
-dispatch. **One packet per ENABLED phase group, minimum 2** — the flow shape is
-composed, so the packet count is too; a phase this flow turned OFF owes nothing.
-A phase ending with `zero new trace lines is a protocol violation`.
-
-**Run end:** the `FINISH` packet goes out and RETURNS, then delete
-`log_dir/.current`.

package/templates/skills/orc-diy/references/blocks/verify.md

@@ -1,25 +0,0 @@
-## Phase: Verify
-
-<!-- diy:when verify=off -->
-Verification is DISABLED in this flow. The build+test evidence in each
-executor return is the only green signal; say "verify skipped by flow
-config" in the summary. Never claim criteria were verified.
-<!-- /diy:when -->
-<!-- diy:when verify=smoke -->
-Run a SMOKE verify only: dispatch the verifier
-(`orc-verifier-opus-5-med`) with an explicitly narrowed scope — build +
-full test suite, red/green verdict, NO per-criterion definition-of-done
-sweep. Red blocks ship exactly as a full verify would.
-<!-- /diy:when -->
-<!-- diy:when verify=full -->
-Dispatch verification exactly as the full lane does — follow the verify half
-of `.claude/skills/orc/subskills/orc-review-verify/SKILL.md` (build + tests +
-every acceptance criterion checked against the definition of done).
-<!-- /diy:when -->
-<!-- diy:when tdd=on -->
-TDD gate (rides the verify slot): the verifier slice carries the plan's
-`tdd_suite[]`; green is the definition-of-done for non-exempt requirements,
-red → the repair loop capped at `tdd_loop_max` (cap hit → STOP + honest red
-report). The adversarial half of the verify pass applies as the full lane
-defines it.
-<!-- /diy:when -->