opencode-plugin-flow 4.1.11 → 4.1.14

package/dist/cli.js

@@ -1,11 +1,20 @@
 #!/usr/bin/env node
-import{createHash as qe}from"node:crypto";import{mkdir as Pe,readdir as te,readFile as Te,rm as De,writeFile as y}from"node:fs/promises";import{createRequire as je}from"node:module";import{dirname as Be,join as l,normalize as We,sep as Se}from"node:path";var j=`# Flow worker handoff contract
+import{createHash as De}from"node:crypto";import{mkdir as Te,readdir as oe,readFile as Pe,rm as je,writeFile as b}from"node:fs/promises";import{createRequire as Se}from"node:module";import{dirname as We,join as u,normalize as Oe,sep as Be}from"node:path";var S=`# Flow worker handoff contract
 
 Flow managers merge only the worker's final response. Treat that response as the
 worker report of record: it must include the assigned scope, what was actually
 covered, the evidence for each useful claim, and the remaining gaps. End worker
 prompts with "Return only this Flow handoff."
 
+Status meanings:
+
+- \`success\`: the assigned scope was covered, or any skipped items are explicitly
+  immaterial to the assigned question.
+- \`partial\`: useful evidence was gathered, but material assigned scope remains
+  unchecked or unresolved.
+- \`blocked\`: the worker cannot answer the assigned question without missing
+  access, input, dependencies, or manager clarification.
+
 ## Evidence, review, validation, or audit worker report
 
 Use this for \`flow-evidence-worker\`, \`flow-reviewer\`,
@@ -47,7 +56,17 @@ success | partial | blocked
 Validation workers must include exact command names and raw outcome summaries
 for commands they actually ran. Audit workers must include guards checked for
 any blocking-severity candidate. Review workers must separate blocking findings
-from advisory notes.
+from advisory notes. In the shared \`Findings or facts\` section, review workers
+should prefix review items with \`blocking:\` or \`advisory:\` before the claim.
+
+Example evidence quality:
+
+- Good fact: \`[high] public Flow command prompts include bundled instructions;
+  evidence: src/config-shared.ts:135; corroboration: single source\`.
+- Weak fact: \`[high] prompts look self-contained; evidence: read the config\`.
+- Good validation: \`bun test tests/distribution-and-surface.test.ts\`, status
+  passed, summary \`surface tests passed and covered bundled command prompts\`.
+- Weak validation: \`tests pass\`, with no command, status, or raw outcome.
 
 ## Verifier worker report
 
@@ -118,7 +137,7 @@ live-verified | test-verified | type-check-only | not-verified
 
 The manager must inspect and validate any candidate patch before recording Flow
 completion.
-`;var B=`# Parallel orchestration
+`;var W=`# Parallel orchestration
 
 Use fan-out when Flow work is broad enough that independent workers can gather
 evidence faster than one linear pass. The manager still owns the Flow session:
@@ -131,6 +150,26 @@ Read these companion references before a broad wave:
 - \`verification-gates.md\` for coverage checks, handoff acceptance, verifier
   triggers, and synthesis rules.
 
+## Operational defaults
+
+- Prefer serial work when the scope is small, tightly coupled, or blocked by one
+  decision that must be made before slices are meaningful.
+- A normal first wave is two to five workers with independent slices. Use more
+  only when the coverage gate is countable and the slices remain non-overlapping.
+- Run at most one routine follow-up wave. Extra waves need an explicit manager
+  reason, such as a high-stakes verifier check or a newly discovered bounded
+  slice.
+- Do not fan out just to keep agents busy. Every worker should reduce a known
+  planning, validation, review, audit, or implementation uncertainty.
+
+Skip fan-out when:
+
+- one file, command, or design question determines the next step.
+- slices would share the same contracts, fixtures, or edit targets.
+- the manager can inspect the full scope faster than writing and checking
+  worker prompts.
+- the result would still need the same manual synthesis with no time saved.
+
 ## Manager sequence
 
 1. Call \`flow_status\` if a Flow session may already exist.
@@ -154,9 +193,10 @@ Read these companion references before a broad wave:
    claims to \`flow-verifier-worker\`.
 9. Run second waves only for material gaps, conflicts, narrowed scope, or
    verification needs.
-10. Synthesize one Flow artifact: plan fields, completion evidence, review
-    payload, audit report, or candidate patch decision. Do not paste worker
-    handoffs as the user-facing result.
+10. Apply the manager synthesis barrier: keep only distilled, evidence-backed
+    claims and synthesize one Flow artifact, such as plan fields, completion
+    evidence, review payload, audit report, or candidate patch decision. Do not
+    paste worker handoffs as the user-facing result.
 
 ## Modes
 
@@ -174,6 +214,36 @@ carry the permission boundaries for each mode.
 | \`verifier\` | \`flow-verifier-worker\` | Per-claim verdicts against cited evidence or commands | No | \`flow_status\` only if needed |
 | \`candidate-implementation\` | \`flow-candidate-worker\` | Candidate patch summary from an isolated worktree or exact path-owned slice | Only with explicit user authorization plus isolation or exact non-overlapping path ownership | No state-changing Flow tools |
 
+Mode examples:
+
+- Use \`flow-evidence-worker\` when the repo shape is unclear and the output will
+  become plan requirements, decisions, targets, or validation entries.
+- Use \`flow-reviewer\` when changed files or risk lenses can be reviewed
+  independently before the manager returns one review payload.
+- Use \`flow-validation-worker\` when the manager needs command options or raw
+  output from an explicitly authorized command.
+- Use \`flow-audit-worker\` when candidate findings must be refuted before they
+  can become a report or follow-up feature.
+- Use \`flow-verifier-worker\` for atomic claims that are contested,
+  single-sourced, high-stakes, or destined for a Flow payload.
+- Use \`flow-candidate-worker\` only after explicit user authorization and only
+  with an isolated worktree or exact non-overlapping path ownership.
+
+## Permission contract
+
+The plugin injects these hidden workers with the following permission values.
+\`Flow state tools\` means the \`flow_*\` rule, while \`Flow status\` documents the
+explicit \`flow_status\` exception.
+
+| Worker | Edit | Bash | Task | Skill | Flow state tools | Flow status |
+| --- | --- | --- | --- | --- | --- | --- |
+| \`flow-reviewer\` | deny | deny | deny | deny | deny | allow |
+| \`flow-evidence-worker\` | deny | deny | deny | deny | deny | allow |
+| \`flow-validation-worker\` | deny | ask | deny | deny | deny | allow |
+| \`flow-audit-worker\` | deny | ask | deny | deny | deny | allow |
+| \`flow-candidate-worker\` | ask | ask | deny | deny | deny | allow |
+| \`flow-verifier-worker\` | deny | ask | deny | deny | deny | allow |
+
 Do not fan out parallel \`flow_plan_save\`, \`flow_plan_approve\`,
 \`flow_run_start\`, \`flow_feature_complete\`, \`flow_feature_reset\`, or
 \`flow_session_close\` calls. Runtime locking protects files, but Flow accepts only
@@ -209,7 +279,7 @@ Mode: evidence | review | validation | audit | verifier | candidate-implementati
 Your exact slice: <paths, modules, command, claim ids, risk lens, or worktree>
 Expected coverage: <count, paths, range, or complete question set>
 Do: <bounded actions>
-Do not: call Flow state tools, edit .flow/**, own sibling slices, or make the final Flow verdict.
+Do not: call state-changing Flow tools, edit .flow/**, own sibling slices, or make the final Flow verdict.
 Return exactly the matching handoff shape from handoff-format.md.
 \`\`\`
 
@@ -217,6 +287,71 @@ For research or current-doc slices, require source checks for versioned or
 time-sensitive facts. For implementation candidates, remind workers that other
 work may be active and that they must not revert unrelated changes.
 
+## Full-wave example
+
+Goal: review whether bundled Flow command guidance is self-contained and aligned
+with hidden worker permissions.
+
+Serial orientation: the manager reads \`src/config-shared.ts\` enough to identify
+five public command templates and six hidden worker configs. The manager keeps
+\`flow-status\` local because it is one line and does not need a worker.
+
+Coverage gate: ten countable items remain after the local check.
+
+- Slice A: \`flow-auto\`, \`flow-plan\`, and \`flow-run\` templates, expected 3/10.
+- Slice B: \`flow-review\` template plus \`flow-reviewer\` config, expected 2/10.
+- Slice C: remaining hidden worker permission blocks, expected 5/10 after
+  excluding the reviewer already covered by Slice B.
+
+Worker prompts:
+
+\`\`\`text
+Overall goal, context only: confirm Flow public commands are self-contained.
+Mode: evidence
+Your exact slice: flow-auto, flow-plan, and flow-run templates in src/config-shared.ts.
+Expected coverage: 3/3 templates.
+Do: report bundled sections, setup preflight coverage, and any gaps with file:line evidence.
+Do not: call state-changing Flow tools, edit .flow/**, own sibling slices, or make the final Flow verdict.
+Return exactly the matching handoff shape from handoff-format.md.
+\`\`\`
+
+\`\`\`text
+Overall goal, context only: confirm Flow review command and hidden reviewer behavior.
+Mode: review
+Your exact slice: flow-review command template and flow-reviewer config in src/config-shared.ts.
+Expected coverage: 2/2 surfaces.
+Do: separate blocking findings from advisory notes and cite file:line evidence.
+Do not: call state-changing Flow tools, edit .flow/**, own sibling slices, or make the final Flow verdict.
+Return exactly the matching handoff shape from handoff-format.md.
+\`\`\`
+
+\`\`\`text
+Overall goal, context only: confirm hidden worker permissions match the orchestration model.
+Mode: audit
+Your exact slice: flow-evidence-worker, flow-validation-worker, flow-audit-worker, flow-candidate-worker, and flow-verifier-worker permissions in src/config-shared.ts.
+Expected coverage: 5/5 worker permission blocks.
+Do: report edit, bash, task, skill, flow_*, and flow_status permissions with evidence.
+Do not: call state-changing Flow tools, edit .flow/**, own sibling slices, or make the final Flow verdict.
+Return exactly the matching handoff shape from handoff-format.md.
+\`\`\`
+
+Handoff checks: the manager accepts only reports with terminal status, matching
+coverage counts, concrete file:line evidence, confidence tags, and claims inside
+the assigned slice. A claim such as \`[high] validation workers may run commands;
+evidence: src/config-shared.ts:281-288; corroboration: single source\` is usable.
+A claim such as \`[high] permissions look safe; evidence: config reviewed\` is
+dropped or retasked.
+
+Verifier pass: the manager sends any single-source claim that will enter the
+Flow payload to \`flow-verifier-worker\`, for example: \`C1: validation, audit,
+candidate, and verifier workers have bash ask while evidence and review workers
+have bash deny; sources: src/config-shared.ts worker permission blocks\`.
+
+Final synthesis: the manager re-reads the relevant config lines, keeps only
+verified or clearly labeled claims, and records one artifact such as a plan
+decision, review payload, or docs patch. Raw handoffs and unverified suggestions
+do not move into the next wave or user-facing answer.
+
 ## Where handoffs go
 
 - Planning evidence becomes \`requirements\`, \`decisions\`, feature \`targets\`,
@@ -235,6 +370,10 @@ work may be active and that they must not revert unrelated changes.
 When worker results conflict, inspect the underlying artifact directly and rerun
 the smallest check that can settle the disagreement.
 
+The manager synthesis barrier means raw handoffs do not move forward by default.
+Only claims that survived coverage, evidence, confidence, and verifier checks may
+enter the next wave, Flow payload, patch decision, or user-facing answer.
+
 ## Second waves
 
 Start a follow-up wave when first-wave handoffs reveal:
@@ -247,7 +386,7 @@ Start a follow-up wave when first-wave handoffs reveal:
 
 Do not recurse by default. If a worker says it needs another worker, the manager
 decides whether that is a second wave and writes the next bounded prompt.
-`;var W='# Recovery playbook\n\nUse this when a Flow tool returns `status: "error"`, a blocker, or a `nextAction` that conflicts with memory.\n\n## First response\n\n1. Re-anchor with `flow_status`.\n2. Read the returned `summary`, `recovery`, `lastError`, and active feature.\n3. Fix the cause, then retry the smallest valid Flow action.\n\n## Common cases\n\n- `missing_session`: start with `flow_plan_save` using the user\'s goal.\n- `missing_goal`: ask for a concrete goal before planning.\n- `Approved plans cannot be changed`: use `flow_feature_reset` when only affected features need another pass; otherwise close and start a new goal.\n- `No feature is currently running`: call `flow_run_start` before completing.\n- `already in progress`: finish, reset, or block the active feature before starting another.\n- `Completion requires recorded validation evidence`: run real validation and include at least one passing `validationRun`.\n- `Completion requires all recorded validation to pass`: fix failures and rerun. Do not relabel failed checks as passed.\n- `Non-final feature completion requires targeted validation`: use `validationScope: "targeted"` for ordinary features.\n- `Final feature completion requires broad validation`: run the project-level gate and use `validationScope: "broad"`.\n- `Completion requires a passing featureReview`: run or request a real review and include a passing `featureReview` only when there are no blocking findings.\n- `Final feature completion requires a finalReview`: perform final review and include `finalReview`.\n- `Final review depth must match the plan policy`: use `reviewDepth` equal to the approved plan\'s `finalReviewPolicy`; valid final-review values are `broad` and `detailed`.\n- `Cannot close ... unfinished features`: complete, reset, defer, or abandon honestly. Do not mark completed while work remains.\n\n## Reset guidance\n\nUse `flow_feature_reset` when the active or completed work was built on the wrong assumption, validation revealed a design issue, dependencies need to be rerun, or dependent features must be invalidated. Resetting a feature also resets its dependents.\n\n## Closure guidance\n\nUse `flow_session_close`:\n\n- `completed`: only after all planned features are complete.\n- `deferred`: the user intentionally postpones unfinished work.\n- `abandoned`: the session should be archived without claiming delivery.\n\nAfter closure, the active `.flow/session.json` is removed and the archived JSON is stored under `.flow/history/`.\n';var S=`# Verification gates
+`;var O='# Recovery playbook\n\nUse this when a Flow tool returns `status: "error"`, a blocker, or a `nextAction` that conflicts with memory.\n\n## First response\n\n1. Re-anchor with `flow_status`.\n2. Read the returned `summary`, `recovery`, `lastError`, and active feature.\n3. Fix the cause, then retry the smallest valid Flow action.\n\n## Common cases\n\n- `missing_session`: start with `flow_plan_save` using the user\'s goal.\n- `missing_goal`: ask for a concrete goal before planning.\n- `Approved plans cannot be changed`: use `flow_feature_reset` when only affected features need another pass; otherwise close and start a new goal.\n- `No feature is currently running`: call `flow_run_start` before completing.\n- `already in progress`: finish, reset, or block the active feature before starting another.\n- `Completion requires recorded validation evidence`: run real validation and include at least one passing `validationRun`.\n- `Completion requires all recorded validation to pass`: fix failures and rerun. Do not relabel failed checks as passed.\n- `Non-final feature completion requires targeted validation`: use `validationScope: "targeted"` for ordinary features.\n- `Final feature completion requires broad validation`: run the project-level gate and use `validationScope: "broad"`.\n- `Completion requires a passing featureReview`: run or request a real review and include a passing `featureReview` only when there are no blocking findings.\n- `Final feature completion requires a finalReview`: perform final review and include `finalReview`.\n- `Final review depth must match the plan policy`: use `reviewDepth` equal to the approved plan\'s `finalReviewPolicy`; valid final-review values are `broad` and `detailed`.\n- `Cannot close ... unfinished features`: complete, reset, defer, or abandon honestly. Do not mark completed while work remains.\n\n## Reset guidance\n\nUse `flow_feature_reset` when the active or completed work was built on the wrong assumption, validation revealed a design issue, dependencies need to be rerun, or dependent features must be invalidated. Resetting a feature also resets its dependents.\n\n## Closure guidance\n\nUse `flow_session_close`:\n\n- `completed`: only after all planned features are complete.\n- `deferred`: the user intentionally postpones unfinished work.\n- `abandoned`: the session should be archived without claiming delivery.\n\nAfter closure, the active `.flow/session.json` is removed and the archived JSON is stored under `.flow/history/`.\n';var B=`# Verification gates
 
 Verification is how Flow keeps parallel work from turning into parallel
 guesswork. Worker handoffs are candidate evidence; the manager decides what can
@@ -322,7 +461,7 @@ Candidate implementation patches are not Flow evidence until the manager
 inspects, merges or rejects them, and runs suitable validation in the main
 Flow-managed workspace.
 
-## Final synthesis
+## Manager synthesis barrier
 
 Before presenting or recording the result:
 
@@ -332,6 +471,8 @@ Before presenting or recording the result:
   instead of arbitrating from summaries.
 - Run the strongest practical local check for the deliverable.
 - Re-read critical files or docs that will be cited in the final decision.
+- Move only distilled, evidence-backed claims forward; raw handoffs remain
+  candidate evidence, not a plan, review, completion payload, or final answer.
 - Record gaps honestly instead of converting missing evidence into success
   language.
 
@@ -350,10 +491,11 @@ Use Flow as a minimal state ledger, not as a framework. Skills provide judgment;
 
 1. Call \`flow_status\` first. Trust its active session and next action over conversation memory.
    If the result includes \`setup.skills\`, report that setup status and do not
-   load Flow skills in this startup. A just-synced skill can be on disk while
-   unavailable to the running OpenCode process.
+   native-load Flow skills in this startup. Public bundled Flow commands may
+   continue with their embedded instructions, but a just-synced native skill can
+   be on disk while unavailable to the running OpenCode process.
 2. If there is no active session and the user gave a goal, load \`flow-plan\`, save a plan with \`flow_plan_save\`, then approve it with \`flow_plan_approve\` only after explicit user approval or prior authorization for autonomous implementation. If there is no goal, ask for one.
-3. Load \`flow-run\`, call \`flow_run_start\`, implement exactly one feature, validate it, and prepare a \`flow_feature_complete\` payload. For validation-heavy, regression-sensitive, or browser/UI work, use \`flow-test\` to choose and summarize evidence before completion.
+3. Load \`flow-run\`, call \`flow_run_start\`, implement exactly one feature, validate it, and prepare a \`flow_feature_complete\` payload. For validation-heavy, regression-sensitive, browser QA, route QA, or failure-prone work, use \`flow-test\` to choose and summarize evidence before completion.
 4. Load \`flow-review\` for the required feature review. The reviewer reports a \`featureReview\` payload; the manager records it inside \`flow_feature_complete\`.
 5. On the final feature, run broad validation and include \`finalReview\` in the same \`flow_feature_complete\` call. Its \`reviewDepth\` must match the plan's \`finalReviewPolicy\`.
 6. After all features are complete, archive the session with \`flow_session_close\` using \`kind: "completed"\`.
@@ -367,9 +509,11 @@ commit preparation or commit creation.
 ## Skill Availability
 
 If \`flow_status\` returns \`setup.skills\`, report that setup status and stop
-loading Flow skills in the current OpenCode startup. Missing, incomplete, or
-outdated managed skills require a sync/restart cycle before their instructions
-can be trusted by the running process.
+native-loading Flow skills in the current OpenCode startup. Missing, incomplete,
+or outdated managed skills require a sync/restart cycle before their native skill
+instructions can be trusted by the running process. Public command bundles are
+self-contained and may continue when the command prompt already embeds the
+required Flow instructions.
 
 If optional helper skills such as \`flow-test\`, \`flow-deslop\`, or
 \`flow-ui-quality\` are unavailable, continue only with explicit coverage gaps. Do
@@ -409,7 +553,7 @@ Planning and running require loaded Flow tools; do not simulate plan approval or
 - Unknown runtime error: read \`summary\` and \`recovery\`; see \`references/recovery-playbook.md\` for common cases.
 
 Never fabricate validation output, backfill review approval you did not perform, or close as \`deferred\`/\`abandoned\` merely to avoid an unfinished-work blocker.
-`;var O=`---
+`;var E=`---
 name: flow-commit
 description: Prepare safe Git commits and commit messages. Use only when the user asks to inspect, stage, validate, write a commit message, or create a commit; preserves unrelated work and never pushes, amends, rebases, or publishes without explicit authorization.
 ---
@@ -482,21 +626,23 @@ Before commit creation, check the staged diff for:
 - Package or version metadata drift unrelated to the requested change.
 
 When this repository-local contribution preflight exists, defer to it for staged
-and outgoing validation instead of duplicating its checks:
+or outgoing validation instead of duplicating its checks:
 
 \`\`\`bash
 .agents/skills/flow-contribution-check/scripts/preflight.sh commit
 \`\`\`
 
-Run it after staging and rerun it after any staging change. The preflight
-validates staged or outgoing work; it does not choose commit boundaries or write
-commit messages. If the script is absent, use the repository's documented commit
+Run it after staging and rerun it after any staging change. Commit mode validates
+the staged boundary for diff hygiene, staged review, and staged secret screening;
+it does not run a whole-worktree gate, choose commit boundaries, or write commit
+messages. If the script is absent, use the repository's documented commit
 preflight from package scripts, AGENTS/docs, or CI guidance.
 
 Use the repository's documented broad validation gate when a full local check is
-appropriate, such as package scripts, AGENTS/docs, or CI guidance. Use narrower
-tests only when the user has asked for a lighter pass or when the change is
-intentionally not ready for the broad gate.
+appropriate, such as package scripts, AGENTS/docs, or CI guidance. Treat broad
+checks as whole-worktree evidence unless the repository explicitly provides a
+staged-content runner. Use narrower tests only when the user has asked for a
+lighter pass or when the change is intentionally not ready for the broad gate.
 
 ## Message
 
@@ -523,7 +669,7 @@ Before running \`git commit\`, report:
 
 After a successful commit, report the commit hash and leave push or release
 actions for a separate explicit request.
-`;var E=`# Safe refactor workflow
+`;var N=`# Safe refactor workflow
 
 Refactoring is a behavior-preserving sequence of small changes. This workflow keeps cleanup from becoming an unreviewable rewrite.
 
@@ -565,7 +711,7 @@ Weak evidence includes:
 - Public contracts and compatibility shims remain intact or were explicitly planned.
 - Deleted code is actually unreachable or obsolete.
 - Validation can catch a realistic mistake in the refactor.
-`;var N=`# Deslop smell rubric
+`;var G=`# Deslop smell rubric
 
 Use this rubric to turn vague cleanup instincts into reviewable findings.
 
@@ -641,7 +787,7 @@ For each claimed smell removal, verify:
 - **blast radius** — public contracts and downstream callers still work.
 
 Never approve cleanup because it "looks cleaner" without evidence. Tests passing is necessary but not sufficient when the refactor changes structure across files.
-`;var G=`# Parallel discovery
+`;var M=`# Parallel discovery
 
 Use this only after a serial orientation pass has identified the repo shape and the likely slices. Workers are read-only evidence gatherers; the planner owns the plan.
 
@@ -674,6 +820,10 @@ For this repository, good first-wave slices are:
   \`bun.lock\`, \`README.md\`, and \`CHANGELOG.md\`.
 - Docs and operator contract: \`docs/**\`, \`README.md\`, and skill references.
 
+Treat these as starting points, not a simultaneous coverage map. Before fan-out,
+choose the relevant entries and de-overlap shared docs, skills, or release
+surfaces in the coverage gate.
+
 ## Coverage gate
 
 Before spawning workers, state the total discovery scope and one line per slice.
@@ -684,17 +834,19 @@ state the completeness rule, such as "all changed files plus callers."
 ## Worker prompt
 
 \`\`\`text
-Inspect <slice> for <goal>. Read-only. Do not edit files or call Flow tools.
-Return the evidence/review/validation/audit handoff shape from ../../flow/references/handoff-format.md.
+Inspect <slice> for <goal>. Read-only. Do not edit files or call
+state-changing Flow tools. Return the evidence/review/validation/audit handoff
+shape from ../../flow/references/handoff-format.md.
 \`\`\`
 
 For validation-oriented discovery:
 
 \`\`\`text
-Inspect <slice> for validation risk. Read-only. Do not edit files or call Flow
-tools. You may report commands that should be run, and include raw output only
-for commands you actually ran. Return the evidence/review/validation/audit
-handoff shape from ../../flow/references/handoff-format.md.
+Inspect <slice> for validation risk. Read-only. Do not edit files or call
+state-changing Flow tools. You may report commands that should be run, and
+include raw output only for commands you actually ran. Return the
+evidence/review/validation/audit handoff shape from
+../../flow/references/handoff-format.md.
 \`\`\`
 
 ## Synthesis
@@ -707,6 +859,10 @@ Convert only evidence-backed work into plan fields:
 - feature \`validation\`: checks expected to prove the feature.
 
 If workers disagree, inspect the source artifact yourself. If a candidate finding lacks a concrete citation or refutation pass, make it a review-first deliverable rather than a fix feature.
+
+Apply the manager synthesis barrier from
+\`../../flow/references/verification-gates.md\`: only distilled, evidence-backed
+claims become plan fields.
 `;var L=`# Planning examples
 
 ## Rate limiting feature set
@@ -792,7 +948,7 @@ Better plan:
 - Validation that only says "manual testing".
 - Targets that name the entire repo.
 - Features with hidden dependencies instead of \`dependsOn\`.
-`;var M=`---
+`;var $=`---
 name: flow-plan
 description: Plan Flow work for the v4 skills-first runtime: inspect the repo, decompose a user goal into right-sized features, save a draft with flow_plan_save, and approve it with flow_plan_approve.
 ---
@@ -807,9 +963,9 @@ If \`flow_plan_save\` or \`flow_plan_approve\` is unavailable, stop and tell the
 
 - Read the files, docs, tests, package scripts, and local conventions that determine the work.
 - For broad discovery, read \`references/parallel-discovery.md\` after a serial orientation pass. Use \`../flow/references/parallel-orchestration.md\` when discovery needs multiple workers, and apply its coverage gate before fan-out.
-- For complex validation, regression-sensitive changes, browser/UI workflows,
-  or uncertain test strategy, load \`flow-test\`. If it is unavailable, record a
-  planning gap and keep validation claims conservative.
+- For complex validation, regression-sensitive changes, browser QA, route QA,
+  failure-prone checks, or uncertain test strategy, load \`flow-test\`. If it is
+  unavailable, record a planning gap and keep validation claims conservative.
 - For cleanup/refactor goals, load \`flow-deslop\`. If it is unavailable, record
   a planning gap and keep cleanup claims conservative.
 - For UI/frontend goals, load \`flow-ui-quality\`. If it is unavailable, record a
@@ -862,7 +1018,7 @@ Use only \`finalReviewPolicy: "broad"\` or \`"detailed"\`. These are the canonic
 After saving, summarize the plan to the user. Call \`flow_plan_approve\` only after explicit user approval, unless the user already authorized autonomous implementation. Approved plans are immutable; changing them later requires reset/closure rather than silent edits.
 
 See \`references/planning-examples.md\` for payload examples and decomposition anti-patterns.
-`;var K=`# Review rubric
+`;var Q=`# Review rubric
 
 Use this to decide whether a \`featureReview\` or \`finalReview\` payload may pass.
 
@@ -950,7 +1106,7 @@ When reviewing a findings report, verify findings adversarially:
 - Downgrade or reject findings that do not survive refutation.
 
 Approve only on evidence actually inspected. A review is a claim of coverage, not a courtesy stamp.
-`;var $=`---
+`;var K=`---
 name: flow-review
 description: Review Flow work in the v4 runtime: inspect feature or final-session changes, classify findings, and return featureReview or finalReview payloads for flow_feature_complete.
 ---
@@ -969,7 +1125,7 @@ recorded.
 - Identify whether this is a feature review or final review.
 - Read the approved plan fields relevant to the work: \`requirements\`, \`decisions\`, feature \`targets\`, feature \`validation\`, and dependencies.
 - Inspect the actual diff, changed files, tests, and validation output. Do not review only the completion summary.
-- Load \`flow-test\` for validation-heavy, regression-sensitive, browser/UI, or
+- Load \`flow-test\` for validation-heavy, regression-sensitive, browser QA, or
   unclear coverage reviews. If it is unavailable, record a coverage gap and
   treat missing validation evidence as a gap or blocker based on user impact.
 - Load \`references/review-rubric.md\` for severity, depth, and payload shape.
@@ -1011,7 +1167,7 @@ Use \`status: "failed"\` when any blocking finding remains. Advisory findings ma
 
 - Cleanup/refactor: load \`flow-deslop\`; verify the smell was real, refutation paths were checked, and behavior was preserved. If unavailable, record a coverage gap instead of approving cleanup claims.
 - UI/frontend: load \`flow-ui-quality\`; verify state coverage and visual evidence when a local target was available. If unavailable, record a coverage gap and do not claim visual polish was verified.
-- Audit reports: use \`flow-run/references/audit-rubric.md\`; findings must survive refutation before they can drive fix features.
+- Audit reports: use \`../flow-run/references/audit-rubric.md\`; findings must survive refutation before they can drive fix features.
 - Large reviews: use \`../flow/references/parallel-orchestration.md\` for
   read-only slices by changed-file group, risk lens, or validation surface.
   Use the named review, audit, evidence, or validation agents from that
@@ -1020,7 +1176,7 @@ Use \`status: "failed"\` when any blocking finding remains. Advisory findings ma
   \`finalReview\` payload.
 
 Never approve to unblock completion, fix findings in the review pass, or vouch for validation you did not inspect.
-`;var Q=`# Audit findings rubric
+`;var Y=`# Audit findings rubric
 
 What counts as a valid finding when the feature's deliverable is a findings report: a codebase audit, a review-first feature, or any report whose findings a later feature will fix. The commands you run are still governed by \`validation-rubric.md\`; this rubric governs the findings themselves.
 
@@ -1130,7 +1286,7 @@ Broad validation usually means the repo's full check command, full relevant test
 - If validation needs external access, missing credentials, or ambiguous user input, record \`status: "needs_input"\` with an honest \`outcome\`.
 
 Never trim failing output, relabel a failed command as passed, or use "not run" as completion evidence.
-`;var Y=`---
+`;var J=`---
 name: flow-run
 description: Execute one approved Flow feature in the v4 runtime: start a feature with flow_run_start, make scoped changes, gather real validation evidence, obtain review payloads, and complete with flow_feature_complete.
 ---
@@ -1164,8 +1320,8 @@ If \`flow_run_start\` is unavailable, stop and tell the user to check that \`ope
 
 ## Validate
 
-- For complex validation, regression-sensitive changes, browser/UI workflows,
-  failure-prone checks, unclear coverage, route QA, exploratory QA, or
+- For complex validation, regression-sensitive changes, browser QA, route QA,
+  failure-prone checks, unclear coverage, exploratory QA, or
   \`validationRun\` summarization, load \`flow-test\`. If it is unavailable, record
   the coverage gap and keep validation claims conservative.
 - Read \`references/validation-rubric.md\` before completing.
@@ -1217,7 +1373,7 @@ Complete with:
 \`\`\`
 
 If genuinely blocked, call \`flow_feature_complete\` with \`status: "needs_input"\` and an \`outcome\` that explains the blocker and next step. Never fabricate validation or review evidence to force progress.
-`;var J=`---
+`;var Z=`---
 name: flow-test
 description: Test, validate, make test plans, triage failures, and gather Flow validation evidence. Use when selecting checks, running tests, running browser QA for UI changes, classifying failures, or preparing validationRun evidence for flow_feature_complete.
 ---
@@ -1341,7 +1497,7 @@ covered. Static inspection alone is a gap for behavioral changes.
 
 Never relabel a failed command as passed, invent output, or use "not run" as
 completion evidence.
-`;var Z=`# UI quality rubric
+`;var H=`# UI quality rubric
 
 Use this rubric for frontend planning, implementation, and review.
 
@@ -1385,7 +1541,7 @@ class; severity; location or screenshot area; evidence inspected; user impact; f
 \`\`\`
 
 Blocking UI findings are issues that prevent task completion, hide required information, break accessibility basics, create incoherent layout at supported sizes, or make the visual success claim unverifiable.
-`;var H=`# Visual verification workflow
+`;var ee=`# Visual verification workflow
 
 Use this workflow when UI changes can be run locally. Flow execution may create visual evidence; Flow review usually assesses recorded evidence because the reviewer is read-only.
 
@@ -1425,7 +1581,7 @@ Record the reason and use the strongest available substitute:
 - code inspection against existing component patterns.
 
 Do not claim visual polish was verified if no visual artifact was inspected.
-`;var ee=`---
+`;var ae=`---
 name: flow-ui-quality
 description: Review and improve frontend UI quality for Flow work. Use for UX/UI design, frontend polish, visual quality review, responsive and accessible interfaces, interaction states, screenshots, browser-verified UI work, and avoiding generic AI-generated UI.
 ---
@@ -1473,16 +1629,23 @@ Approve only when the interface is both useful and inspectable:
 - Screenshot/browser evidence supports the claim whenever feasible.
 
 Never approve a UI change based only on code shape. If users will judge it visually, Flow evidence should include visual inspection.
-`;var w=[{name:"flow",files:[{relativePath:"SKILL.md",content:z},{relativePath:"references/recovery-playbook.md",content:W},{relativePath:"references/parallel-orchestration.md",content:B},{relativePath:"references/handoff-format.md",content:j},{relativePath:"references/verification-gates.md",content:S}]},{name:"flow-plan",files:[{relativePath:"SKILL.md",content:M},{relativePath:"references/planning-examples.md",content:L},{relativePath:"references/parallel-discovery.md",content:G}]},{name:"flow-run",files:[{relativePath:"SKILL.md",content:Y},{relativePath:"references/validation-rubric.md",content:X},{relativePath:"references/audit-rubric.md",content:Q}]},{name:"flow-test",files:[{relativePath:"SKILL.md",content:J}]},{name:"flow-review",files:[{relativePath:"SKILL.md",content:$},{relativePath:"references/review-rubric.md",content:K}]},{name:"flow-deslop",files:[{relativePath:"SKILL.md",content:V},{relativePath:"references/smell-rubric.md",content:N},{relativePath:"references/refactor-workflow.md",content:E}]},{name:"flow-ui-quality",files:[{relativePath:"SKILL.md",content:ee},{relativePath:"references/ui-rubric.md",content:Z},{relativePath:"references/visual-verification.md",content:H}]},{name:"flow-commit",files:[{relativePath:"SKILL.md",content:O}]}];var C=".flow-skill-version";function x(){return process.env.HOME??process.env.USERPROFILE??""}function A(e=x()){return l(e,".config","opencode","skills")}function _(e){return qe("sha256").update(e).digest("hex")}function b(e,a){return[`version=${a}`,...e.files.map((t)=>`file=${t.relativePath} sha256=${_(t.content)}`),""].join(`
-`)}async function f(e){try{return await Te(e,"utf8")}catch(a){if(a.code==="ENOENT")return null;throw a}}function q(e){let a=new Map;if(!e)return a;for(let t of e.split(/\r?\n/)){let r=/^file=(.+) sha256=([a-f0-9]{64})$/.exec(t)??/^file=(.+)=sha256:([a-f0-9]{64})$/.exec(t);if(r?.[1]&&r[2])a.set(r[1],r[2]);let s=/^hash=sha256:([a-f0-9]{64})$/.exec(t);if(s?.[1]&&!a.has("SKILL.md"))a.set("SKILL.md",s[1])}return a}function ze(e){if(!e)return null;for(let a of e.split(/\r?\n/)){let t=/^version=(.+)$/.exec(a);if(t?.[1])return t[1]}return null}function k(e,a){let t=We(l(e,...a.split("/")));if(t!==e&&t.startsWith(`${e}${Se}`))return t;throw Error(`Unsafe skill file path '${a}'.`)}async function Oe(e,a,t){let r=l(t,e.name),s=l(r,C),n=await f(s),d=q(n);if(await f(l(r,"SKILL.md"))!==null&&n===null)return{name:e.name,action:"skipped_foreign"};let p=!1,m=!1;for(let o of e.files){let i=k(r,o.relativePath),u=await f(i);if(u===o.content)continue;p=!0;let v=d.get(o.relativePath);if(u!==null&&(v?_(u)!==v:n!==null))await y(`${i}.backup`,u,"utf8"),m=!0}if(!p&&n===b(e,a))return{name:e.name,action:"unchanged"};if(!p)return await y(s,b(e,a),"utf8"),{name:e.name,action:"marker_updated"};let g=n!==null;for(let o of e.files){let i=k(r,o.relativePath);await Pe(Be(i),{recursive:!0}),await y(i,o.content,"utf8")}return await y(s,b(e,a),"utf8"),{name:e.name,action:m?"updated_with_backup":g?"updated":"installed"}}function Ee(){return w.map((e)=>e.name)}function Ne(e){return`npx -y opencode-plugin-flow@${e} doctor`}function P(){if(process.env.npm_package_version)return process.env.npm_package_version;try{let e=je(import.meta.url);for(let a of["../package.json","../../package.json"])try{let t=e(a);if(t.version)return t.version}catch{}}catch{}return"0.0.0"}async function oe(e,a=x()){let t=A(a);return Promise.all(w.map((r)=>Oe(r,e,t)))}async function re(e=P(),a=x()){let t=A(a),r=new Set(Ee()),s=await Promise.all(w.map(async(o)=>{let i=l(t,o.name),u=await f(l(i,C)),v=ze(u),T=q(u);if(await f(l(i,"SKILL.md"))===null)return{name:o.name,path:i,status:"missing",markerVersion:v,missingFiles:o.files.map((h)=>h.relativePath),editedFiles:[],outdatedFiles:[]};if(u===null)return{name:o.name,path:i,status:"foreign",markerVersion:v,missingFiles:[],editedFiles:[],outdatedFiles:[]};let I=[],R=[],F=[];for(let h of o.files){let U=await f(k(i,h.relativePath));if(U===null){I.push(h.relativePath);continue}if(U===h.content)continue;let D=T.get(h.relativePath);if(D&&_(U)!==D){R.push(h.relativePath);continue}F.push(h.relativePath)}let ie=u!==b(o,e),ce=I.length>0?"incomplete":R.length>0?"edited":ie||F.length>0?"outdated":"ok";return{name:o.name,path:i,status:ce,markerVersion:v,missingFiles:I,editedFiles:R,outdatedFiles:F}})),n=[];try{n=await te(t)}catch(o){if(o.code!=="ENOENT")throw o}let d=n.filter((o)=>(o==="flow"||o.startsWith("flow-"))&&!r.has(o)).map((o)=>l(t,o)),c=s.filter((o)=>["missing","incomplete","outdated"].includes(o.status)).map((o)=>o.name),p=s.filter((o)=>["foreign","edited"].includes(o.status)).map((o)=>o.name),m=p.length>0,g=c.length>0;return{status:m?"action_required":g?"sync_required":"ok",version:e,root:t,expectedSkills:[...r],skills:s,syncRequiredSkills:c,actionRequiredSkills:p,unmanagedFlowSkills:d}}function ae(e,a,t){if(t.length===0)return;e.push(`- ${a}: ${t.join(", ")}`)}function se(e){let a=["Flow doctor",`- status: ${e.status}`,`- plugin version: ${e.version}`,`- skills root: ${e.root}`,`- expected skills: ${e.expectedSkills.join(", ")}`];ae(a,"startup sync can install/update",e.syncRequiredSkills),ae(a,"needs user decision",e.actionRequiredSkills),a.push("","Skills:");for(let t of e.skills){if(a.push(`- ${t.name}: ${t.status} (${t.path})${t.markerVersion?` marker=${t.markerVersion}`:""}`),t.missingFiles.length>0)a.push(`  missing: ${t.missingFiles.join(", ")}`);if(t.editedFiles.length>0)a.push(`  edited: ${t.editedFiles.join(", ")}`);if(t.outdatedFiles.length>0)a.push(`  outdated: ${t.outdatedFiles.join(", ")}`)}if(e.unmanagedFlowSkills.length>0){a.push("","Unmanaged Flow-like skill folders:");for(let t of e.unmanagedFlowSkills)a.push(`- ${t}`)}if(a.push("","Recommendation:"),e.status==="ok")a.push("- Flow skills are present and current.");else if(e.status==="sync_required")a.push("- Start or restart OpenCode with opencode-plugin-flow enabled so startup sync can install or update the listed skills. If Flow then reports restart_required, restart OpenCode once more so the refreshed skill registry is used.");else a.push("- Resolve user-owned or edited managed skill folders, then restart OpenCode. Move a folder aside to let Flow recreate it, or keep it intentionally as a local override.");return a.push(`- Details command: ${Ne(e.version)}`),`${a.join(`
+`;var y=[{name:"flow",files:[{relativePath:"SKILL.md",content:z},{relativePath:"references/recovery-playbook.md",content:O},{relativePath:"references/parallel-orchestration.md",content:W},{relativePath:"references/handoff-format.md",content:S},{relativePath:"references/verification-gates.md",content:B}]},{name:"flow-plan",files:[{relativePath:"SKILL.md",content:$},{relativePath:"references/planning-examples.md",content:L},{relativePath:"references/parallel-discovery.md",content:M}]},{name:"flow-run",files:[{relativePath:"SKILL.md",content:J},{relativePath:"references/validation-rubric.md",content:X},{relativePath:"references/audit-rubric.md",content:Y}]},{name:"flow-test",files:[{relativePath:"SKILL.md",content:Z}]},{name:"flow-review",files:[{relativePath:"SKILL.md",content:K},{relativePath:"references/review-rubric.md",content:Q}]},{name:"flow-deslop",files:[{relativePath:"SKILL.md",content:V},{relativePath:"references/smell-rubric.md",content:G},{relativePath:"references/refactor-workflow.md",content:N}]},{name:"flow-ui-quality",files:[{relativePath:"SKILL.md",content:ae},{relativePath:"references/ui-rubric.md",content:H},{relativePath:"references/visual-verification.md",content:ee}]},{name:"flow-commit",files:[{relativePath:"SKILL.md",content:E}]}];var q=".flow-skill-version";function _(){return process.env.HOME??process.env.USERPROFILE??""}function D(e=_()){return u(e,".config","opencode","skills")}function g(e){return De("sha256").update(e).digest("hex")}function k(e,a){return[`version=${a}`,...e.files.map((t)=>`file=${t.relativePath} sha256=${g(t.content)}`),""].join(`
+`)}async function m(e){try{return await Pe(e,"utf8")}catch(a){if(a.code==="ENOENT")return null;throw a}}function T(e){let a=new Map;if(!e)return a;for(let t of e.split(/\r?\n/)){let r=/^file=(.+) sha256=([a-f0-9]{64})$/.exec(t)??/^file=(.+)=sha256:([a-f0-9]{64})$/.exec(t);if(r?.[1]&&r[2])a.set(r[1],r[2]);let n=/^hash=sha256:([a-f0-9]{64})$/.exec(t);if(n?.[1]&&!a.has("SKILL.md"))a.set("SKILL.md",n[1])}return a}function ze(e){if(!e)return null;for(let a of e.split(/\r?\n/)){let t=/^version=(.+)$/.exec(a);if(t?.[1])return t[1]}return null}function x(e,a){let t=Oe(u(e,...a.split("/")));if(t!==e&&t.startsWith(`${e}${Be}`))return t;throw Error(`Unsafe skill file path '${a}'.`)}async function Ee(e,a){let t=`${e}.backup.${g(a).slice(0,12)}`;for(let r=0;;r+=1){let n=r===0?t:`${t}.${r}`;try{return await b(n,a,{encoding:"utf8",flag:"wx"}),n}catch(s){if(s.code==="EEXIST")continue;throw s}}}async function Ne(e,a,t){let r=u(t,e.name),n=u(r,q),s=await m(n),d=T(s);if(await m(u(r,"SKILL.md"))!==null&&s===null)return{name:e.name,action:"skipped_foreign"};let i=!1,l=[];for(let o of e.files){let c=x(r,o.relativePath),h=await m(c);if(h===o.content)continue;i=!0;let v=d.get(o.relativePath);if(h!==null&&(v?g(h)!==v:s!==null))l.push(await Ee(c,h))}if(!i&&s===k(e,a))return{name:e.name,action:"unchanged"};if(!i)return await b(n,k(e,a),"utf8"),{name:e.name,action:"marker_updated"};let w=s!==null;for(let o of e.files){let c=x(r,o.relativePath);await Te(We(c),{recursive:!0}),await b(c,o.content,"utf8")}return await b(n,k(e,a),"utf8"),{name:e.name,action:l.length>0?"updated_with_backup":w?"updated":"installed",...l.length>0?{backupPaths:l}:{}}}function Ge(){return y.map((e)=>e.name)}function Ve(e){return`npx -y opencode-plugin-flow@${e} doctor`}function I(){if(process.env.npm_package_version)return process.env.npm_package_version;try{let e=Se(import.meta.url);for(let a of["../package.json","../../package.json"])try{let t=e(a);if(t.version)return t.version}catch{}}catch{}return"0.0.0"}async function re(e,a=_()){let t=D(a);return Promise.all(y.map((r)=>Ne(r,e,t)))}async function se(e=I(),a=_()){let t=D(a),r=new Set(Ge()),n=await Promise.all(y.map(async(o)=>{let c=u(t,o.name),h=await m(u(c,q)),v=ze(h),P=T(h);if(await m(u(c,"SKILL.md"))===null)return{name:o.name,path:c,status:"missing",markerVersion:v,missingFiles:o.files.map((f)=>f.relativePath),editedFiles:[],outdatedFiles:[]};if(h===null)return{name:o.name,path:c,status:"foreign",markerVersion:v,missingFiles:[],editedFiles:[],outdatedFiles:[]};let R=[],U=[],C=[];for(let f of o.files){let A=await m(x(c,f.relativePath));if(A===null){R.push(f.relativePath);continue}if(A===f.content)continue;let j=P.get(f.relativePath);if(j&&g(A)!==j){U.push(f.relativePath);continue}C.push(f.relativePath)}let ce=h!==k(o,e),de=R.length>0?"incomplete":U.length>0?"edited":ce||C.length>0?"outdated":"ok";return{name:o.name,path:c,status:de,markerVersion:v,missingFiles:R,editedFiles:U,outdatedFiles:C}})),s=[];try{s=await oe(t)}catch(o){if(o.code!=="ENOENT")throw o}let d=s.filter((o)=>(o==="flow"||o.startsWith("flow-"))&&!r.has(o)).map((o)=>u(t,o)),p=n.filter((o)=>["missing","incomplete","outdated"].includes(o.status)).map((o)=>o.name),i=n.filter((o)=>["foreign","edited"].includes(o.status)).map((o)=>o.name),l=i.length>0,w=p.length>0;return{status:l?"action_required":w?"sync_required":"ok",version:e,root:t,expectedSkills:[...r],skills:n,syncRequiredSkills:p,actionRequiredSkills:i,unmanagedFlowSkills:d}}function te(e,a,t){if(t.length===0)return;e.push(`- ${a}: ${t.join(", ")}`)}function ne(e){let a=["Flow doctor",`- status: ${e.status}`,`- plugin version: ${e.version}`,`- skills root: ${e.root}`,`- expected skills: ${e.expectedSkills.join(", ")}`];te(a,"startup sync can install/update",e.syncRequiredSkills),te(a,"needs user decision",e.actionRequiredSkills),a.push("","Skills:");for(let t of e.skills){if(a.push(`- ${t.name}: ${t.status} (${t.path})${t.markerVersion?` marker=${t.markerVersion}`:""}`),t.missingFiles.length>0)a.push(`  missing: ${t.missingFiles.join(", ")}`);if(t.editedFiles.length>0)a.push(`  edited: ${t.editedFiles.join(", ")}`);if(t.outdatedFiles.length>0)a.push(`  outdated: ${t.outdatedFiles.join(", ")}`)}if(e.unmanagedFlowSkills.length>0){a.push("","Unmanaged Flow-like skill folders:");for(let t of e.unmanagedFlowSkills)a.push(`- ${t}`)}if(a.push("","Recommendation:"),e.status==="ok")a.push("- Flow skills are present and current.");else if(e.status==="sync_required")a.push("- Start or restart OpenCode with opencode-plugin-flow enabled so startup sync can install or update the listed skills. If Flow then reports restart_required, restart OpenCode once more so the refreshed skill registry is used.");else a.push("- Resolve user-owned or edited managed skill folders, then restart OpenCode. Move a folder aside to let Flow recreate it, or keep it intentionally as a local override.");return a.push(`- Details command: ${Ve(e.version)}`),`${a.join(`
 `)}
-`}async function ne(e=x()){let a=A(e),t=[],r=[],s;try{s=await te(a)}catch(n){if(n.code==="ENOENT")return{removed:t,kept:r};throw n}for(let n of s){if(n!=="flow"&&!n.startsWith("flow-"))continue;let d=l(a,n),c=await f(l(d,C));if(c===null){r.push(d);continue}let p=q(c),m=!1;for(let[g,o]of p){let i=await f(k(d,g));if(i!==null&&_(i)!==o){m=!0;break}}if(m){r.push(d);continue}await De(d,{recursive:!0,force:!0}),t.push(d)}return{removed:t,kept:r}}async function Ve(e){let a=e[2];if(a!=="uninstall"&&a!=="doctor"&&a!=="sync"){process.stderr.write(`usage: opencode-plugin-flow <doctor|sync|uninstall>
-`),process.exitCode=2;return}if(a==="doctor"){process.stdout.write(se(await re()));return}if(a==="sync"){let r=P(),s=await oe(r),n=s.filter((c)=>["installed","updated","updated_with_backup"].includes(c.action)),d=s.filter((c)=>c.action==="skipped_foreign");process.stdout.write(`Flow skill sync (${r})
-`);for(let c of s)process.stdout.write(`- ${c.name}: ${c.action}
-`);if(n.length>0)process.stdout.write(`Restart OpenCode so the refreshed skill registry is used.
-`);if(d.length>0)process.stdout.write(`Some managed skill folders are user-owned or edited; run doctor for repair guidance.
-`);return}let t=await ne();for(let r of t.removed)process.stdout.write(`Removed Flow skill: ${r}
-`);for(let r of t.kept)process.stdout.write(`Kept non-Flow or user-edited skill: ${r}
+`}async function ie(e=_()){let a=D(e),t=[],r=[],n;try{n=await oe(a)}catch(s){if(s.code==="ENOENT")return{removed:t,kept:r};throw s}for(let s of n){if(s!=="flow"&&!s.startsWith("flow-"))continue;let d=u(a,s),p=await m(u(d,q));if(p===null){r.push(d);continue}let i=T(p),l=!1;for(let[w,o]of i){let c=await m(x(d,w));if(c!==null&&g(c)!==o){l=!0;break}}if(l){r.push(d);continue}await je(d,{recursive:!0,force:!0}),t.push(d)}return{removed:t,kept:r}}function F(){return["usage: opencode-plugin-flow <doctor|sync|uninstall> [options]","","commands:","  doctor              Inspect managed Flow skills","  sync                Install or refresh managed Flow skills","  uninstall           Remove pristine Flow-owned managed skills","","doctor options:","  --json              Write the doctor report as JSON","  --check, --strict   Exit nonzero when doctor status is not ok","","global options:","  --help              Show this help","  --version           Print the plugin version"].join(`
+`)}function Me(e,a){return e.every((t)=>a.has(t))}function Le(e,a){if(a.json){process.stdout.write(`${JSON.stringify(e,null,2)}
+`);return}process.stdout.write(ne(e))}async function $e(e){let a=e[2],t=e.slice(3);if(a==="--help"||a==="-h"){process.stdout.write(`${F()}
+`);return}if(a==="--version"||a==="-v"){process.stdout.write(`${I()}
+`);return}if(a!=="uninstall"&&a!=="doctor"&&a!=="sync"){process.stderr.write(`${F()}
+`),process.exitCode=2;return}if(a==="doctor"){if(!Me(t,new Set(["--json","--check","--strict"]))){process.stderr.write(`${F()}
+`),process.exitCode=2;return}let s=await se();if(Le(s,{json:t.includes("--json")}),(s.status==="sync_required"||s.status==="action_required")&&(t.includes("--check")||t.includes("--strict")))process.exitCode=1;return}if(t.length>0){process.stderr.write(`${F()}
+`),process.exitCode=2;return}if(a==="sync"){let n=I(),s=await re(n),d=s.filter((i)=>["installed","updated","updated_with_backup"].includes(i.action)),p=s.filter((i)=>i.action==="skipped_foreign");process.stdout.write(`Flow skill sync (${n})
+`);for(let i of s){process.stdout.write(`- ${i.name}: ${i.action}
+`);for(let l of i.backupPaths??[])process.stdout.write(`  backup: ${l}
+`)}if(d.length>0)process.stdout.write(`Restart OpenCode so the refreshed skill registry is used.
+`);if(p.length>0)process.stdout.write(`Some managed skill folders are user-owned or edited; run doctor for repair guidance.
+`);return}let r=await ie();for(let n of r.removed)process.stdout.write(`Removed Flow skill: ${n}
+`);for(let n of r.kept)process.stdout.write(`Kept non-Flow or user-edited skill: ${n}
 `);process.stdout.write(`Remove opencode-plugin-flow from your OpenCode plugin config and restart OpenCode.
-`)}Ve(process.argv).catch((e)=>{process.stderr.write(`${e instanceof Error?e.message:String(e)}
+`)}$e(process.argv).catch((e)=>{process.stderr.write(`${e instanceof Error?e.message:String(e)}
 `),process.exitCode=1});