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" }, |
timoteo7
pushed a commit
that referenced
this pull request
Sep 24, 2026
…ead-only) FNXC:VerifyPerf 2026-09-24-01:00: MOVED from #17 (board-reliability) to #11 (verify-perf theme, per review). The typecheck step keeps the incremental tsbuildinfo cache (warm runs recheck only changed files) while staying READ-ONLY (--noEmit: no dist emit, no partial dist on a killed typecheck). Symptom Verification: warm verify typecheck rechecks only changed files; the step emits nothing (read-only).
timoteo7
force-pushed
the
fix/task-dispatch-pause-review-loop
branch
from
September 24, 2026 01:00
e6c0b48 to
6f75d66
Compare
timoteo7
force-pushed
the
fix/task-dispatch-pause-review-loop
branch
3 times, most recently
from
September 24, 2026 06:07
9f58a8b to
a14c77b
Compare
timoteo7
force-pushed
the
fix/task-dispatch-pause-review-loop
branch
from
September 25, 2026 04:15
78daa29 to
321491d
Compare
Owner
Author
|
Review notes for the audited SHA The current diff changes ten TypeScript configs to disable source/declaration maps; it does not contain the stranded-source, planning-spin, graph-identity, or watchdog fixes promised by the title. Please retitle and scope this as a build-output change, or close/supersede it with the actual behavior fixes in their respective PRs. Six of the config edits appear redundant because those packages inherit the changed plugin base config. Before landing the map change, please show a measured build/package benefit and verify that published diagnostics/artifacts do not depend on those maps. The package-files test and upstream config expect map globs, but that alone does not prove this change breaks packaging; the issue is that the PR currently provides neither the advertised reliability work nor evidence for removing the maps. |
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.
Supersedes the closed #10 (cannot reopen). See the commit for Root Cause + Symptom Verification.