Stop `additionalContext` — ork opts out #2269

CC 2.1.163 made Stop/SubagentStop additionalContext legal again. ork keeps the door closed on purpose. This PR corrects the stale comments that said it was impossible — without changing behavior.

CC 2.1.78error-loop fixed

API errors triggered Stop hooks that re-fed the error to the model → infinite loop. ork hard-ruled: Stop hooks return silent success, never additionalContext.

CC 2.1.163Stop additionalContext permitted

"Stop and SubagentStop hooks can now return hookSpecificOutput.additionalContext to give Claude feedback and keep the turn going without being labeled a hook error."

ork #2269deliberate opt-out

No consumer asks for it, and re-enabling re-opens the 2.1.78 loop surface. ork keeps silent success — but the comments now say "opts out" instead of "impossible."

✗ stale comment (pre-#2269) Implies the capability is forbidden / impossible.

This dispatcher MUST always return
outputSilentSuccess() — never produce
additionalContext … (CC 2.1.78)

✓ reframed (#2269) States the deliberate opt-out + cites 2.1.163.

As of CC 2.1.163, Stop/SubagentStop MAY
return additionalContext … but ork
deliberately opts out: no consumer, and
re-enabling risks the 2.1.78 loop.

What changed

stop/unified-dispatcher.ts — 2 comment blocks reframed comment
stop/stop-failure-handler.ts — opt-out wording comment
lifecycle/perf-snapshot.ts — discard rationale comment
hooks/README.md — Stop event note docs
__tests__/lifecycle-output-protocol.test.ts — assertion is event-scoped & accurate no change

Runtime behavior unchanged · Biome ✅ · tsc ✅ · dist unaffected (comments stripped by esbuild)

Stop additionalContext — ork opts out #2269

What changed

Stop `additionalContext` — ork opts out #2269