Add ISAC mechanic gap handoff actions

docs/DESIGN_SYSTEM.md

@@ -2041,6 +2041,11 @@ its state to assistive technology. Focus remains in the active field when the
 generated script refreshes, and reduced-motion preferences remove expansion
 and replacement transitions.
 
+The recipe starter opens with no recipe selected. Keep its count, duration, and
+distance parameters hidden until the author chooses a recipe. Disable `ADD
+RECIPE BRANCH` while the selection is empty, and show `REPLACE PROGRAM` only
+after the author selects a recipe and the current program contains a branch.
+
 #### AI mechanic drafting
 
 `MechanicProgramEditor` keeps its complete manual authoring controls available
@@ -2075,6 +2080,16 @@ The panel presents five explicit states:
 - `DRAFT PREVIEW` shows assumptions, warnings, readiness, and the generated
   script before an explicit `APPLY TO EDITOR` action.
 
+The capability-gap state offers `COPY DEVELOPER PROMPT` and `SUBMIT TO ADMIN
+TEAM` beside `REVISE SOURCE WORDING`. The copied prompt includes the exact
+analyzed wording, clarification answers, gap evidence, and implementation
+acceptance criteria. Submission sends one mandatory ISAC notification to each
+active full administrator and records the report in the `ai_assistance` audit
+history. Disable duplicate submission for the current assistant request.
+Clipboard or network failures keep the handoff visible and show a specific
+recovery message. Neither action changes the mechanic editor or saves the
+parent record.
+
 Applying a draft fills the structured fields in the current unsaved editor.
 It does not save, publish, submit a proposal, close the editor, or discard
 manual changes without confirmation. Show a concise before-and-after summary

docs/architecture.md

@@ -484,6 +484,17 @@ The model returns one structured result:
   representation, an optional workaround, and the schema, runtime, editor,
   reference, and test changes a developer would need to add support.
 
+For a mechanic capability gap, the client builds a developer prompt from the
+exact analyzed wording, clarification transcript, source profile, and
+structured gap response. The author can copy that prompt without another model
+request. The author can also submit the gap to active full administrators.
+The submission endpoint validates bounded fields, confirms that the request ID
+belongs to the author's audited `capability_gap` generation, suppresses repeat
+submissions, sends mandatory ISAC notifications, and appends a
+`mechanic_gap.submitted` event to the `ai_assistance` audit category. The
+notification links to the filtered audit evidence. Submission does not mutate
+the mechanic draft or parent game-data record.
+
 The server validates `draft_ready` output against the response schema and the
 same deterministic mechanic parser used by manual authoring. Unknown events,
 Attributes, value models, scopes, operators, reducers, or outcomes fail