opportunities-extension/openspec/changes/archive/2026-10-31-document-project-baseline/tasks.md

Tasks

These are application-phase tasks for a documentation baseline. Creating these planning artifacts does not complete the documentation edits below. No task authorizes runtime feature changes, schema customization, a release, or live Oracle writes.

1. Reconcile the documented user experience

• 1.1 Update README.md Opportunity Views to describe the current Calendar, coordinated Customer/Owner filters, filter isolation and persisted sorting; verify against tests/opportunityCalendar.test.cjs, tests/dependentFilters.test.cjs, tests/allOpportunityFilters.test.cjs and tests/tableSorting.test.cjs with the existing Node test runner.
• 1.2 Update README.md product/workload, Booking and projection descriptions and remove active AI-summary descriptions; verify the relevant behavior against tests/badgeIcons.test.cjs, tests/ramp-projection.test.cjs and tests/workload-forecast-update.test.cjs, and confirm no active AI API/module claim remains in README.md.
• 1.3 Update README.md Organization Charts with stored alphanumeric PartyNumber, transient email, on-demand contact refresh, creation and paginated contact opportunities; verify against tests/orgChart.test.cjs and tests/accountContact.test.cjs without sending real contact writes.
• 1.4 Update README.md customer insights and shell coverage with Rate Card order filtering, printing, favorite shortcuts/hints and draggable modal headers; verify against the relevant source and tests/ratecard.test.cjs, tests/bookmarkShortcut.test.cjs, tests/bookmarkHint.test.cjs and tests/dialogDrag.test.cjs, recording any visual behavior that remains untested in an installed browser.

2. Reconcile authentication and asynchronous loading

• 2.1 Update README.md authentication to use the current SPA bootstrap URL, identity reuse, independent SR session preparation and SALES_REP restrictions including Manage Time; verify against tests/currentUser.test.cjs, tests/srSessionPreparation.test.cjs and tests/manageTime.test.cjs.
• 2.2 Correct README.md SR/Actions sequencing and saved-search contracts, including progressive SR badges and allowed activity cache-miss requests for cached products; verify against tests/srRequestPriority.test.cjs, tests/crmServiceRequests.test.cjs, tests/activityProgress.test.cjs and tests/productActivities.test.cjs.
• 2.3 Revise docs/architecture.md runtime contexts, generated manifest permissions/hosts, service credentials, saved searches and timeout/stale-response behavior; verify each changed contract against scripts/build.mjs, composition roots and relevant service/auth sources, and run tests/architecture.test.cjs and tests/buildOutput.test.cjs.

3. Reconcile persistence and establish documentation navigation

• 3.1 Update docs/architecture.md storage ownership and cache lifetimes for preferences, debug, identity/session state, products, workloads, activities and organization charts; verify each storage location/key against source and tests/activityCache.test.cjs, tests/formRequestCache.test.cjs, tests/workloads.test.cjs and tests/refreshAll.test.cjs.
• 3.2 Correct README.md and docs/architecture.md debug descriptions to include lazy rendering, page-one reset, persistence across modal closure and the distinction between masking and stored originals; verify against tests/debugStorage.test.cjs and tests/debugTabs.test.cjs and remove blanket claims that all credentials remain only in memory.
• 3.3 Add concise OpenSpec navigation to README.md and link the architecture documentation to the capability baseline, clearly identifying this change as proposed until archival; verify link targets, retain # Opportunities Extension, keep historical notes in RELEASE_NOTES.md and confirm no schema/config change is included.

4. Validate the integrated baseline

• 4.1 Review all twelve capability specifications against the final documented behavior and evidence map; verify every requirement has a WHEN/THEN scenario, every proposed capability has one matching spec file, and no runtime enhancement is concealed as an existing contract. Record unresolved discrepancies rather than silently changing code.
• 4.2 Run openspec validate document-project-baseline --strict and node scripts/build.mjs --check; verify strict validation succeeds and generated browser packages are unchanged and current.
• 4.3 Run node scripts/test.cjs for final integration verification and git diff --check; record results and explicitly distinguish synthetic coverage from any unperformed installed-browser or live Oracle checks. Confirm the final change is confined to approved documentation and OpenSpec artifacts, with version and release notes unchanged.

Workflow follow-up

• After application and review, use $openspec-archive-change document-project-baseline to promote the baseline specifications and archive the change. Archival is not a prerequisite for completing the tracked tasks.
• Confirm openspec list --specs --json lists the twelve promoted capabilities, no generated Purpose placeholder remains, and README navigation resolves to the durable specs.
• Use capability-specific delta changes for future behavior updates; do not rewrite the baseline from release history or silently replace it with an unreviewed implementation snapshot.