Eval Criteria: ea-livrable-assembler

Eval Criteria: ea-livrable-assembler

Created: 2026-05-14 Target: production-lines/digital-talent/talents/agent-ea-v2/.claude/commands/ea-livrable-assembler.md Purpose: Edward skill that assembles 4-page split HLSD HTML deliverable (index, page1 A100+A280, page2 A270, page3 A290 conditional) + catalog/, ready for JCT publish.

Questions (binary YES/NO)

Register model (TFD-018)

  1. Does the skill expose a --register board|console flag with board as default?
  2. Does the skill explicitly cite TFD-018 (or its register vocabulary: register-board / register-console / LITE) as the canonical aesthetic decision?
  3. Does the skill correctly distinguish which template family to read per register (template-*.html for board vs template-*-LITE.html for console)?
  4. Does the skill apply the register-board / register-console class to <body> in the output (or instruct Edward to do so)?

Templates and SVG components

  1. Does the skill reference svg-components/ partials as the canonical SVG source (rather than telling Edward to redraw the 8 diagrams inline)?
  2. Does the skill list (or point to) the 8 SVG partials with their target page sections, so Edward knows which to inline where?

Accessibility (WCAG AA baseline)

  1. Does the skill mandate the WCAG AA baseline (focus-visible, contrast, keyboard a11y on interactive SVG, skip link, lang="fr-CA") as a non-negotiable output contract item?

Conditional logic

  1. Does the page3 emission rule cite both a CSV-column trigger (e.g. cost columns in objects.csv) AND an intrant-section trigger, so the decision is data-driven?

Catalog deep-linking

  1. Does the skill explicitly instruct emission of <a href="catalog/browser.html?layer=X&impact=Y"> deep-links (not plain <div>s) on the heat-map cells in page1?

Backwards compatibility

  1. Does the skill keep --style stm-brand|fluent|factory functional (deprecated in description but accepted) so existing invocations don't break?

Frontmatter and invocation

  1. Is the frontmatter (name:, description:, etc.) intact, well-formed YAML, and does the description reflect register vocabulary rather than only --style?
  2. Does the skill specify register resolution precedence (CLI --register > CLAUDE-{slug}.md register: > default board)?