NEXT temporary contract 3.11 — Bridges and brownfield

01Temporary normative staging unit. Its body is the accepted architecture from refined plan revision 4, section 3.11. Before production code cites this law, promote the relevant clauses into permanent specifications. This file is consumed only after semantic coverage, implemented behavior and retained evidence are accepted. The task/retirement checker cannot perform semantic acceptance.

02Spec Kit and a future external skills bridge become flow in current 1.0.0, retaining lawful upstream provenance. The former external skills component has been removed; a replacement upstream and package identity must be explicitly selected and bound before implementation. Imported resources preserve exact closure and declared non-Vibe semantics; wrapper instructions are separate authored resources. Actual Spec Kit pin governs resource/script/template/platform audit; research snapshot is not substituted.

03Required bridge procedure steps using scripts go through explicit typed admitted action and external-adapter/grant machinery; no implicit script execution merely on read. Native bug/assess are flow-supplied change profiles, not runtime state machine. Native product feat reuse is tested on two stacks with actual controlled existing-file edits after M-03.

04Brownfield observe/propose/promote retains original intent/evidence boundary. Core inventory safe and explicit scope/exclusions; stack analyzers separate operations. Immutable capture or complete affected-set revalidation/exclusion before promote. Prototype does not justify silent overwrite. M-11-D general transition is pulled forward into M-03; later M-11-E proves real brownfield composition.