feat: restore the shared application shell and primary workflows

[bradtaylorsf]

Summary

Replace the six-file Memory/Ask/Import shell with the proven library-as-workspace application and restore the primary single-user workflows: content, import, tags, libraries, and answers.

Why this matters

These are the core ways users inspect, organize, and retrieve their own data. The current OSS shell makes imported history searchable but prevents users from managing the product model already built in enterprise.

Proposed approach

• Port the shared design system, app shell, routing, query hooks, tables, dialogs, forms, and content inspector from enterprise.
• Use local browser-session bootstrap instead of ProtectedRoute/Auth0 and omit workspace/team/admin permission chrome.
• Restore libraries list/CRUD, library overview/members/filtering/manual include-exclude, tag taxonomy CRUD/assignment, complete import flow, content detail/raw/archive/artifact views, and top-level/per-library grounded Answers.
• Preserve responsive and accessible behavior; adapt the existing blueprint styling rather than redesigning features.

Acceptance criteria

• Local root redirects into the complete application without login or manual API-key input.
• Users can create/edit/delete tags and libraries, assign/unassign content, filter/search/sort/paginate, use bulk actions, inspect raw content/summary/lineage, and import supported content.
• Answers can be scoped to a library and show real citations.
• Existing Claude, Codex, and Cowork history appears in content and library workflows.
• No paid navigation or dead enterprise-only controls appear.
• Unit/integration tests, pnpm verify, and agent-browser desktop/mobile interaction checks pass.

Out of scope

• Recipes, reports, dashboards, batch-job management, access tokens, and audit screens, which are restored by the next child.
• Roles, RBAC, teams, billing, and permissions.

Related

• Parent epic: epic: Open-source the complete single-user Answer Engine application #6
• Depends on: feat: port the neutral application data model and API foundation #8
• Source behavior: the-answerai/answer-engine-enterprise#439, #509, #443, #438, and #444

Batching note: run alone. It replaces the application shell and touches shared routing, API hooks, and styles used by the next UI child.

[bradtaylorsf]

Part of #6

[bradtaylorsf]

Incorrect-start interruption

Alpha Loop advanced into #9 planning after SIGINT had already been requested while stopping #8. This was an orchestration bug, not a valid queue transition: #8 remains unchecked and incomplete. The #9 worker was forcibly terminated during planning before source edits, commits, or a PR.

Lesson Learned

An interrupted batch must never advance to the next ordered child. Resume must begin at the first unchecked child (#8), and #9 must remain queued behind it. An interrupted #9 learning artifact will be tracked even though no implementation occurred.

[bradtaylorsf]

Implementation and verification plan

Product outcome

Restore the proven library-as-workspace shell for local single-user use. A fresh browser session will enter Content directly, with complete Content, Import, Tags, Libraries, and Answers workflows and no Auth0, paid navigation, or enterprise-only controls.

Technical work

1. Replace the local three-view component with React Router and TanStack Query providers, a local-session gate, responsive Blueprint shell, and routes for /content, /import, /tags, /libraries, /libraries/:libraryId, and global/library Answers.
2. Add typed API clients and query/mutation hooks for content detail/lineage/artifacts/blobs, imports, tags and assignments, libraries/filter previews/members/manual overrides, and grounded ask; centralize envelope/meta parsing and cache invalidation.
3. Extend the tenant-scoped content list API with validated search/source/type/tag/status/date filters, stable sort cursors, sort direction, tags/source/status projections, and detailed raw metadata without adding a migration.
4. Build accessible CRUD dialogs, tables, bulk actions, content inspector tabs, import preview/results, library filter/member management, and citation-to-content inspection using the existing Blueprint tokens and responsive/reduced-motion behavior.
5. Add focused server and web tests for routing/session bootstrap, API contracts and invalidation, filtering/sorting/cursors, primary workflows, citation navigation, and absence of paid UI.

Verification

Run focused tests during development, then pnpm verify. Start the local stack and exercise the changed workflows with Playwright at desktop and 375px widths, including keyboard focus and reduced-motion checks, and capture screenshots.