Merge pull request #5 from Denys/audio-dev-dashboard-unified-agent

Add Field mapping workflow and audio development dashboards

Author: Denys

.agent/skills/dvpe-development/README.md

@@ -14,8 +14,8 @@ stored as `.dvpe` JSON files and can be exported to C++ firmware for Daisy Field
 Without a structured design workflow, two problems repeat every time:
 
 - **Wrong block selected** — e.g., `reverb` instead of `reverb_sc`, or `filter` instead of `svf`.
-  The DVPE block library has 108+ blocks with specific `definitionId` strings. Guessing the ID
-  produces broken `.dvpe` files that won't load.
+  The live DVPE block library is exported with `py -3 execution\dvpe_cli.py blocks export`.
+  Guessing the ID produces broken `.dvpe` files that won't load.
 - **Unvalidated signal flow** — connections drawn between incompatible port types (`audio` vs `cv`
   vs `trigger`) only become obvious after attempting to generate C++.
 - **Hardware mismatches** — generating a Field patch with an encoder block (Field has no encoder),
@@ -125,11 +125,11 @@ You can refine any diagram before advancing. Gate does not self-advance.
 
 For every Audio Flow node, Claude:
 
-1. Looks up the `definitionId` in the Block Catalog (108+ blocks)
-2. Verifies the block exists in `BlockRegistry.ts`
+1. Runs `py -3 execution\dvpe_cli.py blocks export`
+2. Verifies the block exists in `.tmp/block_library.json`
 3. Flags any unmapped node with the nearest available alternative
-4. Generates `.dvpe` JSON following SCHEMA.md rules
-5. Validates the schema checklist (6 common mistakes) before declaring done
+4. Generates `.dvpe` JSON using the current block and port IDs
+5. Runs `py -3 execution\dvpe_cli.py patch validate <file.dvpe>` before declaring done
 
 Output is saved to `_block_diagrams_code/{patch_name}.dvpe`.
 
@@ -203,9 +203,9 @@ After Claude presents all 3 Mermaid diagrams, your options:
   OLED visualization, correct LED indexing, and other FieldUX requirements. Always pass it
   through `/daisy-qae` before flashing to hardware.
 
-- **Don't guess `definitionId` strings.** The Block Catalog in SKILL.md lists all 108+
-  verified IDs. Using a made-up ID (like `"reverb"` instead of `"reverb_sc"`) produces a
-  `.dvpe` that fails to load silently.
+- **Don't guess `definitionId` strings.** Treat the SKILL.md catalog as a quick reference only.
+  Run `py -3 execution\dvpe_cli.py blocks export` and validate generated files with
+  `py -3 execution\dvpe_cli.py patch validate <file.dvpe>`.
 
 - **Don't skip Diagram A for "simple patches."** Simple patches still run on real hardware.
   The block diagram catches platform mismatches (Field vs Pod), MIDI assumptions, and OLED
@@ -215,7 +215,8 @@ After Claude presents all 3 Mermaid diagrams, your options:
 
 ## Block Catalog Quick Reference
 
-Full catalog with all `definitionId` strings is in SKILL.md. Key blocks by use case:
+This is a quick reference. The current catalog is `.tmp/block_library.json` after running
+`py -3 execution\dvpe_cli.py blocks export`. Key blocks by use case:
 
 ### Synthesis Starting Points
 
@@ -334,22 +335,23 @@ the DVPE workflow.
 ```
 .claude/skills/dvpe-development/
 ├── README.md      ← This file
-├── SKILL.md       ← Mermaid-First Rule + 4 modes + Block Catalog + Platform Reference
+├── SKILL.md       ← Mermaid-First Rule + 4 modes + CLI validation rule + quick reference
 └── EXAMPLES.md    ← 3 complete workflow traces + anti-pattern table
 ```
 
 ---
 
 ## Extending the Skill
 
-### Adding a new block to the catalog
+### Adding a new block
 
 When a new block is added to `dvpe_CLD/src/core/blocks/definitions/`:
 
 1. Find its `id` property in the `.ts` definition file
-2. Add it to the Block Catalog in SKILL.md under the appropriate category
-3. Note LGPL status if applicable
-4. Add to EXAMPLES.md if it introduces a new usage pattern
+2. Run `py -3 execution\dvpe_cli.py blocks export`
+3. Run `py -3 execution\dvpe_cli.py skill check`
+4. Update the SKILL.md quick reference only if it is useful for humans
+5. Add to EXAMPLES.md if it introduces a new usage pattern
 
 ### Adding a new platform
 
@@ -374,4 +376,4 @@ If a 4th diagram type becomes useful (e.g., memory layout for delay-heavy patche
 *Part of the DVPE project.*
 *See also: `daisy-qae` skill for production firmware quality assurance.*
 *Block definitions: `dvpe_CLD/src/core/blocks/definitions/`*
-*Schema: `_block_diagrams_code/SCHEMA.md`*
+*Validation CLI: `execution/dvpe_cli.py`*

.agent/skills/dvpe-development/SKILL.md

@@ -34,6 +34,24 @@ override the rule. The diagrams take 5 minutes and prevent wrong block connectio
 
 ---
 
+## Runtime Validation Rule
+
+The block catalog below is a human quick reference only. Before trusting a
+`definitionId`, port ID, generated `.dvpe`, or fixture, validate against the
+live repo CLI:
+
+```powershell
+py -3 execution\dvpe_cli.py blocks export
+py -3 execution\dvpe_cli.py patch validate <file.dvpe>
+py -3 execution\dvpe_cli.py skill check
+```
+
+The exported `.tmp/block_library.json` and `patch validate` output are the
+current source of truth. If this document disagrees with the CLI, follow the
+CLI and update the skill.
+
+---
+
 ## When to Use
 
 Trigger this skill when the user:
@@ -144,7 +162,7 @@ OUT[audio_output]     → block definitionId = "audio_output"
 
 For every node in the Audio Flow diagram:
 
-1. Find matching `definitionId` in the Block Catalog below
+1. Run `py -3 execution\dvpe_cli.py blocks export` and find matching `definitionId`
 2. If found → include in .dvpe blocks array
 3. If NOT found → flag it:
    - Suggest nearest available block
@@ -172,7 +190,13 @@ Follow the schema exactly (see Schema Quick Reference below).
 
 ### Step 3 — Schema Validation Checklist
 
-Before declaring MODE 2 done, verify:
+Before declaring MODE 2 done, run:
+
+```powershell
+py -3 execution\dvpe_cli.py patch validate _block_diagrams_code\{patch_name}.dvpe
+```
+
+Also verify:
 
 - [ ] Top-level `"version": "1.0.0"` present
 - [ ] All blocks wrapped inside `"patch": { "blocks": [...] }` (not top-level)
@@ -256,7 +280,11 @@ Step 5: Handoff to /daisy-qae
 
 ## Block Catalog
 
-Complete `definitionId` reference. Source of truth: `dvpe_CLD/src/core/blocks/BlockRegistry.ts`
+Human quick reference only. The live source of truth is:
+
+```powershell
+py -3 execution\dvpe_cli.py blocks export
+```
 
 `*` = LGPL module — requires `USE_DAISYSP_LGPL = 1` in Makefile
 
@@ -311,8 +339,8 @@ Complete `definitionId` reference. Source of truth: `dvpe_CLD/src/core/blocks/Bl
 | `distortion` | Hard distortion |
 | `bitcrush` | Bit crusher (bit depth reduction) |
 | `decimator` | Sample rate decimator |
-| `soft_clip` | Soft clipping waveshaper |
-| `hard_clip` | Hard clipping waveshaper |
+| `softclip` | Soft clipping waveshaper |
+| `hardclip` | Hard clipping waveshaper |
 | `wavefolder` | Wavefolder |
 | `fold` | Simple fold distortion |
 | `rectifier` | Half/full wave rectifier |
@@ -353,7 +381,7 @@ Complete `definitionId` reference. Source of truth: `dvpe_CLD/src/core/blocks/Bl
 | `sample_hold` | Sample and hold |
 | `envelope_follower` | Envelope follower |
 | `gate_length` | Gate duration control |
-| `fsm4` | 4-state finite state machine |
+| `fsm_4` | 4-state finite state machine |
 
 ### Dynamics
 
@@ -631,8 +659,8 @@ These requests violate the Mermaid-first rule. Redirect to the correct stage.
 - `dvpe_CLD/src/core/blocks/BlockRegistry.ts` — authoritative block ID list
 - `dvpe_CLD/src/core/blocks/definitions/` — individual block definition files
 - `dvpe_CLD/src/codegen/CodeGenerator.ts` — C++ generation logic
-- `_block_diagrams_code/SCHEMA.md` — complete schema documentation
-- `_block_diagrams_code/template.dvpe` — minimal valid .dvpe example
+- `execution/dvpe_cli.py` — live block export, `.dvpe` validation, fixture generation, and skill drift checks
+- `.tmp/block_library.json` — generated block reference after `py -3 execution\dvpe_cli.py blocks export`
 
 ### Directives
 

.gitignore

@@ -2,6 +2,7 @@
 node_modules/
 **/node_modules/
 package-lock.json
+!dvpe_CLD/package-lock.json
 
 # === Build Outputs ===
 dist/