feat: propagate ADR binding decisions through work plan to task executor

[shinpr]

Summary

• Adds an end-to-end propagation path for ADR implementation-binding decisions: ADR → work plan (ADR Bindings table) → task (Binding Decisions section) → task-executor (pre-implementation and Exit Gate Compliance Checks).
• Introduces a 5-value Axis enum (placement | dependency_direction | contract_schema | data_flow | persistence) so executors consult an explicit column instead of inferring the constraint type from free text.
• Extends task-executor escalation schema with binding_decision_violation (including axis per failure row) and reflects the new type in the orchestrator contract (subagents-orchestration-guide).
• Hardens ADR path resolution: work-planner now globs docs/adr/ADR-XXXX-*.md to match the actual ADR-[4-digit]-[title].md naming convention and escalates on 0 / 2+ matches.
• Adds Exit Gate fallback wording so non-binding gate failures use design_compliance_violation instead of leaving the schema ambiguous.
• Trims per-file context pressure in task-executor, task-executor-frontend, and subagents-orchestration-guide while preserving protected regions (entry / step / exit gates, judgment criteria, JSON schemas, stop points, handoff contracts).
• Bumps version to 0.19.2 and resyncs plugin mirrors.

Files affected (SoT)

• agents/work-planner.md — new section 5c "Map ADR Decisions to Tasks" with axis classification and glob-based path resolution
• agents/task-decomposer.md — ADR Binding Propagation and Design Traceability Propagation steps
• agents/task-executor.md / task-executor-frontend.md — Binding Decision Check, Exit Gate re-evaluation, binding_decision_violation escalation schema with axis
• skills/documentation-criteria/references/plan-template.md — ADR Bindings table with Axis column
• skills/documentation-criteria/references/task-template.md — Binding Decisions section with Axis column
• skills/documentation-criteria/references/design-template.md — explicit docs/adr/ADR-XXXX.md placeholder under Prerequisite ADRs
• skills/subagents-orchestration-guide/SKILL.md — binding_decision_violation added to task-executor escalation enum

All four plugin mirrors (dev-workflows, dev-workflows-frontend, dev-workflows-fullstack, dev-skills) are kept in sync via scripts/sync-plugins.mjs.

Per-file context-pressure reduction

Each subagent loads only its own definition plus the skills declared in its frontmatter, so per-file size is what affects context pressure:

File	Before	After	Δ
agents/task-executor.md	462	444	−18
agents/task-executor-frontend.md	417	395	−22
skills/subagents-orchestration-guide/SKILL.md	433	415	−18

Reductions are limited to duplicated explanatory prose; gates, schemas, and judgment criteria are untouched.

Test plan

• npm run sync:check passes (mirrors in sync)
• claude plugin validate .claude-plugin/marketplace.json passes (no warnings)
• claude plugin validate ./dev-workflows, ./dev-workflows-frontend, ./dev-workflows-fullstack, ./dev-skills all pass
• npm run check:skills-index passes
• Author a sample Design Doc → work plan → task and confirm task-executor's Binding Decision Check evaluates each row to Y against the planned implementation, and the Exit Gate re-evaluates every row against the final implementation

🤖 Generated with Claude Code