Conversation
ThreatCrush Security Scan4586 finding(s) HIGH/CRITICAL: 43 | MEDIUM: 4032 | LOW: 511
…and 4536 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| FNXC:TriagePlanningRecovery 2026-09-19-04:04: | ||
| The sweep announced "Recovering specified triage task <id>" on every poll for cards it never | ||
| recovered, and recorded no outcome when the recovery declined or when its own gates skipped the | ||
| candidate. The recorded engine log held 180 announcements and zero reasons, so an operator could |
| paused: false, | ||
| steps: [{ title: "Implement", status: "pending" }], | ||
| workflowStepResults: [ | ||
| { workflowStepId: "plan-review", workflowStepName: "Plan Review", phase: "pre-merge", status: "passed", verdict: "APPROVE" }, |
Owner
Author
|
Consolidated into #14 (board-reliability). |
timoteo7
pushed a commit
that referenced
this pull request
Sep 23, 2026
…lanning-spin + graph identity) FNXC:BoardReliability 2026-09-23-22:04: Consolidates the board-reliability fixes into ONE PR (supersedes #15 and #16): 1. SOURCE-OF-TRUTH stranded count (execution/stranded-commits.ts): fork-point + "0 task-unique = 0 stranded"; a failed fork-point falls back to ZERO, never the raw baseRef (shared fork/main lineage is never unsaved work). 2. Planning-spin: an unchanged-but-valid authoritative PROMPT.md is SUCCESS (was re-planning forever). 3. Graph-failure identity: a parse/compile failure names the failing stage, not node 'unknown'. 4. Manual retry clears ANY non-user pause (was only the deadlock reason). Symptom Verification: - Original symptom: "not safely reclaimable (N stranded commits since <base>)" treadmill + planning-spin + node 'unknown'. - Exact reproduction: a task branch at the main tip (0 unique commits) vs merge-base; a valid unchanged PROMPT.md. - Assertion it is gone: countStrandedCommits()==0 for shared lineage at the single source; planning accepts a valid unchanged spec.
timoteo7
force-pushed
the
fix/graph-failure-node-identity-beta6
branch
from
September 25, 2026 04:15
9c090fe to
16c2e40
Compare
Owner
Author
|
Review notes for the audited SHA The pause/deletion guard on the delayed Plan Review retry is useful; please keep it with a behavioral test proving a paused, user-paused, or deleted task is not dispatched. The title's graph-stage identity fix is not present in the diff—the added note says that identity is still deferred—so the title/scope should be corrected or the actual diagnostic change added separately. The PR also carries shellout allowlist entries for |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See commit for Root Cause + Symptom Verification (FUSI-020/021/022).