[P1][DATA-04] Goal compiler and coordinated plans

Programme: #1
Epic: #17

## Objective
Compile user intent and durable constraints into a coherent data plan, view definition, executable action proposals and verification requirements.

## Scope
- Define `GoalContract`: original request, clarified constraints, authorized resources/accounts, privacy/inference mode, budgets/deadlines, desired representation, success predicate and approval requirements.
- Query/source planning against installed connector capabilities.
- UI plan against the declarative component catalogue.
- Action bindings that resolve to real capability IDs and exact argument schemas.
- Verification plan for each consequential task/action.
- Compiler diagnostics for missing capability, ambiguous target, stale source or unsatisfied constraint.
- Incremental recompilation preserving the last valid view.

## Product rules
- A generated button is invalid unless it resolves to an installed capability under current account/resource semantics.
- User edits to constraints/layout compile into updated plans without requiring conversational reconstruction.
- Authorization remains a separate broker decision; compilation never grants authority.

## Acceptance criteria
- [ ] One goal produces coordinated source queries, view bindings, permitted action proposals and verification predicates.
- [ ] A generated action resolves a real installed operation or is rejected before rendering as actionable.
- [ ] Failed recompilation leaves the previous valid view usable.
- [ ] Missing/ambiguous capabilities produce explicit diagnostics and Original-view fallback where appropriate.
- [ ] Goal constraints remain durable across provider/model switches and conversation compaction.
- [ ] Compilation output is deterministic for the same normalized inputs where model-free planning is sufficient.

## Dependencies
- CORE-01
- DATA-01
- CONN-01
- UI-01

**First phase:** P1
**Maturity target:** P3
**Owner:** workspace-ui-data

## Task issues
- [ ] #366 `DATA-04.T01` — Implement GoalContract editing and normalization
- [ ] #367 `DATA-04.T02` — Build capability-aware source planning
- [ ] #368 `DATA-04.T03` — Compile views from available typed data
- [ ] #369 `DATA-04.T04` — Bind actions to exact capabilities
- [ ] #370 `DATA-04.T05` — Compile independent verification requirements
- [ ] #371 `DATA-04.T06` — Validate and atomically publish coordinated plans
- [ ] #372 `DATA-04.T07` — Implement incremental recompilation and plan diffs
- [ ] #373 `DATA-04.T08` — Test compiler correctness and useful diagnostics

No implementation files, tests, or entry points are named. Start by reading the dependency issues CORE-01, DATA-01, CONN-01, and UI-01, then review task issues #366–#373 to find the relevant implementation boundaries. Done means coordinated plans satisfy the listed acceptance criteria, including rejection diagnostics, safe fallback, durable constraints, deterministic output, and compiler tests.

Written by the indexing model from the issue text.