Skip to content

test: make shared fixture shutdown checks independent of order - #1303

Merged
blove merged 1 commit into
mainfrom
blove/fix-shared-fixture-shutdown-tests
Oct 12, 2026
Merged

blove merged 1 commit into
mainfrom
blove/fix-shared-fixture-shutdown-tests

Conversation

@blove

@blove blove commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

Adding Memory as the first shared fixture made the Skills and Subagents configuration tests fail on main: both assumed Subagents had to be the first shutdown operand. Check that each selected fixture participates in the guard and awaited .close() chain regardless of position, while preserving the closed fixture selection checks.

Validation: all 10 Deep Agents configuration checks passed; 12 mutation probes still reject missing guards, operands, awaits, and closes. Both affected Nx fixture targets passed, followed by 9 Skills and 13 Subagents browser cases. Runtime and server code are unchanged.

@vercel

vercel Bot commented Oct 12, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
threadplane Ready Ready Preview Oct 12, 2026 11:10pm UTC

Request Review

@blove
blove merged commit 6abb09d into main Oct 12, 2026
36 checks passed

This branch was successfully deployed

1 active deployment
Preview – threadplane — 67865714 Deployed Oct 12, 2026 by vercel[bot]
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.

1 participant