Full Nuxt / Vue Conversion

Why this work

Executive summary

1. 1Most of what the UI shows is real. Every listing and the newer detail pages read from qcontrol; the gaps are concentrated in the governance surfaces (Controls, Compliance, Framework, Integrations), where 44 pieces of data are still stand-ins for things the backend does not serve yet. The conversion does not wait on those: they are named, one per line, in a ledger with the backend contract that retires each.
2. 2The bible codifies app.qpoint.io's composable grammar as thirty rules with a test each: pages own scope, appliances are fed by props and speak in emits, primitives are domain-blind and typed, every staged value lives in one ledger.
3. 3The Fable track's app: all 43 routes as bills of materials over 44 domain modules and ~150 fed appliances; 66 spec files / 539 specs; a checker that turns "did we follow the documents" into a number. Verified page by page against the seed.
4. 4What is needed now is a decision on the path to Vue/Nuxt: adopt one app, adopt the bible and iterate, take pieces of both, or take a different route. The evaluation takes about 45 minutes and is laid out below.

How to evaluate — about 45 minutes

The two criteria: did the work follow the documents, and is it clean, simple and consistent — easy to follow, logical, the same noun meaning the same thing in every file.

1. 1
   Pull and run5 min

   git fetch && git checkout c99/compare, then cd crates/qdash/apps/<track> && npm install. Copy the seed db and serve it: cp scripts/qdash-seed/meridian.db /tmp/<track>.db && ./target/release/qdash --db /tmp/<track>.db serve --port 7882, then QDASH_API_BASE=http://127.0.0.1:7882 npm run dev (Fable: :3032; the layer resolves from a sibling q-nuxt-layer checkout or the package).

2. 2
   Read the bible's spine10 min

   02-data-interface-bible.md §2 (the shape), §3 (the three tiers and their tests), §6 (where business logic lives). Skip the prototypes unless a rule surprises you.

3. 3
   Read one page top to bottom10 min

   /team/users: pages/team/users/index.vue (the bill of materials) → composables/team/people.ts (the seven feeds, the rollup) → components/team/UsersRoster.vue (fed) → lib/people-rollups.ts (the math). Then one detail: /team/sessions/detail → useSession → components/team/SessionReading.vue.

4. 4
   Run the tests and the checker2 min

   npm test runs vitest and scripts/bible-check.mjs: no endpoint path outside composables, no lib function in an appliance, no page script over 60 lines, no any in the typed homes.

5. 5
   Skim the judgement calls8 min

   04-execution-log.md §Close and bible §14–15 (the addenda): every place the document had to be decided by the code. phase4/*.md §Judgement calls per tranche if one matters to you.

6. 6
   Decide10 min

   D1 through D6 above. D7–D9 can wait.

Decisions needed, and how to make each

D1 is the decision. D2–D6 are the rules the bible had to guess at; each answer changes a rule, not the shape. D7–D9 can wait for the cutover. Open a decision for its options, how to decide, and the recommendation.

What was produced

What the audit found

Every page read to the field with the components, composables and rollups it imports; every on-screen element classified as served, derived, or one of five kinds of shim; every field claim confirmed against the backend handlers.

What each page shows

The pieces of data each page loads from qcontrol or a shared store such as teams: served, derived from served rows on the client, or synthetic — the UI standing in for something that store should serve. UI state (filters, toggles, labels, copy) is not data and is not counted. Click a page for its on-screen elements; the "Data it reads" column is where each value comes from — the endpoint or rollup, with the field or expression where the audit recorded one.

Pieces of data × pages

Every piece of data a page loads from qcontrol or a shared store — an endpoint, a client rollup over served rows, or a stand-in for something that store should serve — against the pages that instantiate it. Red is synthetic: a projected placeholder, a catalog or localStorage record, a hard-coded number or fixture. UI state is left out unless you include it.