feat(skills): add UX design capability and accessibility Design Intent Records (microsoft#2611)

# Pull Request

## Description

Adds a UX design capability to HVE Core and extends the accessibility
skill with a Design Intent Record contract, so UX practice, engineering
handoff, and accessibility verification share one evidence model.

Two new skills join the `design-thinking` collection, routed by the
existing `ux-ui-designer` agent:

* `ux-artifacts` produces durable, evidence-labelled UX assets in five
modes: `frame-needs`, `map-journey`, `sketch-structure`,
`decide-inclusion`, and `prepare-handoff`. Every claim carries an
evidence class of Observed, Reported, or Assumed, and unresolved items
stay visible rather than becoming invented research.
* `ux-coaching` supports problem framing, design critique, and
stakeholder advocacy as a conversation rather than an artifact.

Completed assets can be mapped to Figma or Mural. Mapping produces
destination intent only; it never authenticates, selects tools, or
performs an external write. Callers supply `destination-kind`,
`destination-target`, and, for Figma, `destination-change`. A missing
value returns a bounded missing-input result naming the absent fields
instead of inferring one.

The accessibility skill gains a Design Intent Record contract, authored
and verification JSON schemas, the `Validate-DesignIntent.ps1` validator
with contract regression tests, runtime probe intent and projection
modules, and a Graphics ARIA and SVG AAM framework reference. A new
`lint:design-intent` script joins the `validate:local` aggregate.

`dt-coach`, the canonical deck, and the coaching-state references are
reconciled with the new UX routes so coaching and artifact production do
not overlap. Collections, plugin outputs, extension manifests, and
generated reference documentation are regenerated by their owners.

The written Markdown asset stays authoritative. A Figma, FigJam, or
Mural rendering is a projection and never supersedes it. Technical
accessibility conformance and COGA guidance remain owned by the
`accessibility` skill; UX assets route conformance questions there
rather than answering them.

## Related Issue(s)

Closes microsoft#2609

## Type of Change

Select all that apply:

**Code & Documentation:**

* [ ] Bug fix (non-breaking change fixing an issue)
* [x] New feature (non-breaking change adding functionality)
* [ ] Breaking change (fix or feature causing existing functionality to
change)
* [x] Documentation update

**Infrastructure & Configuration:**

* [ ] GitHub Actions workflow
* [ ] Linting configuration (markdown, PowerShell, etc.)
* [ ] Security configuration
* [ ] DevContainer configuration
* [ ] Dependency update

**AI Artifacts:**

* [x] Reviewed contribution with `hve-builder` and addressed all
actionable findings
* [x] Copilot instructions (`.github/instructions/*.instructions.md`)
* [x] Copilot prompt (`.github/prompts/*.prompt.md`)
* [x] Copilot agent (`.github/agents/*.agent.md`)
* [x] Copilot skill (`.github/skills/*/SKILL.md`)
* [ ] Copilot hook (`.github/hooks/*/*.json`)
* [x] Eval spec added/updated for changed AI artifacts (`evals/`)

> Note for AI Artifact Contributors:
>
> * Agents: Research, indexing/referencing other project (using standard
VS Code GitHub Copilot/MCP tools), planning, and general implementation
agents likely already exist. Review `.github/agents/` before creating
new ones.
> * Skills: Must include both bash and PowerShell scripts. See
[Skills](../docs/contributing/skills.md).
> * Model Versions: Contributions **MUST** target models listed in the
model catalog (`scripts/linting/model-catalog.json`) whose provider
appears in `providerAllowlist` and whose status is `ga` or `preview`.
Run `npm run lint:models` to validate references.
> * See [Agents Not
Accepted](../docs/contributing/custom-agents.md#agents-not-accepted) and
[Model Version
Requirements](../docs/contributing/ai-artifacts-common.md#model-version-requirements).

**Other:**

* [x] Script/automation (`.ps1`, `.sh`, `.py`)
* [ ] Other (please describe):

## Sample Prompts (for AI Artifact Contributions)

**User Request:**

```text
Use the completed problem-framing output for the renewal flow to create a
current-state journey. Preserve unresolved evidence gaps and do not publish it.
```

**Execution Flow:**

1. The `ux-ui-designer` agent recognises the request as artifact
production rather than coaching, and asks a single routing question only
if the request matches more than one capability.
2. It calls `ux-artifacts` with `mode=map-journey`, `project`,
`subject`, and the coaching `output_ref` passed as the explicit
`source`.
3. The skill reads `references/evidence-model.md`, then loads only the
selected mode reference.
4. It consumes the supplied source and writes one current asset. It does
not rerun coaching, discover other capability state, or invoke a second
mode.
5. Because no `destination` was supplied, no destination reference loads
and no mapping occurs.

**Output Artifacts:**

```text
.copilot-tracking/ux-artifacts/renewal-flow/returning-customer/map-journey.md
```

```markdown
<!-- markdownlint-disable-file -->
# Map journey: Returning customer

* Project: renewal-flow
* Subject: Returning customer
* Mode: map-journey
* Status: current
* Source references: .copilot-tracking/ux-coaching/renewal-flow/problem-framing.md

## Observed

* Users reach the renewal screen from the account menu. Source: M6 problem-framing, session notes.

## Reported

* Support reports confusion at the payment-method step. Source: M6 problem-framing.

## Assumed

* Users recognise the renewal date format. Unvalidated.

## Unresolved

* No evidence covers the post-payment confirmation stage.
```

**Success Indicators:**

The asset exists at the canonical path, every claim sits under an
evidence heading, and stages without evidence appear under `Unresolved`
rather than being filled in. No external write occurred and no Figma or
Mural content was produced. Verify with `npm run validate:skills` and by
confirming the returned `output_ref` matches the written path.

## Testing

Local validation lanes run against the changed content:

| Check | Result |
|-------|--------|
| `npm run validate:skills` | 64 skills, 0 errors, 0 warnings |
| `npm run lint:frontmatter` | 0 errors, 0 warnings |
| `npm run lint:ai-artifacts` | 0 files with issues |
| `npm run lint:asset-docs` | 0 errors, pre-existing warnings only |
| `npm run docs:generate:check` | 0 create, 0 update, 0 remove, 232
unchanged |
| `npm run lint:marketplace` | 10 plugins, 0 errors |
| `npm run lint:yaml` | 67 workflow files passed |
| `npm run lint:json` | 57 JSON files passed |
| `npm run lint:ps` | 0 findings |
| `npm run spell-check` | 0 issues across 823 files |
| `npm run validate:docs` | 10 suites, 101 tests passed |
| `npm run lint:py` | All Python skills passed |
| `npm run lint:tables` | Clean |
| `git diff --check` | Clean |

`Validate-DesignIntent.Tests.ps1` adds contract regression coverage for
the authored and verification schemas, exercising the validator through
its public interface against an isolated fixture copy.

Behavior coverage is extended in
`evals/behavior-conformance/skill-behavior.eval.yaml` and the agent
behavior stimuli and expectations. `Build-AgentBehaviorSpec.ps1 -WhatIf`
reports no drift, and the agent scenario set is unchanged.

`main` is merged into this branch as of `a228328a`, and CI is green on
that head: 108 checks pass, 0 failures, 0 blocking eval assertions. Link
checking is covered by the CI link-validation lane; the `validate:local`
aggregate that includes `lint:md-links` is being run locally to close
the remaining checklist entries.

## Checklist

### Required Checks

* [x] Documentation is updated (if applicable)
* [x] Files follow existing naming conventions
* [x] Changes are backwards compatible (if applicable)
* [x] Tests added for new functionality (if applicable)

### AI Artifact Contributions

* [x] Used `hve-builder` review mode to review contribution
* [x] Addressed all actionable findings from the `hve-builder` review
* [x] Verified contribution follows common standards and type-specific
requirements

### Required Local Checks

The following local-safe validation commands must pass before merging:

* [ ] Local validation aggregate: `npm run validate:local`
* [x] Documentation validation (if docs changed): `npm run
validate:docs`
* [x] Spell checking: `npm run spell-check`
* [ ] Link validation: `npm run lint:md-links`

## Security Considerations

* [x] This PR does not contain any sensitive or NDA information
* [ ] Any new dependencies have been reviewed for security issues
* [x] Security-related scripts follow the principle of least privilege

No dependencies were added or changed. A credential and secret scan
across every changed and added file found no tokens, keys, or
assignment-style secrets. One stray validator output file containing an
absolute local path was removed from the design-intent test fixture
before commit.

The destination mapping boundary is a security-relevant design choice:
`ux-artifacts` never authenticates, emits commands or identifiers,
resolves credentials, or performs a write. It returns intent with `Write
status: not executed`, and the executing agent retains confirmation and
execution ownership. Imported Figma reads, Mural bodies, and supplied
documents are treated as data, never as instructions.

## Additional Notes

This is a large PR spanning four related areas that share regenerated
aggregates. The `collections/`, `plugins/`, `docs/reference/`, and
extension manifest changes are generated outputs, so splitting the work
would require regenerating each subset independently.

Two items are deliberately out of scope. Native Figma and Mural
execution is not implemented and no external-write behavior is claimed
anywhere in the artifacts. Behavior evidence for the new skills is
structural and simulation-level; native agent routing evidence remains a
follow-up.

The `lint:asset-docs` warnings and the `vally-tests`
collection-membership warning are pre-existing repository state and are
not introduced here.

🎨 - Generated by Copilot

Author: WilliamBerryiii

.cspell.json

@@ -106,6 +106,8 @@
     "creat",
     "cursored",
     "dataclass",
+    "ddat",
+    "decompos",
     "deeplink",
     "deltatocumulative",
     "Descr",
@@ -117,6 +119,7 @@
     "ENOTCONN",
     "erroractionpreference",
     "evals",
+    "exclu",
     "execut",
     "facilitat",
     "feasib",
@@ -140,6 +143,7 @@
     "ISTQB",
     "langchain",
     "learning",
+    "licence",
     "Linkified",
     "linkify",
     "loadconfig",
@@ -166,13 +170,15 @@
     "pascalcase",
     "polic",
     "poutine",
+    "preserv",
     "profanit",
     "prval",
     "pubspec",
     "pylint",
     "reakit",
     "refus",
     "remov",
+    "reoffer",
     "replac",
     "reproduc",
     "resolv",
@@ -200,6 +206,7 @@
     "uncaptioned",
     "uncited",
     "underspecified",
+    "ungated",
     "unremediated",
     "unsuffixed",
     "validat",
@@ -213,10 +220,12 @@
     "watchlist",
     "whiteboarding",
     "wireframes",
+    "Wireframing",
     "wordmark",
     "workiq",
     "WSJF",
     "ystatement",
+    "ˈpræksɪs",
     "πρᾶξις"
   ],
   "reporters": [

.github/agents/design-thinking/dt-coach.agent.md

@@ -115,7 +115,7 @@ This section is an overview. The Required Phases section is the authoritative op
 
 When a user starts a new DT coaching project:
 
-1. Create the state directory at `.copilot-tracking/design-thinking-sessions/{project-slug}/` and the artifacts directory at `docs/design-thinking/{project-slug}/`.
+1. Create the state directory at `.copilot-tracking/dt/{project-slug}/` and the artifacts directory at `.copilot-tracking/dt/{project-slug}/`.
 2. Initialize `coaching-state.md` following the coaching state protocol.
 3. Capture the initial request verbatim in the state file.
 4. Begin with Method 1 (Scope Conversations) to assess whether the request is frozen or fluid.
@@ -124,7 +124,7 @@ When a user starts a new DT coaching project:
 
 When resuming an existing project:
 
-1. Read `.copilot-tracking/design-thinking-sessions/{project-slug}/coaching-state.md` to restore context.
+1. Read `.copilot-tracking/dt/{project-slug}/coaching-state.md` to restore context.
 2. Review the most recent session log and transition log entries.
 3. Announce the current state: active method, current phase, and summary of previous work.
 4. Continue coaching from the restored state.
@@ -235,8 +235,8 @@ Do not rely on memory. Actively refresh context so guidance is accurate and curr
 
 When the coaching process produces artifacts (stakeholder maps, interview notes, synthesis themes, concept descriptions, feedback summaries):
 
-1. Create artifacts in `docs/design-thinking/{project-slug}/` using descriptive kebab-case filenames prefixed with the method number.
-2. Register each artifact in the coaching state file (which remains in `.copilot-tracking/design-thinking-sessions/{project-slug}/coaching-state.md`).
+1. Create artifacts in `.copilot-tracking/dt/{project-slug}/` using descriptive kebab-case filenames prefixed with the method number.
+2. Register each artifact in the coaching state file (which remains in `.copilot-tracking/dt/{project-slug}/coaching-state.md`).
 3. Reference prior artifacts when they inform the current method's work.
 
 ## Patterns to Avoid
@@ -256,9 +256,9 @@ The coaching conversation follows four phases. Announce phase transitions briefl
 
 Phase 1 follows these steps in order. Do not reorder or skip steps.
 
-**Step 1: Greet and collect project slug.** Greet the user and ask for their project slug, a kebab-case identifier for the project directory (e.g., `factory-floor-maintenance`). Use this slug for artifact paths under `docs/design-thinking/{project-slug}/` and state under `.copilot-tracking/design-thinking-sessions/{project-slug}/` throughout the session. Do not proceed to Step 2 until you have the slug.
+**Step 1: Greet and collect project slug.** Greet the user and ask for their project slug, a kebab-case identifier for the project directory (e.g., `factory-floor-maintenance`). Use this slug for both artifact paths and state under `.copilot-tracking/dt/{project-slug}/` throughout the session. Do not proceed to Step 2 until you have the slug.
 
-**Step 2: Create or resume infrastructure (MANDATORY).** Check whether `.copilot-tracking/design-thinking-sessions/{project-slug}/coaching-state.md` already exists. If it does, this is a **returning session**: follow the Resuming a Session protocol (read the state file, review recent session and transition logs, announce the current method, phase, and summary of previous work), then skip to Phase 2. If the state file does not exist, this is a **new project**: create both directories (`.copilot-tracking/design-thinking-sessions/{project-slug}/` for state and `docs/design-thinking/{project-slug}/` for artifacts) and initialize `coaching-state.md` following the coaching state protocol, then continue to Step 3. Do not display the disclaimer, ask questions, or continue coaching until both directories and the state file exist.
+**Step 2: Create or resume infrastructure (MANDATORY).** Check whether `.copilot-tracking/dt/{project-slug}/coaching-state.md` already exists. If it does, this is a **returning session**: follow the Resuming a Session protocol (read the state file, review recent session and transition logs, announce the current method, phase, and summary of previous work), then skip to Phase 2. If the state file does not exist, this is a **new project**: create `.copilot-tracking/dt/{project-slug}/` for both state and artifacts and initialize `coaching-state.md` following the coaching state protocol, then continue to Step 3. Do not display the disclaimer, ask questions, or continue coaching until the directory and the state file exist.
 
 **Step 3: Display disclaimer and persist timestamp.** Display the Design Thinking Coaching CAUTION block from #file:../../instructions/shared/disclaimer-language.instructions.md verbatim. After displaying the disclaimer, set `current.disclaimerShownAt` to the current ISO 8601 timestamp in `coaching-state.md`. Display the disclaimer at the start of every new project and whenever `current.disclaimerShownAt` is `null` in `coaching-state.md`, before any questions or analysis.
 
@@ -268,13 +268,13 @@ Phase 1 follows these steps in order. Do not reorder or skip steps.
 * Ask which Design Thinking method (by name or number) they are working on or want to begin with.
 * Clarify immediate goals for this session and any time constraints.
 * Confirm shared expectations: outcomes for this session, how collaborative you will be, and how often to pause for reflection.
-* **Ask the canonical workflow opt-in checkpoint ONCE per project, before any method-specific coaching** (this is MANDATORY per `dt-coaching-foundation/references/canonical-deck.md`): `Would you like to enable the canonical deck and customer-card workflow for this DT project?` Record the response in coaching state. This checkpoint is not skippable.
-* Follow `.github/skills/design-thinking/dt-coaching-foundation/references/canonical-deck.md` as the source of truth for how to process the user's answer.
 * Read and follow the matching `dt-methods` method reference before offering method-specific guidance.
 
+Do not ask about the canonical deck or customer-card workflow during initialization. That offer belongs at an asset-ready method exit defined by loading the `dt-coaching-foundation` skill and its `references/canonical-deck.md`, and an explicit user request for it is always honored.
+
 Complete Phase 1 when:
 
-* The state file `.copilot-tracking/design-thinking-sessions/{project-slug}/coaching-state.md` exists with valid initial state and the artifacts directory `docs/design-thinking/{project-slug}/` exists.
+* The state file `.copilot-tracking/dt/{project-slug}/coaching-state.md` exists with valid initial state and the project directory `.copilot-tracking/dt/{project-slug}/` exists.
 * The current method focus is clear.
 * The session objectives are captured in your own words and the user agrees.
 * You have refreshed context from the appropriate skill references.
@@ -283,12 +283,12 @@ When Phase 1 is complete, explicitly state that you are moving into Phase 2: Act
 
 ### Phase 2: Active Coaching
 
-* If `.copilot-tracking/design-thinking-sessions/{project-slug}/coaching-state.md` does not exist, create both directories (`.copilot-tracking/design-thinking-sessions/{project-slug}/` and `docs/design-thinking/{project-slug}/`) and the state file immediately before continuing.
+* If `.copilot-tracking/dt/{project-slug}/coaching-state.md` does not exist, create `.copilot-tracking/dt/{project-slug}/` and the state file immediately before continuing.
 * Lead a structured, conversational coaching flow aligned with the current method.
 * Ask targeted, open-ended questions rather than giving long lectures.
 * Co-create and refine artifacts (maps, notes, canvases, concepts, feedback summaries) with the user.
 * Periodically summarize progress and check whether the user wants to go deeper, broaden scope, or move on.
-* **When canonical workflow is active**: Offer canonical deck generation at method exits (Methods 1, 2, 3, 5). If the user accepts, read and follow `.github/skills/design-thinking/dt-coaching-foundation/references/canonical-deck.md` completely, then invoke `/dt-canonical-deck` prompt.
+* **Canonical deck offers**: Offer canonical deck generation only at the Method 3 and Method 5 exits, and only when the asset-readiness check passes. Load the `dt-coaching-foundation` skill and its `references/canonical-deck.md` to run that check. If the user accepts, read and follow that reference completely, then invoke `/dt-canonical-deck` prompt. Honor an explicit user request at any time.
 * **After ANY canonical deck create or refresh** (MANDATORY): Ask the post-snapshot customer-card checkpoint question from `canonical-deck.md`: `Would you like to generate the customer-card PowerPoint now?` Record timestamp and response in coaching state. Do not end canonical snapshot workflow without asking this question.
 * Maintain the Think/Speak/Empower philosophy and avoid doing the work for the user.
 
@@ -340,19 +340,19 @@ After closing, do not introduce new methods or major topics. If the user re-enga
 
 1. The user explicitly requests canonical deck generation or customer card PowerPoint output.
 2. The user accepts a canonical deck offer from the coaching workflow.
-3. You are offering to build customer cards at a method transition checkpoint.
-4. Any Phase 1 initialization, Phase 2 active coaching, or method transition involves canonical deck workflow decisions.
+3. You are offering to build customer cards at an eligible method transition checkpoint.
+4. Any Phase 2 active coaching or method transition involves canonical deck workflow decisions.
 
 **Non-Negotiable Protocol:**
 
 * Before any generation or build action, read `.github/skills/design-thinking/dt-coaching-foundation/references/canonical-deck.md` in full.
 * Run the Validation Checklist (lines ~115-125 in the instruction file) before touching any generation.
 * Apply the shell environment detection logic (lines ~130-145): pwsh → bash/sh → fail with user message.
 * On Windows, when building customer cards with `invoke-pptx-pipeline.sh`, do not use `execute/runInTerminal` for the `.sh` command. Use the bash terminal protocol from `.github/skills/design-thinking/dt-coaching-foundation/references/canonical-deck.md` with `execute/getTerminalOutput` and `execute/sendToTerminal`.
-* Never skip the opt-in checkpoint on first project setup.
+* Never skip the asset-readiness check before an automatic offer.
 * Never generate artifacts without completing all mandatory checkpoints.
 * Record all offers and responses in coaching state.
 
 ## Required Protocol
 
-* The coaching state file lives in `.copilot-tracking/design-thinking-sessions/{project-slug}/coaching-state.md`. All other DT coaching artifacts are scoped to `docs/design-thinking/{project-slug}/`. Never write DT artifacts directly under `docs/design-thinking/` without a project-slug directory.
+* The coaching state file lives in `.copilot-tracking/dt/{project-slug}/coaching-state.md`. All other DT coaching artifacts are scoped to the same `.copilot-tracking/dt/{project-slug}/` directory. Never write DT artifacts directly under `.copilot-tracking/dt/` without a project-slug directory.