# Workflow Audit 2026-03-14

## Scope

- Reviewed local workflow JSON files under `.vl-code/workflows/`
- Verified seed copies under `public/seed-workflows/`
- Compared local workflow references against DocCenter path usage
- Improved `/debug` and `/fix` execution logic
- Verified workflow runtime observability and compile-report plumbing

## Confirmed Workflow Issues

1. `add-page.json`
- Used wrong DocCenter prompt paths for service/component/section/app generation
- Did not reliably write the updated app back to the planned `.vx` file

2. `add-service.json`
- Used the wrong service prompt path
- Wrote database changes to a hardcoded `Database/main.vdb` instead of the actual file from `ProjectMeta`

3. `theme-customize.json`
- Referenced the wrong theme prompt path
- Wrote theme changes to a hardcoded theme file path
- Did not persist cascade-updated files back to disk

4. `incremental-update.json`
- Referenced missing DocCenter prompt paths (`50`, `52`)
- Needed stronger inline regeneration instructions once those prompts were removed

5. `6-file-codegen.json`
- Assumed app output path was always `Apps/{appId}.vx`
- Broke multi-app or custom-file-path projects where `filePath !== appId`

6. `compile-fix.json`
- Claimed to compile and recompile inside the workflow even though the workflow engine had no real compile step
- Reworked to a report-driven repair workflow that consumes `.vl-code/last-compile.json`

## Runtime / Tooling Issues Fixed

1. Compile route
- Warning-only diagnostics were treated as hard compile failures
- `.vl-code/last-compile.json` was not being persisted consistently even though prompts and repair logic depended on it

2. Orchestrator repair entrypoints
- CLI help advertised `/fix`, but no `fix` skill existed
- Compile-error language could be misrouted into `VLAdjust` instead of a real compile-repair flow
- `/debug` did not enforce compile-first behavior before browser/runtime inspection

3. Workflow executor context loading
- `readFiles` declarations existed in workflows but were not injected into LLM context
- Added file-context injection so incremental and file-preserving workflows actually see current source files

## Local Files Updated

- `.vl-code/workflows/6-file-codegen.json`
- `.vl-code/workflows/add-page.json`
- `.vl-code/workflows/add-service.json`
- `.vl-code/workflows/theme-customize.json`
- `.vl-code/workflows/incremental-update.json`
- `.vl-code/workflows/compile-fix.json`
- `public/seed-workflows/6-file-codegen.json`
- `public/seed-workflows/add-page.json`
- `public/seed-workflows/add-service.json`
- `public/seed-workflows/theme-customize.json`
- `public/seed-workflows/incremental-update.json`
- `public/seed-workflows/compile-fix.json`
- `src/core/orchestrator.js`
- `src/core/cli.js`
- `src/server/routes/compile.js`
- `src/vl/workflow-executor.js`

## Validation

Executed on 2026-03-14:

- `node test-adjust-workflows.js`
- `node test-adjust-workflow-execution.js`
- `node test-workflow-status-tools.js`
- `node test-workflow-parallel-codegen.js`
- `node test-compile-done-event.js`
- `node test-vl-compile-warnings.js`
- `node test-compile-report-persistence.js`
- `node test-orchestrator-fix-skill.js`
- `node test-workflow-read-files.js`
- `node test-compile-fix-workflow.js`

## DocCenter Sync Targets

- Path `60`: `VL_FullStack_CodeGen_6Files_v3.16`
- Path `120`: `VL_AddPage_Workflow_v1`
- Path `130`: `VL_AddService_Workflow_v1`
- Path `140`: `VL_ThemeCustomize_Workflow_v1`
- Path `141`: `VL_IncrementalUpdate_Workflow_v1`
- Path `142`: `VL_CompileFix_Workflow_v2`
- Path `161`: `VL-Code Workflow Audit Report 2026-03-14`