Skip to content

feat(#473): /launch-check --workflow — opt-in parallel + adversarially-verified audit#474

Merged
atlas-apex merged 1 commit into
me2resh:devfrom
atlas-apex:feature/GH-473-launch-check-workflow
Jun 1, 2026
Merged

feat(#473): /launch-check --workflow — opt-in parallel + adversarially-verified audit#474
atlas-apex merged 1 commit into
me2resh:devfrom
atlas-apex:feature/GH-473-launch-check-workflow

Conversation

@atlas-apex

Copy link
Copy Markdown
Collaborator

Summary

  • Adds an opt-in --workflow mode to /launch-check ([Feature] /launch-check --workflow — opt-in parallel + adversarially-verified audit #473). The 10 readiness dimensions are independent, read-only, and gate-free — the textbook fan-out shape — so --workflow authors and runs a Claude Code Workflow instead of the serial single-context pass.
  • Parallel evaluation + adversarial verify. Each applicable dimension is evaluated by its own agent (reusing that dimension's existing PASS/WARN/FAIL criteria verbatim — no new criteria), and each FAIL/WARN finding is independently refuted-or-upheld as soon as it returns (pipeline, no barrier). A refuted finding downgrades to PASS with a note — the false-positive cut that single-context serial evaluation can't do. PASS findings aren't re-verified.
  • Same output, same persistence, same trend. The workflow synthesizes the identical verdict table + four-state verdict vocabulary (go / go-with-warnings / conditional-go / no-go) and resumes at the existing Step 6 — same _lib-audit-history.sh (audit_run_persist / audit_render_trend), same superset JSON schema, same render-trend.sh chart. Trend history is continuous across serial↔workflow runs; no schema change.
  • Opt-in by design. A workflow run spawns ~10–20 agents vs one serial pass, and the Workflow primitive requires explicit opt-in — the --workflow flag is that opt-in. No flag → serial path, no Workflow invocation. The default behaviour is byte-for-byte unchanged.
  • Graceful degrade. If Workflow isn't available in the installation, the skill says so in one line and falls back to serial. --workflow is an optimisation, not a hard dependency.
  • No new skill / hook / role / agent — this is a mode added to an existing skill, so the framework counts (and test_site_counts.sh) are unchanged.

Testing

  • markdownlint-cli2 (CI ruleset) — 0 errors on the changed files (SKILL.md, AgDR-0055, CLAUDE.md). The only flags from a newer local markdownlint are MD060, a rule absent from CI's pinned version and already firing on pre-existing tables repo-wide.
  • bash .claude/hooks/tests/test_site_counts.shgreen (counts unchanged: this PR adds no skill/hook/role).
  • Default path unchanged — the serial Steps 3–5 and Step 6 persistence are untouched; --workflow only swaps the evaluation of the 10 dimensions for a fan-out, then rejoins Step 6.
  • Canonical workflow script documented in-skill (phases, DIM_SCHEMA / VERDICT_SCHEMA, pipeline-with-adversarial-verify, after-the-workflow synthesis + persist) so each run authors a consistent workflow.

Glossary

Term Definition
Workflow (mode) Opt-in /launch-check --workflow path that authors + runs a Claude Code Workflow to evaluate the 10 dimensions in parallel and adversarially verify findings.
Adversarial verify A second independent agent prompted to refute a WARN/FAIL finding (default upheld=false if it can't confirm); a refuted finding downgrades to PASS. Cuts plausible-but-wrong findings.
Pipeline (no barrier) Each dimension's finding is verified the moment that dimension returns, rather than waiting for the slowest dimension — wall-clock = slowest single chain, not sum-of-slowest-per-stage.
Superset schema The persisted run JSON carries both the canonical audit fields and the launch-check-specific scores{} map, so render-trend.sh keeps plotting unchanged.

Closes #473

…y-verified audit

Adds a third, opt-in mode to /launch-check. The 10 dimensions are independent
and read-only — the textbook fan-out shape — so --workflow authors and runs a
Claude Code Workflow that:
- evaluates all applicable dimensions concurrently (one agent each, reusing each
  dimension's existing PASS/WARN/FAIL criteria; non-applicable dims pre-resolved)
- adversarially verifies every FAIL/WARN finding as it returns (pipeline, no
  barrier) — a refuted finding downgrades to PASS (the false-positive cut)
- synthesizes the SAME verdict table + four-state vocabulary and persists via the
  SAME _lib-audit-history.sh (audit_run_persist / audit_render_trend), so trend
  history and the render-trend.sh chart are continuous across serial↔workflow runs

Opt-in by design: a workflow run spawns ~10-20 agents, so the serial path stays
the default; no flag → no Workflow invocation. Degrades to serial if the Workflow
tool is unavailable. No new skill/hook/role — counts unchanged.

Documents the canonical workflow script (phases, dimension + verdict schemas,
synthesis + persist) in-skill so each run authors a consistent workflow.
AgDR-0055 records the decision and the pattern for other multi-dimension audits.

Closes #473

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

@atlas-apex atlas-apex left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review: PR #474

Commit: a8e4428872daca197e258c75c85d714bb2f8f8c2

Summary

Adds an opt-in --workflow mode to /launch-check. Docs-only: the skill (SKILL.md) gains a frontmatter argument-hint, a third mode in the modes list, and a new "Workflow mode" section documenting a canonical Claude Code Workflow script (parallel fan-out of the 10 dimensions + per-finding adversarial verify, pipelined). Adds AgDR-0055 capturing the decision, plus a one-line CLAUDE.md skill-blurb update. No application/domain code, no new skill/hook/role/agent.

Checklist Results

  • Architecture & Design: Pass — opt-in flag, serial default preserved; reuses existing persistence/trend rather than forking it
  • Code Quality: Pass (docs) — the illustrative workflow script is internally consistent
  • Testing: Pass — no executable code; markdownlint/site-counts/lychee/shellcheck are the relevant gates
  • Security: Pass — read-only audit mode; no secrets, no new attack surface
  • Performance: Pass — opt-in precisely because it costs ~10–20 agents vs one pass; documented and gated behind the flag
  • PR Description & Glossary: Pass — Glossary present (4 terms), ticket linked (Closes #473)
  • Summary Bullet Narrative: Pass — every bullet is what + why; no advisory finding
  • Technical Decisions (AgDR): Pass — AgDR-0055 linked via <!-- agdr: ... -->, covers the decision (opt-in vs default, Workflow vs /fan-out, graceful degrade)
  • Adopter Handbooks: N/A — docs-only skill change; architecture/general handbooks have no trigger here, no .ts/.tsx in diff so the TypeScript handbook doesn't load, no domain handbooks present

Issues Found

None blocking.

Verification notes

  • Serial path + Step 6 unchanged: confirmed against the diff. Steps 1–2 and Step 6 (_lib-audit-history.sh / audit_run_persist / audit_render_trend / render-trend.sh) are untouched; the only edit near the default path is adding the word "serially" to the modes-list bullet — descriptive, not behavioural. The no-flag default is byte-for-byte preserved. No regression.
  • Cross-references resolve: the new section cites "Verdict logic" (SKILL.md L73), "Output format" (L40), and the four-state vocabulary go / go-with-warnings / conditional-go / no-go (L364) — all exist and match. The persistence claim (scores{} from each row's score, findings[] from WARN/FAIL rows, audit_run_persist) lines up with the documented Step 6 superset payload.
  • Workflow script coherence: judged as skill documentation an agent would author from, not runtime-compiled. export const meta (name/description/phases), agent(prompt, opts) with label/phase/schema/agentType, pipeline(items, mapFn, reduceFn), JSON-schema schema option, and the pipeline-with-adversarial-verify shape (PASS short-circuits with nothing to refute; WARN/FAIL spawn a refute agent; upheld === false downgrades to PASS with a note) are all internally consistent. DIM_SCHEMA / VERDICT_SCHEMA are well-formed. return { results: [...preResolved, ...evaluated.filter(Boolean)] } matches the "After the workflow returns" contract. An agent could author a correct workflow from this.
  • Counts: 3 files (SKILL.md modified, CLAUDE.md 1 line, AgDR added). No new skill/hook/role/agent → site-counts unaffected, as the PR claims.

Suggestions

  • nit (non-blocking): the "After the workflow returns" step says "apply the same verdict logic" — the serial verdict-logic table keys on PASS/WARN/FAIL counts, which the workflow rows carry, so this is fine. Worth a one-line note in a future pass that refuted FAILs downgrade to PASS before the count, so the verdict reflects the post-verify state (the script already does this via the downgrade; just not spelled out in the synthesis step). Purely a clarity nit.

Verdict

APPROVED


🤖 Reviewed by Rex (Code Reviewer Agent)
📌 Reviewed commit: a8e4428872daca197e258c75c85d714bb2f8f8c2

@atlas-apex atlas-apex merged commit 1d016da into me2resh:dev Jun 1, 2026
5 checks passed
me2resh added a commit that referenced this pull request Jun 5, 2026
…y-verified audit (#474)

Adds a third, opt-in mode to /launch-check. The 10 dimensions are independent
and read-only — the textbook fan-out shape — so --workflow authors and runs a
Claude Code Workflow that:
- evaluates all applicable dimensions concurrently (one agent each, reusing each
  dimension's existing PASS/WARN/FAIL criteria; non-applicable dims pre-resolved)
- adversarially verifies every FAIL/WARN finding as it returns (pipeline, no
  barrier) — a refuted finding downgrades to PASS (the false-positive cut)
- synthesizes the SAME verdict table + four-state vocabulary and persists via the
  SAME _lib-audit-history.sh (audit_run_persist / audit_render_trend), so trend
  history and the render-trend.sh chart are continuous across serial↔workflow runs

Opt-in by design: a workflow run spawns ~10-20 agents, so the serial path stays
the default; no flag → no Workflow invocation. Degrades to serial if the Workflow
tool is unavailable. No new skill/hook/role — counts unchanged.

Documents the canonical workflow script (phases, dimension + verdict schemas,
synthesis + persist) in-skill so each run authors a consistent workflow.
AgDR-0055 records the decision and the pattern for other multi-dimension audits.

Closes #473

Co-authored-by: me2resh <ahmed.abdelaliem@gmail.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants