Weekly demo improvements and fixes
October 14–21, 2026
Demo improvement · Across launch phases · Completed work and checks
5 improvements completed in dev; weekly record open. Walkthrough exceptions and per-environment release evidence remain explicit.
Five improvements are complete in dev: compact weekly navigation, role-specific story presentation, clear backend-scope labels, a connected-dev walkthrough audit, and responsive sign-in navigation after a verified clean startup/configuration repair. The weekly record remains open; full feature acceptance is separate.
Implementation status is separate from stakeholder approval and publication.
Goal
As a person reviewing the Backcountry demo, I want clear wording, consistent controls and reliable navigation so I can understand and test the product.
How to check
- Read each completed improvement for its location, exact change and expected result.
- Use Review result to inspect the current screen. Historical delivery evidence is preserved; the current connected-dev instructions take precedence over old mock-account setup.
- Open D013 and compare Guide versus Visitor with Review as; Guide begins on Professional Home → View public profile. Open D002 as Registered user to review public saving independently of paid reading.
- Open D071 to inspect its held specialist backend requirements, then D058 for currently authorized connected authentication. Do not expect D058 to remain a backend-only held record.
- For the walkthrough audit compare D001’s footer Profile entry, D084’s Basic page, D088’s real authenticator entry and D073’s explicit stop at the unavailable specialist workflow. Credential and staff-MFA completion still requires the tester.
Completion criteria
- Record each completed improvement with its date and location.
- Explain what changed and what a reviewer should see.
- Link visible results and summarize evidence for documentation or technical work.
- Close the record only when the period is explicitly closed.
Completed improvements · 5 items
Each item shows where the change happened, what changed and how to review it.
- Completed:
Make weekly progress navigation compact
visual review- Where:
- Brief → Progress updates → Progress by week, directly below the page heading
- What changed:
- Replaced the weekly archive cards with a single custom dropdown labeled Currently viewing. It includes every period, including the open current week, newest first by date range, and always selects the displayed period. Removed the separate Current week box and unused two-column layout; the selector is sized for desktop and full-width on phones, with scrollable options.
- Expected result / How to check:
- Open Progress updates and review Progress by week. Only the Currently viewing dropdown is shown as the weekly navigation control. Select October 7–14 or September 30–October 7, then select October 14–21 to return to the open week. Each page and selected range match; browser Back restores the prior period. On phones, the dropdown fits the available width without overflow.
Evidence: UI2 verified current-to-archive-to-current selection, keyboard/focus, Back, Visitor query preservation and phone layout after removing the redundant box. Earlier checks covered dated D054/D055 proof anchors, archived counts, 320/390px layouts, typecheck, focused lint and build.
Dev only. Staging and the HOL demo retain their previously published navigation.
Review result - Completed:
Make story review instructions follow the selected role
visual review- Where:
- Brief → Demo status → individual feature stories → Review as
- What changed:
- Corrected52 existing feature-story guides with113 role-specific variants. D013 starts as Guide and D014 as Creator. Free-account checks use public work and the free account Home; paid boundaries, professional identities and operator responsibilities are stated separately. Missing controls are identified instead of claimed complete.
- Expected result / How to check:
- Open HOL-D013: Guide is selected by default and now starts at Professional Home → View public profile. Choose Visitor and compare the public discovery requirements and Home entry. Open HOL-D002 as Registered user and check The Quiet Between Storms on free Member Home. Compare commercial versus editorial responsibility in D036; staff entry requires genuine MFA.
Evidence: Browser verified Guide default, Visitor content/requirements/start-link switching, Guide Home/profile navigation and Registered-user D002 content. Five focused checks, TypeScript and focused lint passed. Canonical role guides projected to dev; statuses and historical weekly counts unchanged.
Dev only. Backend implementation remains held; no staging/prod publication or week rollover.
Review result - Completed:
Show backend requirements without implying backend completion
visual review- Where:
- Brief → Demo status → individual feature/backend stories
- What changed:
- Added Backend work for this feature with an Implementation on hold label and future verification checks. Backend-only prerequisite pages carry the same hold, use backend-specific headings and omit an unrelated outcome-review button.
- Expected result / How to check:
- Open HOL-D071 → Backend work for this feature and inspect Requirements only · Backend implementation on hold. Follow D058 and compare its Backend development authorized · Dev only scope: authentication has since entered the connected build. This later build does not authorize the held content/verification workflows.
Evidence: Browser verified D071 requirements, Guide/Creator role switching, backend hold and its D058 held prerequisite page. Role/public export/history checks, TypeScript and focused lint passed.
Dev only. This displays requirements; no backend code, migration, service connection or real authentication/activation was implemented.
Review result - Completed:
Align story walkthroughs with the connected dev interface
visual review- Where:
- Brief → Demo status → UI story pages → What to check in the demo
- What changed:
- Audited 89 feature story records with 267 role-specific guides; corrected the shared real-account setup, renamed controls, public/profile/org routes and stale planned/simulated instructions. Preserved story statuses and requirements. Marked specialist Professional tools as unavailable from the connected Home, identified the single-group preview and illustrative reading-progress card, and kept credential/MFA completion separate from ordinary review.
- Expected result / How to check:
- Compare D013 as Guide and Visitor, D001’s Profile → Edit profile path, D084’s Basic page, D088’s Connect authenticator entry and D073’s explicit unavailable-tool stopping point. Planned checks are identified; an audit is not a full feature-acceptance pass.
Evidence: Current browser navigation and visible controls were compared with route/component sources. Credential changes and staff-protected completion stopped at their real security boundary; prepared-fixture edge cases remain open. Full per-story coverage and UI gaps are recorded in the project audit.
Dev only. Staff/MFA, credential changes, unavailable controls and prepared-fixture edge checks are not claimed as passed. No release or weekly rollover.
Review result - Completed:
Keep account-entry navigation responsive
visual review- Where:
- Demo accounts → Use email and password instead → Welcome back
- What changed:
- Made the five public app configuration values explicit, including absent values, and restarted the dev app without reseeding or changing accounts. The browser now responds to sign-in navigation.
- Expected result / How to check:
- Open the demo-account page, choose Use email and password instead and confirm that Welcome back and the password sign-in form open. This check stops before entering credentials or submitting.
Evidence: UI2 verified the actual chooser-to-sign-in navigation in a fresh browser tab, complete served-bootstrap evaluation, TypeScript/lint and five focused checks. The original cause was not isolated to raw environment references alone.
Verified in dev. Staging release and its own acceptance are recorded separately.
Review result