Focused opportunities journey
Direct owner request after the client asked for a clean journey focused on opportunities. Agreed sequence: browse → full details → Apply → Free/Paid options. Uses Listing-Option-B-2026-10-22 visual direction in a separate standalone folder, prototype/opportunities-journey/, with index.html as entry. Original samples are unchanged.
Browse actions now say View details, and titles link to details. Six fictional opportunities each explain the business, desired partner, contribution, fit criteria and terms for discussion. Apply appears on the full detail page. A consistent progress indicator and back links support the three stages. Filters/saves/view remain in memory during navigation; route choice is remembered per opportunity. Direct Apply entry first shows details. Native modal Help and skip-focus behavior are included.
The Free/Paid stage retains the selected opportunity. Free leads toward a future expression-of-interest draft; Paid leads toward a future scope/fee discussion. Route endings clearly identify the preview boundary and never claim submission or payment. Service scope, fees, verification criteria and approval policy remain unagreed. Q02, Q03, Q05 and Q06 remain unresolved. All content is synthetic.
Evidence
Browser checks cover six detail links, cards, filter retention, save sync, both endings, radio keyboard operation, remembered selection, direct-entry guard, skip navigation and modal dismissal. Axe A/AA tags report zero violations/incomplete rules for 10 desktop states (browse, six details, options, two endings) and three core states at 320px, with no mobile overflow. No browser errors recorded. JSON and screenshots are saved in the prototype folder; README states remaining manual accessibility work. No integrated T/DG scenarios change status.
Security: no real data/secrets, no logging of messages, no external submission, bounded search and native accessible controls. Server authorization, cross-company denial, eligibility over private data, idempotency/outbox/audit checks are inapplicable to this local synthetic UI. No security posture change.
No issue/PR, commit or publication created for this follow-up. Next eligible action: owner/client walkthrough of these three screens; after agreement, separately scope real EOI drafting and service intake.
Whole-vault self-test rerun: exit 1 with the same five finding categories as the earlier Option B report; three deliberate mutations detected. Report is saved with the prototype. Evidence-folder findings were not repaired in this UI task.