@orderful/droid 0.53.0 → 0.55.0

package/dist/tools/test-blueprints/skills/test-blueprints/scripts/validate.ts

@@ -0,0 +1,250 @@
+#!/usr/bin/env bun
+/**
+ * test-blueprints validate
+ *
+ * Validate blueprint .json.hbs templates against their Zod schema.
+ * Generates a temporary validation script in the workspace and runs it
+ * via ts-node so that tsconfig paths resolve correctly.
+ *
+ * Usage:
+ *   droid exec test-blueprints validate \
+ *     --workspace /path/to/orderful-workspace \
+ *     --schema-import "simplifiedSchemas/schemaFile" \
+ *     --schema-name "Simplified943Schema" \
+ *     --blueprints-dir "apps/platform-api/src/modules/testTransformation/data/testBlueprints/943s"
+ *
+ * Output (JSON):
+ *   {
+ *     "success": true,
+ *     "results": [
+ *       { "file": "943_standard.json.hbs", "status": "pass" },
+ *       { "file": "943_templated.json.hbs", "status": "skip", "reason": "contains Handlebars expressions" },
+ *       { "file": "943_bad.json.hbs", "status": "fail", "errors": [{ "path": "header.type", "message": "Invalid enum value" }] }
+ *     ],
+ *     "summary": { "pass": 8, "fail": 1, "skip": 2, "total": 11 }
+ *   }
+ */
+
+import { execSync } from 'child_process';
+import { existsSync, writeFileSync, unlinkSync, readdirSync, readFileSync } from 'fs';
+import { join } from 'path';
+import { tmpdir } from 'os';
+
+interface ValidationError {
+  path: string;
+  message: string;
+}
+
+interface FileResult {
+  file: string;
+  status: 'pass' | 'fail' | 'skip';
+  reason?: string;
+  errors?: ValidationError[];
+}
+
+interface ValidateResult {
+  success: boolean;
+  results?: FileResult[];
+  summary?: { pass: number; fail: number; skip: number; total: number };
+  error?: string;
+}
+
+interface ParsedArgs {
+  workspace?: string;
+  schemaImport?: string;
+  schemaName?: string;
+  blueprintsDir?: string;
+}
+
+function parseArgs(args: string[]): ParsedArgs {
+  const result: ParsedArgs = {};
+
+  for (let i = 0; i < args.length; i++) {
+    const arg = args[i];
+    if (arg === '--workspace' && args[i + 1]) {
+      result.workspace = args[++i];
+    } else if (arg === '--schema-import' && args[i + 1]) {
+      result.schemaImport = args[++i];
+    } else if (arg === '--schema-name' && args[i + 1]) {
+      result.schemaName = args[++i];
+    } else if (arg === '--blueprints-dir' && args[i + 1]) {
+      result.blueprintsDir = args[++i];
+    }
+  }
+
+  return result;
+}
+
+function expandPath(p: string): string {
+  if (p.startsWith('~/')) {
+    return p.replace('~', process.env.HOME || '');
+  }
+  if (p.startsWith('$HOME/')) {
+    return p.replace('$HOME', process.env.HOME || '');
+  }
+  return p;
+}
+
+function validate(parsed: ParsedArgs): ValidateResult {
+  if (!parsed.workspace) {
+    return { success: false, error: 'Missing --workspace' };
+  }
+  if (!parsed.schemaImport) {
+    return { success: false, error: 'Missing --schema-import' };
+  }
+  if (!parsed.schemaName) {
+    return { success: false, error: 'Missing --schema-name' };
+  }
+  if (!/^[A-Za-z_][A-Za-z0-9_]*$/.test(parsed.schemaName)) {
+    return { success: false, error: 'Invalid --schema-name: must be a valid identifier' };
+  }
+  if (/['"\n\r]/.test(parsed.schemaImport)) {
+    return { success: false, error: 'Invalid --schema-import: must not contain quotes or newlines' };
+  }
+  if (!parsed.blueprintsDir) {
+    return { success: false, error: 'Missing --blueprints-dir' };
+  }
+
+  const workspace = expandPath(parsed.workspace);
+  if (!existsSync(workspace)) {
+    return { success: false, error: `Workspace not found: ${workspace}` };
+  }
+
+  const blueprintsDir = parsed.blueprintsDir.startsWith('/')
+    ? parsed.blueprintsDir
+    : join(workspace, parsed.blueprintsDir);
+
+  if (!existsSync(blueprintsDir)) {
+    return { success: false, error: `Blueprints directory not found: ${blueprintsDir}` };
+  }
+
+  // Find .json.hbs files
+  const files = readdirSync(blueprintsDir).filter(f => f.endsWith('.json.hbs'));
+  if (files.length === 0) {
+    return { success: false, error: `No .json.hbs files found in ${blueprintsDir}` };
+  }
+
+  // Pre-check for Handlebars templates (skip these from Zod validation)
+  const results: FileResult[] = [];
+  const filesToValidate: string[] = [];
+
+  for (const file of files) {
+    const content = readFileSync(join(blueprintsDir, file), 'utf-8');
+    if (content.includes('{{')) {
+      results.push({ file, status: 'skip', reason: 'contains Handlebars expressions' });
+    } else {
+      // Check JSON parsability before sending to ts-node
+      try {
+        JSON.parse(content);
+        filesToValidate.push(file);
+      } catch (e) {
+        const err = e as Error;
+        results.push({ file, status: 'fail', errors: [{ path: '(root)', message: `Invalid JSON: ${err.message}` }] });
+      }
+    }
+  }
+
+  // If all files are skipped or failed JSON parse, return early
+  if (filesToValidate.length === 0) {
+    const summary = {
+      pass: 0,
+      fail: results.filter(r => r.status === 'fail').length,
+      skip: results.filter(r => r.status === 'skip').length,
+      total: results.length,
+    };
+    return { success: summary.fail === 0, results, summary };
+  }
+
+  // Generate validation script
+  const validationScript = `
+import { ${parsed.schemaName} } from '${parsed.schemaImport}';
+import * as fs from 'fs';
+import * as path from 'path';
+
+const dir = ${JSON.stringify(blueprintsDir)};
+const filesToValidate: string[] = ${JSON.stringify(filesToValidate)};
+const results: Array<{ file: string; status: string; errors?: Array<{ path: string; message: string }> }> = [];
+
+for (const file of filesToValidate) {
+  const content = fs.readFileSync(path.join(dir, file), 'utf-8');
+  const parsed = JSON.parse(content);
+  const result = ${parsed.schemaName}.safeParse(parsed);
+
+  if (result.success) {
+    results.push({ file, status: 'pass' });
+  } else {
+    results.push({
+      file,
+      status: 'fail',
+      errors: result.error.issues.map((issue: { path: (string | number)[]; message: string }) => ({
+        path: issue.path.join('.'),
+        message: issue.message,
+      })),
+    });
+  }
+}
+
+console.log(JSON.stringify(results));
+`.trim();
+
+  const scriptPath = join(tmpdir(), `_validate-${Date.now()}.ts`);
+
+  try {
+    writeFileSync(scriptPath, validationScript, 'utf-8');
+
+    const output = execSync(
+      `npx ts-node -r tsconfig-paths/register --project apps/platform-api/tsconfig.json ${JSON.stringify(scriptPath)}`,
+      {
+        cwd: workspace,
+        encoding: 'utf-8',
+        stdio: ['pipe', 'pipe', 'pipe'],
+        timeout: 60_000,
+      }
+    );
+
+    let zodResults: Array<{ file: string; status: string; errors?: ValidationError[] }>;
+    try {
+      zodResults = JSON.parse(output.trim());
+    } catch {
+      return { success: false, error: `Failed to parse validation output: ${output}` };
+    }
+
+    for (const r of zodResults) {
+      results.push({
+        file: r.file,
+        status: r.status as 'pass' | 'fail',
+        errors: r.errors,
+      });
+    }
+  } catch (err: unknown) {
+    const error = err as { stderr?: string; message?: string };
+    return {
+      success: false,
+      error: `Validation script failed: ${error.stderr || error.message}`,
+    };
+  } finally {
+    try { unlinkSync(scriptPath); } catch { /* ignore cleanup errors */ }
+  }
+
+  // Sort results to match original file order
+  results.sort((a, b) => files.indexOf(a.file) - files.indexOf(b.file));
+
+  const summary = {
+    pass: results.filter(r => r.status === 'pass').length,
+    fail: results.filter(r => r.status === 'fail').length,
+    skip: results.filter(r => r.status === 'skip').length,
+    total: results.length,
+  };
+
+  return { success: summary.fail === 0, results, summary };
+}
+
+// Main
+const args = process.argv.slice(2);
+const parsed = parseArgs(args);
+const result = validate(parsed);
+console.log(JSON.stringify(result, null, 2));
+
+if (!result.success) {
+  process.exit(1);
+}

package/dist/tools/webform/.claude-plugin/plugin.json

@@ -0,0 +1,22 @@
+{
+  "name": "droid-webform",
+  "version": "0.1.0",
+  "description": "Generate PrintView webform templates for EDI transaction types. Reads Orderful JSON schemas and sample transactions, proposes a visual layout, then generates template code with reusable subsection items.",
+  "author": {
+    "name": "Orderful",
+    "url": "https://github.com/orderful"
+  },
+  "repository": "https://github.com/orderful/droid",
+  "license": "MIT",
+  "keywords": [
+    "droid",
+    "ai",
+    "webform"
+  ],
+  "skills": [
+    "./skills/webform/SKILL.md"
+  ],
+  "commands": [
+    "./commands/webform.md"
+  ]
+}

package/dist/tools/webform/TOOL.yaml

@@ -0,0 +1,26 @@
+name: webform
+description: "Generate PrintView webform templates for EDI transaction types. Reads Orderful JSON schemas and sample transactions, proposes a visual layout, then generates template code with reusable subsection items."
+version: 0.1.0
+status: beta
+audience:
+  - engineering
+  - product
+
+includes:
+  skills:
+    - name: webform
+      required: true
+  commands:
+    - name: webform
+      is_alias: false
+  agents: []
+
+dependencies: []
+
+config_schema:
+  schema_repo:
+    type: string
+    description: "Path to orderful-workspace repo (contains Orderful JSON schemas)"
+  ui_repo:
+    type: string
+    description: "Path to o2-app-ui repo (contains PrintView templates and subsection items)"

package/dist/tools/webform/commands/webform.md

@@ -0,0 +1,17 @@
+---
+name: webform
+description: "Generate PrintView webform templates for EDI transaction types"
+argument-hint: "{transaction-type} [sample-transaction-path-or-inline-json]"
+---
+
+# /webform
+
+**User invoked:** `/webform $ARGUMENTS`
+
+**Your task:** Invoke the **webform skill** with these arguments.
+
+## Examples
+
+- `/webform 850 ~/Downloads/sample-850.json` → Generate 850 template from sample
+- `/webform 812 ~/Downloads/812.edi` → Generate 812 template from EDI file
+- `/webform 997` → Start 997 template (will ask for sample transaction)

package/dist/tools/webform/skills/webform/SKILL.md

@@ -0,0 +1,354 @@
+---
+name: webform
+description: "Generate PrintView webform templates for EDI transaction types. Reads Orderful JSON schemas and sample transactions, proposes a visual layout, then generates template code with reusable subsection items. User prompts like '/webform 850 sample.json', 'create a webform for 810'."
+argument-hint: "{transaction-type} [sample-transaction-path-or-inline-json]"
+globs: []
+alwaysApply: false
+allowed-tools: [Read, Write, Edit, Glob, Grep, Bash, Agent]
+---
+
+# Webform Skill
+
+Generate PrintView webform templates for Orderful EDI transaction types.
+
+## When to Use
+
+- Creating a new webform/PrintView template for a transaction type
+- User says "webform", "print view", "create a template for {type}"
+
+## When NOT to Use
+
+- Modifying existing templates (just edit directly)
+- Working on forms-mapper shapes/node mappers (different system)
+
+## Configuration
+
+**IMPORTANT:** Run `droid config --get tools.webform` first and parse the JSON output. If paths are not configured, **ask the user** for them.
+
+| Setting | Default | Description |
+|---------|---------|-------------|
+| `schema_repo` | (none) | Path to orderful-workspace repo (contains Orderful JSON schemas) |
+| `ui_repo` | (none) | Path to o2-app-ui repo (contains PrintView templates) |
+| `override` | (none) | User-defined behaviour overrides |
+
+**If not configured:** Ask the user:
+> "I need two repo paths to generate webform templates:
+> 1. **orderful-workspace** — where are the Orderful JSON schemas? (e.g., `~/Projects/orderful-workspace`)
+> 2. **o2-app-ui** — where are the PrintView templates? (e.g., `~/Projects/o2-app-ui`)"
+
+Then set their choices:
+```bash
+droid config --set tools.webform.schema_repo="{user's choice}"
+droid config --set tools.webform.ui_repo="{user's choice}"
+```
+
+### Derived Paths
+
+Once configured, derive all paths from the config:
+
+- **Schema location:** `{schema_repo}/libs/schemas/src/lib/data/transactionSchemas/orderful/{type}.schema.json`
+- **Template location:** `{ui_repo}/src/pages/Transaction/PrintView/templates/`
+- **Subsection items:** `{ui_repo}/src/pages/Transaction/PrintView/templates/subsectionItems/`
+- **Helpers:** `{ui_repo}/src/pages/Transaction/PrintView/templates/helpers.ts`
+- **Types:** `{ui_repo}/src/pages/Transaction/PrintView/types/index.ts`
+- **Tests:** `{ui_repo}/src/pages/Transaction/PrintView/templates/tests/templates.spec.ts`
+- **Allowed types:** `{ui_repo}/src/pages/Transaction/CreateTransaction/index.tsx`
+- **Print view routing:** `{ui_repo}/src/shared/helpers/printViewHelpers/getPrintViewComponentAndCsv.ts`
+
+**Overrides:** This skill supports user-defined overrides. See `/droid` skill § Skill Overrides for how to create, register, and use overrides.
+
+## Invocation
+
+```
+/webform {transaction-type} {sample-transaction}
+```
+
+- `transaction-type`: e.g., `850`, `810`, `997`
+- `sample-transaction`: file path to a JSON file, or inline JSON pasted by the user. If not provided, ask for it.
+
+## Workflow
+
+Follow these steps in order. Do NOT skip the visual layout step.
+
+### Step 1: Load Inputs
+
+1. **Read config** — run `droid config --get tools.webform` and parse the JSON. If not configured, ask the user.
+
+2. **Read the Orderful JSON schema** for the transaction type:
+   ```
+   {schema_repo}/libs/schemas/src/lib/data/transactionSchemas/orderful/{type}.schema.json
+   ```
+   This gives you field names (camelCase), titles, descriptions, and nesting structure. Pay attention to:
+   - `schemaType`: `element`, `segment`, `segmentArray`, `loop`, `loopArray`
+   - `title`: human-readable name like "BEG03 - Purchase Order Number"
+   - `segmentIdentifier`: X12 segment ID like "BEG", "N1", "PO1"
+
+3. **Parse the sample transaction** (file or inline JSON). This determines which segments/loops are actually used and should appear in the template. **Only model what's in the sample — not every possible field in the schema.**
+
+### Step 2: Inventory Existing Subsection Items
+
+Scan the existing subsection items directory:
+```
+{ui_repo}/src/pages/Transaction/PrintView/templates/subsectionItems/
+```
+
+Build a map of what already exists. Read the `index.ts` barrel file and glob for all `.ts` files. For each item, note:
+- The segment/loop it handles (e.g., `BEG`, `N1_loop`, `DTM`)
+- Whether it exports a block, table, or both variants
+- The `parentPath` it expects
+
+**CRITICAL: X12 is composed of shared building blocks. The same segment (N1, DTM, REF, etc.) appears across many transaction types. ALWAYS reuse existing subsection items. NEVER duplicate.**
+
+**NAMING: Subsection items must NOT include transaction type suffixes (e.g., `CDD_loop`, not `CDD_loop_812`).** Subsection items represent reusable X12 building blocks, not transaction-specific components. Some existing items like `PO1_loop_850` have this antipattern — do not follow that convention. Name items after the segment/loop they represent (e.g., `BCD`, `SHD`, `CDD_loop`).
+
+### Step 3: Map Sample to Subsection Items
+
+Walk the sample transaction's `transactionSets` structure. For each segment or loop present:
+
+1. **Check if a subsection item already exists** → mark as EXISTING
+2. **Check if it exists but needs additional fields** for this transaction type → mark as EXTEND
+3. **No subsection item exists** → mark as NEW
+
+Use the schema to determine:
+- Field labels (from `title`, strip the element ID prefix like "BEG03 - ")
+- Field types (`ElementType`: Alphanumeric, Numeric, Date, Time, etc. — infer from `X12DataElementType` or schema `type`)
+- Whether a field value comes from a qualifier code (use `QualifiedValueFieldMapItem` or `QualifiedLabelFieldMapItem`)
+- Whether data is a single record (→ block) or repeating array (→ table)
+
+### Step 4: Propose Visual Layout
+
+Present an ASCII/markdown layout to the user showing the proposed template structure. This is the most important step — **wait for user approval before generating any code.**
+
+Format:
+
+```
+# Proposed Webform: {type} - {title}
+
+## Section 1: {Section Title}
+
+  [{SEGMENT}] {Description} (block) ← EXISTING
+   • {Field Label}    • {Field Label}    • {Field Label}
+   • {Field Label}    • {Field Label}
+
+  [{SEGMENT}] {Description} (table) ← NEW
+   | {Column 1} | {Column 2} | {Column 3} |
+
+## Section 2: {Section Title}
+
+  [{LOOP}] {Description} (block, 2-col) ← EXISTING
+   • {Field Label}    • {Field Label}
+   ...
+
+## Section N: Totals
+
+  [footer] ← EXISTING (footer_CTT_loop)
+   Left: {fields}    Right: {fields}
+```
+
+For each subsection item, clearly indicate:
+- `EXISTING` — will import and reuse as-is
+- `EXTEND` — exists but needs fields added (list which fields)
+- `NEW` — will create a new reusable subsection item
+
+**Grouping guidance** (based on existing templates):
+- Header/general info segments go in the first section (BEG/BAK/BIG + CUR, PER, CSH, REF, N9)
+- Allowances/charges (SAC_loop) get their own section if present
+- Additional info segments together (ITD, FOB, DTM, PID, TD5, etc.)
+- Party identification (N1_loop) gets its own section, typically as `block--two-col`
+- Line items loop gets its own section with `countPath`
+- Totals/footer in the last section
+
+### Step 5: Iterate on Feedback
+
+The user may request changes:
+- Regroup sections
+- Add/remove fields
+- Change block ↔ table rendering
+- Adjust column layout for tables
+
+Iterate until the user confirms the layout.
+
+### Step 6: Generate Code
+
+Once approved, generate the template and any new subsection items.
+
+#### Template File
+
+Create `{ui_repo}/src/pages/Transaction/PrintView/templates/{type}.template.ts`
+
+Follow the exact patterns from existing templates. Example structure:
+
+```typescript
+import { PrintViewTemplate } from './types';
+import {
+  BEG,
+  CUR,
+  // ... other imports from subsectionItems
+} from './subsectionItems';
+
+export const template: PrintViewTemplate = [
+  {
+    sectionTitle: 'Section Title',
+    subsections: [
+      [BEG],
+      [CUR],
+    ],
+  },
+  // ... more sections
+];
+```
+
+Key patterns:
+- Each section is a `PrintViewPredefinedSection` with `sectionTitle` and `subsections`
+- `subsections` is an array of arrays — each inner array is a group of subsection items rendered together
+- Line item sections use `countPath` pointing to the loop array path (e.g., `'PO1_loop'`)
+- Party sections typically use `block--two-col` layout via the subsection item's `subsectionType`
+
+#### New Subsection Items
+
+For each NEW item, create a file in `subsectionItems/`:
+```
+{ui_repo}/src/pages/Transaction/PrintView/templates/subsectionItems/{Name}.ts
+```
+
+Follow existing patterns exactly. Key rules:
+- Import types from `'../types'`
+- Use `ElementType` enum for field value types
+- For blocks: set `subsectionType: 'block'` or `'block--two-col'`
+- For tables: set `subsectionType: 'table'`
+- For footers: set `subsectionType: 'footer'` with `leftFieldMap` and `rightFieldMap`
+- `parentPath` should use the Orderful JSON path (e.g., `'beginningSegmentForPurchaseOrder'`)
+- Field `valuePath` is relative to the parentPath
+- For qualifier fields, use `valueQualifierPath` or `labelQualifierPath`
+- Export the item as a named const
+
+#### Extended Subsection Items
+
+For EXTEND items, propose the specific `Edit` changes to add new fields to the existing file. Show the user what will change before applying.
+
+#### Register in helpers.ts
+
+Add the new template to the `loadPrintViewTemplate` switch/map in:
+```
+{ui_repo}/src/pages/Transaction/PrintView/templates/helpers.ts
+```
+
+#### Update barrel exports
+
+Add any new subsection items to:
+```
+{ui_repo}/src/pages/Transaction/PrintView/templates/subsectionItems/index.ts
+```
+
+#### Add TransactionType enum value
+
+If this transaction type isn't already in the `TransactionType` enum, add it to:
+```
+{ui_repo}/src/pages/Transaction/PrintView/types/index.ts
+```
+
+Follow the naming convention: `SCREAMING_SNAKE_CASE = '{type}_{SCREAMING_SNAKE_NAME}'` (e.g., `CREDIT_DEBIT_ADJUSTMENT = '812_CREDIT_DEBIT_ADJUSTMENT'`).
+
+#### Add to ALLOWED_TRANSACTION_TYPES
+
+If this is a new transaction type, add it to the `ALLOWED_TRANSACTION_TYPES` array in:
+```
+{ui_repo}/src/pages/Transaction/CreateTransaction/index.tsx
+```
+
+#### Wire up PrintView component
+
+Update the print view routing in:
+```
+{ui_repo}/src/shared/helpers/printViewHelpers/getPrintViewComponentAndCsv.ts
+```
+
+If there's an existing legacy component for this transaction type, replace it with `PrintView`. If there's no existing case, add one:
+```typescript
+case '{type_enum_value}':
+  printViewComponent = PrintView;
+  break;
+```
+
+#### Add to test coverage
+
+Add the transaction type to `testedTransactionSets` in:
+```
+{ui_repo}/src/pages/Transaction/PrintView/templates/tests/templates.spec.ts
+```
+
+This test validates that all paths in the template exist in the schema. The template **must** pass this test — if paths don't resolve, the field names in subsection items are wrong.
+
+### Step 7: Summary
+
+After generating, provide a summary:
+- Files created (with paths)
+- Files modified (with description of changes)
+- Existing subsection items reused
+- Any items that were extended
+
+## Type Reference
+
+Quick reference for the template type system (defined in `templates/types.ts`):
+
+### Subsection Item Types
+
+| Type | Use When | Key Fields |
+|------|----------|------------|
+| Block (static header) | Single record, fixed title | `subsectionType`, `header`, `parentPath`, `fieldMap` |
+| Block (dynamic header) | Single record, title from data | `subsectionType`, `headerQualifierPath`, `parentPath`, `fieldMap` |
+| Table (static header) | Repeating records, fixed title | `subsectionType`, `header`, `parentPath`, `columns` |
+| Table (dynamic header) | Repeating records, title from data | `subsectionType`, `headerQualifierPath`, `parentPath`, `columns` |
+| Footer | Totals/summary | `subsectionType: 'footer'`, `parentPath`, `leftFieldMap`, `rightFieldMap` |
+| Hierarchy | HL loops (856 only) | `subsectionType: 'hierarchy'`, complex nesting |
+
+### FieldMapItem Types
+
+| Type | Use When | Key Fields |
+|------|----------|------------|
+| DirectFieldMapItem | Simple label + value | `label`, `valuePath`, `valueType` |
+| QualifiedLabelFieldMapItem | Label comes from a code qualifier | `labelQualifierPath`, `valuePath`, `valueType` |
+| QualifiedValueFieldMapItem | The qualifier code IS the display value | `label`, `valueQualifierPath` |
+
+### Table Column Types
+
+| Type | Use When | Key Fields |
+|------|----------|------------|
+| TableStaticValueColumn | Simple column | `header`, `valuePath`, `valueType` |
+| TableQualifiedValueColumn | Column value from qualifier | `header`, `valueQualifierPath` |
+| TableFieldMapColumn | Multiple fields in one column | `header`, `fieldMap` |
+| NestedTableColumn | Blocks nested inside column | `header`, `subsections` |
+
+### ValueFormat
+
+Use `valueFormat` on DirectFieldMapItem when needed:
+- `'currency'` — e.g., $123.45
+- `'signedCurrency'` — with +/- sign
+- `'percent'` — e.g., 15%
+- `'decimalPercent'` — e.g., 0.15
+
+### ElementType
+
+Common values: `Alphanumeric`, `Numeric`, `Date`, `Time`, `ID`
+
+## Existing Subsection Items
+
+**Do NOT hardcode this list — always scan the subsectionItems directory at runtime.** This list is for reference only and may be outdated.
+
+### High Reuse (4+ templates)
+N1_loop, DTM (table + block), REF (table + block), SAC_loop, SAC_loop_block, FOB (table + block), TD5 (table + block), PID (table + block)
+
+### Medium Reuse (2-3 templates)
+CUR, PER, CSH, ITD, MEA (table + block), TD1, NTE, MAN, LIN, AMT, CAD, PKG, QTY, TXI
+
+### Transaction-Specific Headers
+BEG (850), BAK (855), BIG (810), BIA (846), BSN (856), G82 (875/880), BCD (812)
+
+### Line Item Loops
+PO1_loop_850, PO1_loop_855, IT1_loop_810, CDD_loop, G68_loop, G83_loop, HL_loop + HL_loop_items
+
+### Footers
+footer_CTT, footer_CTT_loop, footer_TDS_CTT, footer_G76, footer_G84
+
+### Other
+ISS_loop, LIN_loop, R4, V1, SDQ, SCH, LDT, PRF, PO4, SN1, IT3, TD3, TD4_block, MTX, YNQ, N9 (block + loop + table), SHD, G01-G86 (grocery segments), constants

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@orderful/droid",
-  "version": "0.53.0",
+  "version": "0.55.0",
   "description": "AI workflow toolkit for sharing skills, commands, and agents across the team",
   "type": "module",
   "bin": {