📝 docs(docs): build the Affirm wiki from the repository docs and source
Split the oversized README.md, GETTING-STARTED.md, AGENTS.md, WORKTRUNK.md,
and SECURITY.md from tecapps/affirm into 30 focused wiki pages, each checked
against the code on the staging branch at commit 45a78c3.
- Home: stack overview, task-based entry points, and provenance
- Setup: Getting started, Environment variables, Commit signing, Tooling,
and editor pages for VS Code and WebStorm
- Code: Project structure (layout, auto-imports, aliases), Frontend (routes,
components, composables), Styling, Server API (endpoint contracts,
bindings), and Authentication (current state and gaps)
- Data: Database (schema reference), Database migrations, and Remote
database access (Drizzle Studio, db:push)
- Quality: Commands reference, Testing (Vitest and Playwright), and
Linting and formatting (Trunk linters and Git hooks)
- Process: Branching and pull requests, Commit conventions, Worktrunk, and
Worktrunk hooks and config
- Shipping: Deployment (Workers Builds), Manual deployment, CI, and
Configuration files (Wrangler configs, D1 binding overrides, Worker types)
- Reference: Gotchas, Known issues, Glossary, and Security
- Add _Sidebar.md navigation and _Footer.md
Known issues records problems found in the source: two Drizzle fields
sharing the businessRepresentative column, registration omitting the
required username, login not creating a session, the missing staging
secrets.required, and drift between the repository docs and the code
(Nuxt Content, the ~ alias, the module list).