pstack: operate PDCA harness when present - #186
Conversation
When OPERATOR.md or HARNESS.md is present, load the repo contract and route delivery through intake/build stations instead of inventing board state. Co-authored-by: Cursor <cursoragent@cursor.com>
Expand plan/validate/pin/build/status via the repo OPERATOR.md full commands before running. Co-authored-by: Cursor <cursoragent@cursor.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.
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 5d72b40. Configure here.
| - `docs/OPERATOR.md` | ||
| - `docs/HARNESS.md` | ||
| - `harness/tree/docs/OPERATOR.md` or `harness/tree/docs/HARNESS.md` | ||
| - `.cursor/skills/intake-next/SKILL.md` and `.cursor/skills/build-next/SKILL.md` |
There was a problem hiding this comment.
Harness detection signals disagree
Medium Severity · Logic Bug
The SKILL.md and playbook incorrectly identify a bare harness/ directory as a PDCA harness. This contradicts references/pdca-harness.md, which requires specific paths like harness/tree/docs/... for detection. As a result, agents may false-positive on unrelated harness/ directories and enter Orchestrator mode without a loadable operator contract.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 5d72b40. Configure here.
|
|
||
| 1. Read `references/pdca-harness.md`, then `docs/OPERATOR.md` (or `docs/HARNESS.md` / `harness/tree/…` equivalents). | ||
| 2. Throughput checkpoint stays one line: `throughput checkpoint: n/a, harness operator` unless a Feature/Bug fix playbook also applies to product code. | ||
| 3. Match the user ask to an **alias** in `docs/OPERATOR.md` (`plan`, `validate`/`pre-do`, `pin wi-N`, `build`/`do`, `status`). Expand to that file’s **Full commands** block. Echo the expansion in `action:`. |
There was a problem hiding this comment.
Alias lookup ignores contract fallbacks
High Severity · Logic Bug
The PDCA harness logic has inconsistent expectations for contract file paths. While detection and initial loading support docs/OPERATOR.md, docs/HARNESS.md, and harness/tree/docs/ variants, alias expansion, route phrases, and role agent spawning are more rigid. This prevents alias matching, command expansion, and role agent spawning for valid HARNESS.md or harness/tree/docs/ based kits.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 5d72b40. Configure here.
1 participant
Summary
docs/OPERATOR.md/docs/HARNESS.md/harness/in poteto-mode.references/pdca-harness.md.Harness kits stay independent. pstack is the preferred host when installed.
Test plan
docs/OPERATOR.md, attach/poteto-mode, ask to validate upstream; expect intake/build routing, not a parallel plan.Made with Cursor