FE-1316: Audit current system authority and drift - #412
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
PR SummaryLow Risk Overview The only runtime change fixes stale Reviewed by Cursor Bugbot for commit 51f3e07. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Pull request overview
This PR performs a documentation/audit pass following FE-1316, tightening the structured-exchange “present_digest → ask” guidance to match the current conversational correction flow, and updating planning artifacts to record the audit closeout plus two newly admitted follow-on frontiers.
Changes:
- Updated
present_digesttool description/guidelines to reflect free-text correction continuations and the separateacceptsDigestcapture step. - Adjusted extension tests to assert the new guidance and reject the deprecated approve/request-changes/reject phrasing.
- Recorded FE-1316 closeout and admitted frontiers in
memory/PLAN.md, with corresponding archival notes indocs/archive/PLAN_HISTORY.md.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/.pi/extensions/exchanges/present-digest.ts | Updates the tool’s user-facing guidance to match the current correction + capture flow. |
| src/.pi/extensions/tests/exchanges-extension.test.ts | Updates assertions to reflect the revised guidance strings and remove expectations for deprecated phrasing. |
| memory/PLAN.md | Logs FE-1316 completion and adds definitions + sequencing entries for two new follow-on frontiers. |
| docs/archive/PLAN_HISTORY.md | Archives FE-1316 closeout narrative and records the admitted follow-on frontiers. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Why
After a run of related work landed, this was a scheduled check-in: are we tracking every open thread correctly, and has anything drifted out of sync between what the docs say and what the code actually does? This is a review pass, not new product functionality.
What
How to test
This is an audit/planning pass with one small text fix.
npm run checkpasses.