v7

.gitignore

@@ -37,3 +37,10 @@ next-env.d.ts
 # docs old and ref
 /docs-old
 /docs-ref
+
+# LLM-friendly generated artifacts (rebuilt by scripts/generate-llms.mjs)
+/public/llms.txt
+/public/llms-full.txt
+/public/index.md
+/public/v6/**/*.md
+/public/v7/**/*.md

.scratch/claude-code-voltprocure-thunderclap-prompt.md

@@ -0,0 +1,65 @@
+# Claude Code Prompt — Replan VoltProcure around Thunderclap / Laravolt v7.0.0-beta.3
+
+You are helping Rama re-plan the VoltProcure demo for Laravolt v7.0.0 stable preparation.
+
+Context:
+- Laravolt v7.0.0-beta.3 is released: https://github.com/laravolt/laravolt/releases/tag/v7.0.0-beta.3
+- Thunderclap is now intended as a central/meta feature for Laravolt v7.
+- Previous VoltProcure MVP exists at `/Users/rama/Laravolt/voltprocure`, but it was hand-coded quickly and should be revised so CRUD/admin surfaces are generated by Thunderclap.
+- Docs repo is `/Users/rama/Laravolt/docs-v7`.
+- Replan file: `/Users/rama/Laravolt/docs-v7/.scratch/voltprocure-thunderclap-replan.md`.
+- Thunderclap execution validation notes: `/Users/rama/Laravolt/docs-v7/.scratch/thunderclap-execution-validation.md`.
+
+Goal:
+Create a practical implementation plan for a Thunderclap-first VoltProcure demo that can become article material for laravolt.dev.
+
+Important principle:
+The demo should prove this path:
+
+```txt
+Database schema → Thunderclap generated modules → reviewable Laravolt code → business actions/workflows → tests/docs → deployable demo
+```
+
+Please do NOT jump straight into code unless asked. First produce an implementation plan and risk review.
+
+Tasks:
+1. Read the replan file and validation notes.
+2. Inspect current VoltProcure repo state:
+   - `/Users/rama/Laravolt/voltprocure`
+   - identify what should be kept vs rewritten.
+3. Inspect Laravolt v7.0.0-beta.3 Thunderclap behavior if needed.
+4. Propose the cleanest branch strategy:
+   - either rewrite current VoltProcure on a new branch
+   - or create a fresh VoltProcure beta.3 branch/app and port useful workflow code.
+5. Define exact schema to create before running Thunderclap.
+6. Define exact Thunderclap commands to run for MVP modules.
+7. Define generated module registration steps.
+8. Define what remains hand-written:
+   - business actions
+   - approval inbox
+   - PO issue/receiving
+   - inventory posting
+   - seed story
+   - tests
+9. Define article/demo milestones:
+   - first screenshotable Thunderclap CRUD
+   - workflow MVP
+   - Docker deploy
+   - AI-assisted extension demo
+10. Return:
+   - recommended approach
+   - step-by-step execution checklist
+   - files likely changed
+   - tests/build gates
+   - risks/blockers
+   - article outline
+
+Known beta.3 Thunderclap notes:
+- `--use-existing-models` is fixed in beta.3.
+- Generated modules still require explicit registration:
+  - Composer autoload PSR-4: `"Modules\\": "modules/"`
+  - provider lines in `bootstrap/providers.php`
+  - `composer dump-autoload`
+  - `php artisan optimize:clear`
+
+Do not overclaim. The demo should show Thunderclap generates the CRUD base, while Laravolt conventions guide the business workflow layer.