Resolve dead Review Pack early-access CTA and offering-scoped capture

[sarthakagrawal927]

Why

Live owner-session Chrome on 2026-10-04 renders Review Pack · Coming soon and a Get early access button at /library. Clicking the button has no visible effect or navigation. src/components/ReviewPackBanner.tsx confirms the button has no handler. The only Review Pack production references found are this banner and its HomeClient mount; PROJECT_STATUS describes personal-use, maintenance-first support. The banner therefore advertises an offering whose launch intent is unconfirmed.

What

Resolve the advertised offering and its broken capture path as part of the owner-requested Fleet feedback/newsletter/waitlist rollout. Preserve the functioning Reader app and its existing newsletter policy. Do not build Review Pack itself or declare all of Reader unreleased.

Design

If Review Pack is a real planned offering, connect this existing trigger to the already approved shared capture component in explicit waitlist mode, with offering-specific copy, unchecked consent, durable deduplicated acceptance, unsubscribe, and the matching App Health waitlist.join event. First confirm how offering scope is represented by the shared subscription contract; do not silently mix generic Reader updates with Review Pack interest. If it is not a planned offering, remove the misleading banner and dead CTA in a scoped product-truth repair.

Preserve Reader's established visual system and the selected shared capture treatment. Use the design-workflow preserve lane with rendered evidence for any interaction addition. No new production dependencies, auth changes, secrets or production config changes are proposed.

Specs

Requirement: Honest offering

Reader SHALL advertise early access only for an owner-confirmed unreleased offering.

Scenario: Offering not planned

• WHEN Review Pack is not a planned offering
• THEN the unsupported launch promise and dead early-access CTA are removed without changing library behavior.

Requirement: Functional consented capture

• WHEN Review Pack is confirmed and the owner opens early access
• THEN a clearly scoped waitlist form opens, consent starts unchecked, and success is displayed only after a durable write.
• WHEN a confirmed join is repeated
• THEN it does not create a second subscription outcome or App Health alert.
• WHEN the subscriber unsubscribes
• THEN future sending eligibility is removed, with safe repeat behavior.
• App Health SHALL receive only privacy-limited outcome metadata, never the subscriber address or library data.

Tasks

• Reproduce the live dead CTA and inspect its source handler.
• Confirm Review Pack launch intent with the owner and review this proposal.
• Inspect offering-scope support in the shared capture contract before selecting implementation.
• Implement the selected repair in an isolated writer; preserve unrelated dirty Reader work.
• Run focused tests and the applicable design preflight/rendered review/check.
• Release using the existing authorized guarded workflow and qualify the actual live flow.
• Record the outcome in Reader status and the Fleet capture tracker.

Related: sass-maker/saas-maker#156 and sass-maker/app-health#83. No email, feedback, capture POST, subscription or external AI handoff was submitted during discovery.

[sarthakagrawal927]

Completed the owner-selected removal in PR #74, merged as 963e0ead536752831574ce44795dc847f6731edb. Exact-main CI passes the full quality gate and local library, guest PDF, account PDF, and account notes suites.

All six Fleet deploy gates passed before the production release. Cloudflare confirms Worker reader version 2f582008-9406-432a-a110-ccd9cbe1a433, exact merged-SHA tag, at 100% traffic. The real signed-in /library before/after render confirms Review Pack, Coming soon, and Get early access are absent; the existing two sources, library navigation, search, Add Source, and filters remain.

The release also includes the independently reviewed scoped Astro http-cache security patch needed to pass the audit gate, with 27 consumer-resolved security cases and zero unexpected high/critical advisories. No production resource, configuration, or schema changes were made.