trevon/fold
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
fold/docs
History
Exact
trvon b8c997c732
 fix(scan): report quarantined TUs as coverage gaps 
Problem: a TU skipped because a prior run quarantined it was not analysed,
but coverage did not say so. The serial path dropped it from the attempted
set, so a scan whose only TU was quarantined was complete and exited 0; the
fan-out path saw no file_finished record and called it frontend-failed.

Fix: the shard runner counts every requested TU and records skipped ones
with gap reason `quarantined`; a worker emits a file_finished record with
that reason so the parent classifies it the same way. USAGE lists the reason.

Test: test_subprocess_fanout "[quarantine]" covers serial (was 2 attempted,
no gap) and fan-out (was frontend-failed). CLI probe: serial and fan-out
both exit 2 with a `quarantined` gap.
2026-09-24 21:41:42 -06:00
..
architecture docs: trim the README and move the performance roadmap to docs/ 2026-09-24 21:11:54 -06:00
internal feat(analysis): harden quality and solver pipelines 2026-07-29 20:46:51 -04:00
research fix(docs,tests): correct the pre-push hook claim, a dead link, MCP cleanup 2026-09-24 20:57:32 -06:00
BUILDING.md docs(build): canonical BUILD.md with per-platform deps 2026-05-24 18:11:31 -04:00
compatibility.md docs: document convergence contracts 2026-07-29 00:58:19 -04:00
mcp-tools.md docs: expand fold-sast skill; document call-graph decomposition + budgets 2026-08-16 16:41:33 -06:00
positioning.md docs(positioning): drop claims the code and evidence do not support 2026-09-24 20:58:26 -06:00
README.md feat: harden security scanner routing 2026-05-27 10:36:57 -04:00
USAGE.md fix(scan): report quarantined TUs as coverage gaps 2026-09-24 21:41:42 -06:00

README.md

fold documentation

Public-facing docs in this directory are intentionally small:

  • USAGE.md — CLI usage and report formats.
  • BUILDING.md — build and radare2 integration notes.
  • positioning.md — high-level product positioning and tradeoffs.
  • research/ — public research/background notes.

Verbose development plans, audit logs, benchmark snapshots, and agent-specific notes live under internal/. Link to those files from public docs only when a contributor needs the implementation detail.