Save a story and pick up where I left off
editorial · Proposed launch phase 1
Start from HomeReview as Paid member
User story
As a paid member, I want to save an accessible story and continue reading so I can return to useful editorial work.
Draft requirements for review · Updated 2026-10-19
What the app should do
- Display reading progress only when it comes from actual persisted progress. Remove the unconditional67% claim and do not imply scroll restoration from an ordinary save. Unsupported progress must be absent or honestly unavailable.
- Save The Long Way In from The Decision Line series, retain reading progress, and find it in My Backcountry.
- Use the active Paid member role fixture for member-only actions. A free account or a professional identity does not supply paid access. The review identity is a genuine local account; another account’s checkout state stays separate.
What to check in the demo
Follow these steps from the role’s landing page through navigation and feature checks.
Begin on the paid Member Home. Use the Paid member demo role or Casey Bennett in Try a demo account, then select Member in the account/workspace menu if necessary. This creates a genuine local session with a seeded no-charge test membership; it does not upgrade a different account.
Navigation from sign-in
- 01Open the fictional Paid member account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
- 02Select Read the story in the Home hero to open The Long Way In.
Feature checks start here
The Long Way In
October19 scoped dummy-account fixes are available in dev. Named Home/reload and truthful profile checks pass; exact no-preference Professional browser coverage awaits a suitable account. Full-story acceptance remains separate. Navigation and feature checks can be reviewed in the current demo.
- 03Open a fresh dummy profile/story and inspect reading state; no fixed67% appears as measured personal progress. Confirm actual supported saved state belongs to the current account.
- 04Select Save on The Long Way In, then use footer My Backcountry → Saved and reopen the same story.
- 05Toggle the save state and check the visible result. In connected dev, saved work must reflect this account’s supported persisted state. No measured reading percentage or automatic scroll-position restoration is available; saving alone must not imply either.
- 06Remaining acceptance: record actual reading position and resume at that position. Verify removal changes the account’s Saved list; do not treat opening a saved story as measured progress.
Backend work for this feature
Backend development authorized · Dev only
What needs to be supported
- Display reading progress only when it comes from actual persisted progress. Remove the unconditional67% claim and do not imply scroll restoration from an ordinary save. Unsupported progress must be absent or honestly unavailable.
- Limit current implementation to dummy identity/persisted-data accuracy, entry and landing. Do not build unsupported private feature writes or a broad profile redesign. Preserve custom records, permissions and existing account/session behavior.
How to verify in dev
- Open a fresh dummy profile/story and inspect reading state; no fixed67% appears as measured personal progress. Confirm actual supported saved state belongs to the current account.
- Test owner isolation, real-user exclusion, preservation across repeat startup, reload and account switch; no role/client flag may grant access.
Before this can work
- Begin on the paid Member Home. Use the Paid member demo role or Casey Bennett in Try a demo account, then select Member in the account/workspace menu if necessary. This creates a genuine local session with a seeded no-charge test membership; it does not upgrade a different account.
No prerequisite story has been confirmed. The setup above describes the content or decisions needed.