v0.4.4

consort v0.4.4

• Deploy lane carries through to promote. consort-drive --only deploy on a built feature now runs deploy then promote and offers the PR/merge prompt (the deploy-bound stopWhen admits the ship "coarse" lane), instead of halting after deploy.
• Staging stays in sync after merge. The done effect fast-forwards local staging to origin/<parent> after the server-side squash merge, ending the false "local not in sync" alarm.
• Schema-change conformance. A pre-reflect check flags a test whose schema_change_id is not declared in db-design schema_changes[]; Gate 3 requires every test-worthy change (create_table / add_index / add_constraint) to be covered. The DBA now emits stable SC<n> ids.
• API-contract consistency (Gate 3). The architect declares api_contracts[] (EP ids); a conflicting duplicate endpoint shape and a dangling api_contract_id both fail closed. annotate-ac --api-contract writes the AC-to-contract link.
• driver-green receives architecture.json as input, so GREEN builds against the declared contracts.
• Dashboard RUN view. approve-intake / backlog / plan / deploy / promote gates emit paired gate.surfaced + gate.approved, so gate turns get #N in the event log; planning-lane cards are clickable; the deploy and promote gate cards flash at their gate; the design-loop VERIFY card lights only on cycle.verified (release-engineer color, not gate purple).