Sessions are now the unit of the product instead of an implicit capture run. - Nothing is deleted by default: the fixed 10-session cap is gone. An age limit (Never / 7 / 14 / 30 / 90 / 180 / 365 days) is chosen in Settings > Sessions and applied on launch, after archiving, and by "Clean up now". Sent PDFs are never touched. - Each session carries review details: lane, deployed version, commit, reviewer (pre-filled with the Mac user) and a free note. They persist in session.json and are inherited by the next session, so a review run is typed once. - PDF file names are Redline-<yyyyMMdd-HHmm>-<LANE>-<SHORTID>.pdf, and every page carries a two-line reference footer (tool, build time, session / lane, deployed build, commit, reviewer, note). The PDF document info carries the same values in Author and Keywords. - Verification: 159 tests, a headless panel self-test, and a LaunchServices-driven end-to-end run that types and clicks the real panel.
Redline
A macOS menu-bar app that captures a remembered screen region, builds a one-screenshot-per-page PDF, AirDrops it to an iPad for markup, then watches for the annotated file to come back.
Hotkeys
- ⌥⇧1 — pick a new region, then capture it.
- ⌥⇧2 — capture the remembered region instantly (no picker).
Sessions
Every review is a session. Captures go into the open session; "New session" closes it and keeps it in the Past sessions list, named and dated, whether or not it was sent.
- Nothing is deleted by default. A session is kept until you delete it.
- Settings > Sessions > Delete after sets an age limit (7 days … 1 year). Sessions older than the limit are removed on the next launch and by Clean up now. Only Redline's own saved screenshots are removed; a PDF that was already sent stays in the folder it was sent to.
- Details on the current session records what is being reviewed: lane/environment, the deployed build, the commit, the reviewer (pre-filled with this Mac's user) and a free note. A new session inherits the previous session's details.
Files and PDF metadata
The PDF is named
Redline-<yyyyMMdd-HHmm>-<LANE>-<SHORTID>.pdf (lane recorded)
Redline-<yyyyMMdd-HHmm>-<SHORTID>.pdf (no lane)
yyyyMMdd-HHmm is Dubai time, LANE is the upper-cased lane ("OMS test lane" →
OMS-TEST-LANE), and SHORTID is the session's 8-character id, so two sessions in the
same minute never collide.
Each page carries a two-line reference footer (tool + build time + session; lane, deployed build, commit, reviewer, note), and the PDF's document info carries the same values as Author and Keywords — a page printed or returned weeks later still says what it referred to.
Screen Recording permission
On first launch macOS asks once for Screen Recording. Grant it at System Settings > Privacy & Security > Screen Recording. You never have to do this again as long as the app is not re-signed with a different identity.
The grant is bound to the bundle identifier ai.flowmaster.shotdeck plus the code signature. Changing either one forces a fresh prompt.
Build
swift build && swift test
./scripts/build-app.sh # signed .app for daily use
open .build/Redline.app
Verification scripts
./scripts/render-panels.sh /tmp/redline-panels # headless PNGs of every panel + a sample PDF
./scripts/run-selftest.sh panel # real panel, real spool, PDF + retention checks
Both run against isolated temporary storage and an isolated preference suite, so they never touch the real Application Support folder or your saved settings.