Skip to content

test(tool-diff): drop toolDiff from the act-warning baseline - #27041

Merged
javenciu merged 1 commit into
mainfrom
test/act-warnings-tool-diff
Nov 1, 2026
Merged

javenciu merged 1 commit into
mainfrom
test/act-warnings-tool-diff

Conversation

@javenciu

@javenciu javenciu commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: website/src/test/toolDiff.test.tsx stops emitting React act() warnings, so its row leaves website/integration/act-warning-baseline.json and the guard in website/integration/setup.ts checks it like any file outside the list.

The file no longer emits act() warnings on main: its tests already wait for every update they cause. The row is stale, and while it stays the guard would hide a warning the file starts to emit.

Why it matters

website/docs/testing.md (Rules every test keeps) treats an act() warning as a finding: the update lands after the assertions, so whether the test sees it depends on timing. The baseline is shrink-only, and each file that leaves it is held to the rule from then on.

Not a goal

  • Other files on the baseline (each is its own change).
  • Any change to the components under test.
  • Filtering or silencing the warning; the test waits for the update instead.

What changed (motivation → approach → change)

Only the baseline row is removed; the test file is unchanged.

  • website/integration/act-warning-baseline.json: removed src/test/toolDiff.test.tsx.

Backwards compatibility

Compatible: test-only change.
Removes nothing: a baseline row is a tolerance the guard stops needing, not a capability.

Tests

  • With the row removed: KIROCREW_ACT_STRICT=1 npx vitest run src/test/toolDiff.test.tsx from website/ passes 5 runs out of 5 with 0 act() warnings (15 tests).
  • integration/setup.refactor.determinism.test.ts passes (the baseline stays sorted, unique and existing); npx eslint is clean on the file.

Manual verification

N/A: test-only change; the strict runs above are the check.

Screenshots / video

Why no screenshot: nothing renders; this change touches one test file and a test baseline only.

No issue exists; burn-down of the act() warning baseline that #17673 introduced.

Make website/src/test/toolDiff.test.tsx stop emitting React act() warnings, and drop its row from
website/integration/act-warning-baseline.json so the guard in website/integration/setup.ts checks it.
@javenciu
javenciu requested review from a team and KiroCrewCaptain as code owners November 1, 2026 12:38
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 1, 2026
@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ⏭️ skipped

Revision 3719683402e4ae0e957655dbe7732d0a1c515079 ships no reviewable capability (docs, tests or generated files only), so there is nothing to inventory. Does not block merge.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

UX-level review of 3719683402e4ae0e957655dbe7732d0a1c515079 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

UX-Verdict: PASS

Nothing to check. The only change removes one row from a test baseline file, so there is nothing users can see and no screenshot is needed.

[UX-REVIEWED] 3719683

Description read

[DESCRIPTION-READ] 3e3f8f50385a1c873e749e57d1b218249d8bdff89bd1544778388b166d115527

That sha256 names everything this verdict read: the PR description, plus the 3 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 3719683402e4ae0e957655dbe7732d0a1c515079 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing to check. The diff only removes one stale row from a shrink-only test baseline and renders nothing.

[DESIGN-REVIEWED] 3719683

Description read

[DESCRIPTION-READ] 89cc1e12ebccd47eeabf7020eb454a5e0258948c57e260f067ad28768ad9565a

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 3719683402e4ae0e957655dbe7732d0a1c515079 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 3719683

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 3719683402e4ae0e957655dbe7732d0a1c515079 false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 3719683402e4ae0e957655dbe7732d0a1c515079 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 3719683

Verdict parsed from the review's SHA-scoped output markers for commit 3719683402e4ae0e957655dbe7732d0a1c515079.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 3719683402e4ae0e957655dbe7732d0a1c515079 false-positive: <reason, 20 to 500 characters>

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 1, 2026
@javenciu
javenciu enabled auto-merge (squash) November 1, 2026 13:48

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Tier 1 auto-approve: test (1 files). Criteria: no conflict, no requested changes, security path denylist clean, design-doc gate clean, security checklist all-NO, no reviewer-lane findings, readiness signal fresh for this head SHA, declared category matches the diff. Category: removes toolDiff.test.tsx from the act-warning baseline, a one-line test-baseline change.

@javenciu
javenciu merged commit ae51fd1 into main Nov 1, 2026
95 checks passed
@javenciu
javenciu deleted the test/act-warnings-tool-diff branch November 1, 2026 14:20
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 1, 2026
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