This was generated by AI during triage.
Two related framing defects in the interview skill's session-config guidance, both advisory prose (no gate, reversible):
session-config.md "Inverse direction — mid-task" is phrased as an imperative to an executing actor, but /interview terminates at handoff and nothing wires this context into the downstream execution session, so read as runtime behavior it never fires.session-config.md frames its recommendation as configuring "the downstream execution session," but SKILL.md Step 5 makes a general session terminal with no downstream consumer, while the deliberate "Both domains" section extends the recommendation to general sessions — producing model/effort/advisor guidance for a session that will not exist.
Decision defaulted: reframe the mid-task rule as guidance the interview hands the USER at handoff ("watch for these signals during execution"), consistent with the file's own advisory-framing section; and for general/terminal sessions frame the recommendation as config for the current/next session applied now, preserving the deliberate "Both domains" scope — veto before merge. Maintainer-vetoable alternative: relocate the mid-task rule into the execution/implement workflow where an agent is actually running.
Acceptance: no session-config prose reads as a runtime imperative to a nonexistent downstream session; general-session guidance is framed as current/next-session config; the "Both domains" scope is retained.
Sweep-converted from #657.
This was generated by AI during triage.
Two related framing defects in the interview skill's session-config guidance, both advisory prose (no gate, reversible):
session-config.md"Inverse direction — mid-task" is phrased as an imperative to an executing actor, but/interviewterminates at handoff and nothing wires this context into the downstream execution session, so read as runtime behavior it never fires.session-config.mdframes its recommendation as configuring "the downstream execution session," but SKILL.md Step 5 makes a general session terminal with no downstream consumer, while the deliberate "Both domains" section extends the recommendation to general sessions — producing model/effort/advisor guidance for a session that will not exist.Decision defaulted: reframe the mid-task rule as guidance the interview hands the USER at handoff ("watch for these signals during execution"), consistent with the file's own advisory-framing section; and for general/terminal sessions frame the recommendation as config for the current/next session applied now, preserving the deliberate "Both domains" scope — veto before merge. Maintainer-vetoable alternative: relocate the mid-task rule into the execution/implement workflow where an agent is actually running.
Acceptance: no session-config prose reads as a runtime imperative to a nonexistent downstream session; general-session guidance is framed as current/next-session config; the "Both domains" scope is retained.
Sweep-converted from #657.