@fernado03/zoo-flow 0.11.1 → 0.11.2

package/examples/fix-flow.md

@@ -1,139 +0,0 @@
-# Example: `/fix` flow
-
-A worked example of the multi-phase `/fix` chain: orchestrator delegates
-to the architect, architect diagnoses, architect switches to the tweaker
-to implement, tweaker switches back, architect runs the post-mortem,
-tweaker prepares the commit. The whole flow has explicit HITL stops.
-
-## Setup
-
-- Active mode: `🪃 Custom Orchestrator`.
-- Workspace has a real bug to fix. For this example, assume:
-
-  > "The login button does nothing on the second click. First click
-  > works."
-
-## Phase 1 — orchestrator routes
-
-Type:
-
-```
-/fix The login button does nothing on the second click. First click works.
-```
-
-**Expected**
-
-Orchestrator looks up the routing matrix and delegates with `new_task`
-targeting `system-architect`. The delegated message includes the
-slash form, user context, proceed policy, command-protocol pointer,
-skills location, and the completion rule.
-
-## Phase 2 — architect diagnoses
-
-The new task window opens in `🏗️ System Architect`. The architect:
-
-1. Loads `/fix` per the command protocol.
-2. Runs the `diagnose` skill, phases 1–3.
-3. Produces a short list of hypotheses.
-4. **Halts** and asks you to pick one.
-
-**Expected message (paraphrased)**
-
-> Hypotheses:
-> 1. Click handler is wired once and never re-bound after a state change.
-> 2. The button enters a disabled state on first click and never resets.
-> 3. A queued network request is canceling the second click's handler.
->
-> Which would you like to instrument? (1 / 2 / 3)
-
-You answer:
-
-```
-2
-```
-
-## Phase 3 — architect instruments
-
-The architect runs phase 4 of the `diagnose` skill on hypothesis 2.
-This phase may involve reading state-management code, adding a
-console-log or instrumentation suggestion (Markdown only — the architect
-cannot edit source), and producing a confirmed root cause.
-
-**Expected**
-
-> Root cause confirmed: `LoginButton` sets `disabled` on the first
-> click and the `onSuccess` handler does not reset it. The second
-> click is being absorbed by the disabled state.
-
-The architect summarizes the proposed fix and prepares to hand off.
-
-## Phase 4 — architect switches to tweaker
-
-The architect calls `switch_mode` to `code-tweaker` **inside the same
-task window** with a summary of:
-
-- The root cause.
-- The proposed fix (`onSuccess` resets `disabled`).
-- The files involved.
-- The tests to add or extend.
-
-The tweaker takes over without losing context.
-
-## Phase 5 — tweaker implements
-
-The tweaker:
-
-1. Edits the `LoginButton` component to reset `disabled` on success
-   and on error.
-2. Adds or extends tests covering the second-click case.
-3. Runs the test suite.
-4. Reports back.
-
-**HITL stop**: the tweaker does not commit. Per the git rule, it waits
-for your approval.
-
-## Phase 6 — back to architect for post-mortem
-
-The tweaker calls `switch_mode` back to `system-architect`. The
-architect runs phase 6 of `diagnose` (post-mortem):
-
-- What was the original assumption that masked the bug?
-- Is this an isolated mistake or a pattern?
-- If a pattern, would `/refactor` help?
-
-The architect produces a short post-mortem note in `docs/` or
-`.scratch/` (Markdown only) and either drops the matter there or
-suggests `/refactor`.
-
-## Phase 7 — tweaker prepares the commit
-
-The architect switches back to the tweaker. The tweaker suggests
-`/commit-and-document`. **The orchestrator does not auto-launch it.**
-That command runs only when you type it.
-
-## Phase 8 — return to orchestrator
-
-When the chain is complete (or blocked), the active mode calls
-`attempt_completion`. The orchestrator summarizes for you and halts.
-
-## Pass criteria
-
-- [ ] Orchestrator delegated to `system-architect`, not the tweaker.
-- [ ] Architect halted after phase 3 hypotheses, did not instrument
-      until you picked one.
-- [ ] Architect did not edit source code at any point.
-- [ ] Architect used `switch_mode` (same window) to hand off, not
-      `new_task`.
-- [ ] Tweaker did not run `git commit` or `git push` without your
-      explicit approval.
-- [ ] After return, orchestrator halted instead of auto-launching
-      `/commit-and-document`.
-
-## Common slips
-
-- Architect tries to edit source: see
-  [`docs/troubleshooting.md`](../docs/troubleshooting.md#architect-trying-to-edit-source).
-- Tweaker commits without approval: tighten the git rule in the
-  tweaker's `customInstructions`.
-- Orchestrator launches `/commit-and-document` automatically: see
-  [`docs/troubleshooting.md`](../docs/troubleshooting.md#slash-command-leakage-from-subtask-summaries).

package/quality/scorecard.json

@@ -1,88 +0,0 @@
-{
-  "version": 1,
-  "minimum_score": 9.5,
-  "categories": {
-    "command_integrity": {
-      "weight": 0.20,
-      "checks": [
-        "All documented commands have mode declarations",
-        "All mode declarations match command-policy map",
-        "Global rules cover paths, protocol, failure, reply, context-economy",
-        "Mode rule folders exist for all three custom modes",
-        "Routing table matches command-policy map"
-      ],
-      "max_score": 10.0
-    },
-    "skill_quality": {
-      "weight": 0.20,
-      "checks": [
-        "Every command referencing a skill uses canonical Skill: marker",
-        "Referenced skills exist on disk",
-        "Skills describe purpose, steps, and output format",
-        "No thin non-canonical skill wrappers exist",
-        "Skills follow bucket layout under .roo/skills/"
-      ],
-      "max_score": 10.0
-    },
-    "validation_depth": {
-      "weight": 0.20,
-      "checks": [
-        "Doctor validates all required files exist",
-        "Doctor checks skill-reference integrity",
-        "Doctor checks mode slugs against allowed set",
-        "Doctor detects built-in delegation targets",
-        "Doctor checks .roomodes permits documented commands",
-        "Doctor validates routing table rows",
-        "Doctor detects old doc-name leakage",
-        "Doctor validates ADR path consistency"
-      ],
-      "max_score": 10.0
-    },
-    "token_economy": {
-      "weight": 0.10,
-      "checks": [
-        "Context-economy rule exists and is referenced",
-        "Domain-doc read gate defers broad reads",
-        "Completion rules specify evidence output format",
-        "Orchestrator routes by risk level to lightest safe workflow"
-      ],
-      "max_score": 10.0
-    },
-    "verification": {
-      "weight": 0.10,
-      "checks": [
-        "Verify command exists and references verify skill",
-        "Verify skill specifies evidence output format",
-        "Verify skill hard-codes no-claim-unless-run rule",
-        "Doctor fixture tests exist and pass",
-        "Routing eval cases exist and validate",
-        "Package-link integrity check exists"
-      ],
-      "max_score": 10.0
-    },
-    "review_process": {
-      "weight": 0.10,
-      "checks": [
-        "Review command exists and references review skill",
-        "Review skill covers standards and spec axes",
-        "Review skill has Security/Risk axis",
-        "Review findings ordered by severity",
-        "Review result ends with one of four canonical results"
-      ],
-      "max_score": 10.0
-    },
-    "release_readiness": {
-      "weight": 0.10,
-      "checks": [
-        "release:check script exists in package.json",
-        "release:check runs doctor, eval-routing, package-links",
-        "release:check runs package-manifest check",
-        "release:check runs token-budget check",
-        "release:check runs score-quality check",
-        "quality/scorecard.json defines minimum thresholds",
-        "npm pack --dry-run succeeds"
-      ],
-      "max_score": 10.0
-    }
-  }
-}

package/quality/token-budget.exceptions.json

@@ -1,13 +0,0 @@
-{
-  "_comment": "Token budget exceptions. Keys are relative file paths from project root. Values are reason + override size.",
-  "overrides": {
-    "compiled.md": {
-      "reason": "Single-file bundle doc, expected to be large",
-      "max_bytes": 819200
-    },
-    "ZOO-FLOW-BUNDLE.md": {
-      "reason": "Single-file bundle doc, expected to be large",
-      "max_bytes": 819200
-    }
-  }
-}