Repository navigation
feat: add explicit offline local scan history - #9
Merged
Merged
Conversation
This was referenced Oct 20, 2026
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
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.
Explicit local history
Developers can explicitly initialize a private history directory and save manually initiated scans with both
--history-dirand--project-id. Plain scans and HTML-only scans still create no history. Saved schema-1 UUID records preserve privacy-filtered evidence, original Scanner/catalog metadata and uncertainty without changing detection, catalog or existing terminal/JSON behavior.Adds newest-saved-first history cards matching the approved Scanner dashboard, explicit historical HTML reopening without rescanning, and CLI-only deletion/pruning. Deletion previews by default and requires
--apply; combined age/keep-last policies use AND. No comparison, monitoring, Cloud sync, AI repair, authentication, billing or paid Cloud capability is included.Security and boundaries
Verification
Local Node 24/macOS: lint, typecheck, all 429 tests across 15 files, build, benchmark, package verification, self-contained archive creation and isolated empty-cache offline installation passed. Installed CLI checks include history init/two saves/list/reopen/delete preview/apply/prune preview, privacy, CSP, no-overwrite, blocked parent dependencies/network transports and unchanged synthetic targets.
Synthetic benchmark: 12 repositories, 14 TP / 0 FP / 2 unsupported FN; not a real-world accuracy guarantee. Founder approved desktop/mobile history design. Automated browser rendering was unavailable locally.
Based directly on public main
50813af697f04f3b375b1307cc38974bbee75e0b, containing merged Phase A PR #8. Only the 16 reviewed Scanner files are included; no private infrastructure or local records/previews/build artifacts. Ubuntu/macOS CI must pass before founder review. Do not merge automatically; no npm publication or release is authorized.