You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
SCRIP-SITE-010: integrate the reader product into one installable delivery #273
Owner request, 2026-10-10: review every open PR and prepare one major product update in a new PR against master. The published repository has not received the accumulated local work.
Bounded delivery
Integrate #268 (offline frozen report), #270 (private local analyzer) and #272 (five-route reader site) without duplicate implementations. Add a standard installable CLI, CSV export, readable metric labels/summary, exact numeric presentation, bounded input and private error handling from the tested local handoffs. Preserve the existing Python public API, historical artifacts, complete repository tests and deployment interlocks.
Acceptance
One new PR targets master; old PRs/branches remain until the integrated result is accepted.
Actual local UTF-8 input -> 29 unchanged metrics -> JSON/HTML/CSV, with no manuscript payload or private paths in errors.
FIFO, symlink, oversized-input and output-collision regressions; dictionary limits and null semantics remain explicit.
Installed CLI exposes real analyze/diagnostic/site commands, with documented build and install steps.
The canonical site retains all existing routes and the digest-approved full-work diagnostic. Full repository tests and a deterministic site rebuild run on the new head; package smoke tests run on the installed artifact.
No M1/M2/M3/M4/M5 completion claim, no external registry publication, no Pages activation/admin change.
Review receipts have been posted on all three current PRs. #270 has reproduced input-blocking and path-disclosure findings; carry the fix in the integration. This issue/PR is the sole integration claim; do not open competing local-workbench integration branches.
Owner-requested cleanup on 2026-10-18: #268 and #272 were independently accepted and merged into master (6338bedbeaf94b00374a95423bba5dd82368e593, then 9412ee54ab1a56c7c81f6ff4d290e39d83f49630); #267/#271 are completed.
The latest owner asks for a NEW PR covering the remaining executable issues. #275 claims the successor delivery path using the existing, un-PR'd scrip-site-two-full-work-gallery branch, preserving its three unique files and #274's existing Reader implementation/history. This prospectively replaces #274 as the active repair path, not the mission or acceptance gates. #270/#274 remain provenance pending successor acceptance. The syntax fix has been verified against the complete current renderer blob, and crash-safe publication now passes 11 actual Linux filesystem/subprocess tests. Full successor CI is still pending; no repaired change will be merged in this authoring run.
Activity
fix: respect canonical site output boundary in installed smoke
fix(site): stage complete builds and atomically publish without clobber
andy-zen-dev commentedon Oct 18, 2026
Owner-requested cleanup on 2026-10-18: #268 and #272 were independently accepted and merged into master (
6338bedbeaf94b00374a95423bba5dd82368e593, then9412ee54ab1a56c7c81f6ff4d290e39d83f49630); #267/#271 are completed.The latest owner asks for a NEW PR covering the remaining executable issues. #275 claims the successor delivery path using the existing, un-PR'd
scrip-site-two-full-work-gallerybranch, preserving its three unique files and #274's existing Reader implementation/history. This prospectively replaces #274 as the active repair path, not the mission or acceptance gates. #270/#274 remain provenance pending successor acceptance. The syntax fix has been verified against the complete current renderer blob, and crash-safe publication now passes 11 actual Linux filesystem/subprocess tests. Full successor CI is still pending; no repaired change will be merged in this authoring run.fix: converge Reader 0.2 delivery and recover crash-safe site builds