Skip to content

fix(ci): tighten review signals and align workflow artifacts - #6

Merged
daniel-tsx merged 2 commits into
mainfrom
fix/workflow-p2-corrections
Oct 24, 2026
Merged

daniel-tsx merged 2 commits into
mainfrom
fix/workflow-p2-corrections

Conversation

@daniel-tsx

Copy link
Copy Markdown
Owner
  • T2 detection: shared idempotency service and its payload hash, and runtime app modules (wiring a dormant writer is an activation). CI and guard scripts get a separate guard-change label: independent review without T2 financial reading.
  • Skip guard: env-gated suites must match the exact RUN_* === '1' ? describe : describe.skip alias; any other new skip needs a non-empty "// allow-skip: " comment and is always listed for human approval. Mentioning process.env or allow-skip no longer bypasses the guard.
  • Non-blocking signals for net assertion removal and weak matchers.
  • engineering-workflow artifact set made explicit (state.json, plan.md, immutable reviewer reports, verification.json, final-checks.json, at most one handoff.md); recorded files change only via the state helper.
  • docs/verification.md documents the job-scoped issues/pull-requests write permissions of Review signals and why they are needed.

The "new skipped test fails unless env-gated or explicitly allowed" case is replaced by three narrower tests (env gate, allowed-and-listed, bypass attempts).

Claude-Session: https://claude.ai/code/session_015v69WpyGF25M7eMDxFThpE

What and why

Review guide

Task size

Checks

Result Command Scope / notes

Unverified boundaries

Review

Docs and temporary files

daniel-tsx and others added 2 commits October 24, 2026 05:39
- T2 detection: shared idempotency service and its payload hash, and
  runtime app modules (wiring a dormant writer is an activation). CI and
  guard scripts get a separate guard-change label: independent review
  without T2 financial reading.
- Skip guard: env-gated suites must match the exact
  RUN_* === '1' ? describe : describe.skip alias; any other new skip
  needs a non-empty "// allow-skip: <reason>" comment and is always
  listed for human approval. Mentioning process.env or allow-skip no
  longer bypasses the guard.
- Non-blocking signals for net assertion removal and weak matchers.
- engineering-workflow artifact set made explicit (state.json, plan.md,
  immutable reviewer reports, verification.json, final-checks.json, at
  most one handoff.md); recorded files change only via the state helper.
- docs/verification.md documents the job-scoped issues/pull-requests
  write permissions of Review signals and why they are needed.

The "new skipped test fails unless env-gated or explicitly allowed"
case is replaced by three narrower tests (env gate, allowed-and-listed,
bypass attempts).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015v69WpyGF25M7eMDxFThpE
The guard-change description string lost its closing quote, so the
"Sync review labels" step failed with "unexpected EOF". All workflow
run blocks were checked with bash -n, and the label step was exercised
with a stub gh under bash -eo pipefail for t2/guard/none combinations.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015v69WpyGF25M7eMDxFThpE
@github-actions github-actions Bot added the guard-change Changes CI or a guard script: independent review label Oct 24, 2026
@daniel-tsx
daniel-tsx merged commit 438dfbe into main Oct 24, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

guard-change Changes CI or a guard script: independent review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant