feat(skills): mirror Vellum's slug/name separation in Nova architect brief

[jjackson]

Summary

Follow-up to #347 (0.13.274). That PR capped module/deliver-unit name length at 40 chars to dodge Connect's 50-char SlugField columns — treating the symptom. This PR addresses the cause by mirroring what the HQ-side authoring source of truth — dimagi/Vellum:src/commcareConnect.js, the plugin humans use in the form designer when the COMMCARE_CONNECT flag is on — does naturally: keep the Connect slug and the human display name as TWO SEPARATE fields.

From src/commcareConnect.js:117-173:

```javascript
ConnectLearnModule: {
rootName: "module",
childNodes: [
{id: "name", writeToData: true},
{id: "description", writeToData: true},
{id: "time_estimate", writeToData: true},
],
mugOptions: { spec: {
nodeID: { lstring: 'Module ID' }, // ← slug; user-supplied directly
name: { lstring: 'Name', required: true },
...
} }
}
```

Emitter at `dataChildFilter:89-115`:

```javascript
getExtraDataAttributes: () => ({
"xmlns": CCC_XMLNS,
"id": mug.p.nodeID, // ← slug from nodeID, NOT a slugified name
})
```

Fixture `tests/static/commcareConnect/learn_module.xml`:

```xml
<module xmlns="http://commcareconnect.com/data/v1/learn\" id="module_1">
module 1
...
<time_estimate>2</time_estimate>

```

Two distinct values: `id="module_1"` (short, code-like) and `module 1` (display label, can be long). Vellum-authored apps never hit the slug-length trap because humans naturally pick short identifiers.

Nova diverges. Nova's `compile_app` defaults the Connect `id` to `module__<slugify(name)>` when `connect.learn_module.id` is omitted. The API already supports the explicit-id field; ACE's brief just never told the architect to set it.

Changes

Three brief-template additions to `pdd-to-learn-app/SKILL.md` and `pdd-to-deliver-app/SKILL.md`:

1. NEW REQUIRED clause: set `connect..id` explicitly. Every `learn_module` / `assessment` / `deliver_unit` / `task` block MUST include an explicit `id` field (8-20 chars, lowercase, snake_case, stable across renames of the display name). This becomes the load-bearing rule; the ≤40-char name fallback below drops to defense-in-depth.

2. NEW REQUIRED clause (Learn only): `time_estimate` is in HOURS. Vellum's plugin help text says "Estimated time to complete the module in hours" (`src/commcareConnect.js:158`) and Connect's `LearnModule.time_estimate` model field docstring says "Estimated hours to complete the module". An architect on the LEEP run set 10-20 (intending minutes) which Connect would have stored as 10-20-hour modules.

3. Reframed ≤40-char name clause as FALLBACK. Kicks in only when the explicit-id rule above is missed. Removal criterion split: drop the fallback when commcare-connect#1195 lands + `SLUG_LENGTH_LIMIT` bumps in lock-step, but KEEP the explicit-id rule indefinitely — it's a cleanliness invariant matching Vellum's separation, not a workaround.

`docs/learnings/2026-05-17-connect-slug-length-50-char-trap.md` § Generalization extended with full Vellum source citations + a table of other Vellum-prescribed rules Nova should mirror:

• `time_estimate` integer-only validator (currently Nova allows decimals via `"type": "number"`)
• `relevantAttr` for conditional Connect-block display (not exposed in Nova)
• `ConnectWorkAreaUpdate` mug type (entire feature missing from Nova's vocabulary)

What's NOT in this PR

• No MCP / test code changes. The structural backstop (`app-release` Step 6's `oversized_slugs` projection gate, shipped in 0.13.274) remains the wall — this PR shifts left of it, not at it.
• The Vellum-prescribed rules in the new doc table are surfaced for visibility but not implemented (`time_estimate` validator narrowing, `relevantAttr`, `ConnectWorkAreaUpdate`) — they're follow-up candidates, not load-bearing today.

Test plan

• No code changes; doc + skill template only. `tsc --noEmit` clean (unchanged from main).
• After merge + `/ace:update`, the next `/ace:run` invocation of `pdd-to-learn-app` / `pdd-to-deliver-app` will emit a brief with the new REQUIRED clauses. Verify the Nova architect actually sets `connect..id` explicitly in the resulting build.
• Cross-reference: a Nova-built Learn app from a fresh run should produce CCZ form XML matching the shape `<module id="m1_background">Why This Survey Exists…` (id and name distinct) rather than the prior `<module id="module_1_why_this_survey_exists">` shape.

🤖 Generated with Claude Code