SCRIP-SITE-010: integrate the reader product into one installable delivery
Maintainers usually reply within 1 day
@andy-zen-dev is already working on this.
Since Oct 10, 2026.
Assessment
This issue has not been assessed yet.
Description
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.
- Dominant language
- Python
- Stars
- 4
- Forks
- 0
- Avg merge
- 10h 58m
- Merged PRs (30d)
- 78
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from drevendev/Scriptorium
-
Reader 0.2 release repair and ready-backlog consolidationPossibly taken @andy-zen-dev claimed this today. Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
drevendev/Scriptorium#275 ·
Maintainers usually reply within 1 day
-
SCRIP-METRIC-003: ship local UTF-8 analysis as private JSON and offline HTMLPossibly taken @andy-zen-dev claimed this 11 days ago. Open
drevendev/Scriptorium#269 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
drevendev/Scriptorium#265 · 2 comments ·
Maintainers usually reply within 1 day
All issues in drevendev/Scriptorium
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SwiftKickMobile/skai#84 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
jxxghp/MoviePilot#7070 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
flop-labs/technocore-chat#997 ·
Maintainers usually reply within 1 day
-
tunneld on Windows: Wi-Fi devices are not discovered because uvicorn runs on a ProactorEventLoopOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
doronz88/pymobiledevice3#2051 ·
Maintainers usually reply within 1 day