@memnexus-ai/mx-agent-cli 0.1.254 → 0.1.255
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -10,7 +10,7 @@ Use this skill before closing an iteration, opening a PR, merging a PR, or handi
|
|
|
10
10
|
4. Confirm tests, fixtures, replays, screenshots, or manual checks appropriate to the risk were completed.
|
|
11
11
|
5. Confirm hook output and command failures were interpreted from exit status and logs, not from noisy reminder text alone.
|
|
12
12
|
6. Confirm state memories, issue comments, or claim ledgers were updated when the work changed project knowledge.
|
|
13
|
-
7. Confirm every GitHub issue and PR referenced in a team-owned tracking document was reconciled against its real state with `gh issue view` / `gh pr view` before that document is cited in a product-owner-facing decision or status report. Correct each contradiction in the document, or flag it there explicitly. These documents go stale
|
|
13
|
+
7. Confirm every GitHub issue and PR referenced in a team-owned tracking document was reconciled against its real state with `gh issue view` / `gh pr view` before that document is cited in a product-owner-facing decision or status report. Correct each contradiction in the document, or flag it there explicitly. These documents go stale without anyone editing them — the issues and PRs they cite change state elsewhere — so no PR-triggered check sees a diff to fire on; this step fires at iteration close instead. Scope limit: this step only triggers when an agent cites such a document in a product-owner-facing decision or status report. A stale document the PO opens and reads directly is not covered — nothing in this checklist causes anyone to reconcile it. Instance: on 2026-07-31 `product/open-preview-blockers-20260815.md` still showed security blocker #4491 with mitigation "due this week" six days after PR #4497 (merged 2026-07-25) shipped the interim mitigation that removed #4491 from the Aug 11 gate — telling the PO the Aug 11 launch gate was blocked when it was not. Note the direction of the correction: #4491 itself remains OPEN pending the durable fix, so the document was wrong about the gate, not about the issue's state. Same drift produced the stale registry-submission exception (iteration 98) and a metric assumption that outlived its replacement by six days.
|
|
14
14
|
8. List any unresolved risks before declaring the iteration complete.
|
|
15
15
|
|
|
16
16
|
## Required Output
|