Skip to content

pstack: name maintain source readers and stop routing the pass through swarm - #264

Open
0xrep wants to merge 3 commits into
cursor:mainfrom
0xrep:cursor/maintain-source-readers-29c5
Open

pstack: name maintain source readers and stop routing the pass through swarm#264
0xrep wants to merge 3 commits into
cursor:mainfrom
0xrep:cursor/maintain-source-readers-29c5

Conversation

@0xrep

@0xrep 0xrep commented Aug 25, 2026

Copy link
Copy Markdown

The source wave had no role name, so pstack-models.mdc could not bind it and operators treated the pass as a /swarm. That composition hits the cloud async cap and drops readers.

This names the role maintain source readers, defaults it to inherit-parent, and spawns with readonly: true. The coordinator still owns every live drive and executes the map's own Driving section, not child-derived recipes. verified-unreachable is a clean coverage result when the prerequisite and route are named. A product gap stays in the report and does not flip the pass to changed or blocked.

The guide no longer says a /swarm can split a full map pass. That line was how the wrong composition got taught.

Skipped: fan-out caps, shared-harness re-drive, churn window, retry-once unit. Those remain operator notes.


Note

Low Risk
Documentation and agent-skill instructions only; no product code, auth, or runtime behavior changes.

Overview
Introduces a dedicated maintain source readers role for /maintain-verification-skill’s parallel source wave so /setup-pstack can bind it in pstack-models.mdc (default inherit-parent). The maintain skill now spells out spawning those children as read-only generalPurpose tasks and explicitly says not to wrap the pass in /swarm—readers are not swarm workers; the coordinator still runs every live drive from the map’s Driving it with harness text, with child recipes only for drift reconciliation.

Outcomes are tightened: clean counts source coverage plus live drive or documented verified-unreachable; product gaps in the report alone don’t force changed/blocked. blocked applies when a feature never got a source-wave return or wasn’t driven/classified. Target selection when multiple verify skills exist prefers the path in the current diff instead of guessing.

The verify-and-ship guide drops the line that taught splitting a full map pass via /swarm and mirrors the new maintain behavior and anti-swarm guidance.

Reviewed by Cursor Bugbot for commit 916db3b. Bugbot is set up for automated code reviews on this repo. Configure here.

0xrep added 2 commits August 26, 2026 00:26
…h swarm

Give the source wave a bindable role, default inherit-parent, and readonly
spawns. Map verified-unreachable onto clean/blocked. Drive the feature map
text, not child recipes. Drop the guide line that sent the same job to /swarm.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

Fix All in Cursor

Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.

Reviewed by Cursor Bugbot for commit 629f9d8. Configure here.

Comment thread pstack/skills/maintain-verification-skill/SKILL.md Outdated
Comment thread pstack/skills/maintain-verification-skill/SKILL.md Outdated
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