Fix TSV column misalignment in runtime-canon-divergence journal

Author: cursoragent

journal/2026-05-10-runtime-canon-divergence.tsv

@@ -1,5 +1,5 @@
 type	typeName	facet	quality_score	quality_max	quality_level	title	content
-O	Observation			4	5	medium	Two runtime docs in this PR represent two iterations of the same architectural concept	The prior compacted session produced spawned-agent-session-runtime-contract.md (Tier 2, draft, five-orthogonal-dimensions framing: persona, mode, role, surface, engagement). The current session produced persona-shaped-agent-runtime.md (Tier 1, proposed, mode-bound-roles framing aligned to operator's later guidance about session-per-mode discipline). Both files are committed to preserve the work, but they overlap heavily and would be confusing if both landed as canon. Operator should pick one or reconcile during review.
-L	Learning			4	5	medium	Engagement (assistant vs agent) is a useful dimension missing from the persona-shaped framing	The runtime-contract draft introduced an "engagement" dimension distinguishing turn-based dialogue (assistant — clarifying questions valid; yields turn-control) from autonomous run-to-completion (agent — clarifying questions forbidden per bottleneck-respect canon). This dimension is genuinely orthogonal to persona, mode, role, and surface, and is missing from the persona-shaped doc. If the persona-shaped doc is selected as canonical, engagement should be folded in.
-D	Decision			3	5	medium	Recommend persona-shaped-agent-runtime as the canonical doc; runtime-contract as historical context	The persona-shaped doc reflects operator's later directives (five-role taxonomy, sessions-mirror-modes derivation, mode-transitions-require-encoded-handoff derivation) and aligns with the new principle and constraint that just landed in the parallel mode-discipline canon PR. The runtime-contract draft predates that guidance. Recommend keeping persona-shaped as canon and either (a) folding engagement-dimension content into persona-shaped before merge, or (b) keeping runtime-contract as a draft sibling for the engagement-dimension framing if operator wants it preserved.
-H	Handoff			4	5	medium	Runtime canon ready for review; depends on PR A (substrate options) and PR C (mode-discipline canon)	PR D references URIs that land in PR A (klappy://canon/methods/spawned-agent-session-substrate-options) and PR C (klappy://canon/principles/sessions-mirror-modes, klappy://canon/constraints/mode-transitions-require-encoded-handoff). Recommend merging PR A and PR C first; PR D's URIs resolve once they land. Operator should also reconcile the two runtime docs before this PR merges.
+O	Observation		4	5	medium	Two runtime docs in this PR represent two iterations of the same architectural concept	The prior compacted session produced spawned-agent-session-runtime-contract.md (Tier 2, draft, five-orthogonal-dimensions framing: persona, mode, role, surface, engagement). The current session produced persona-shaped-agent-runtime.md (Tier 1, proposed, mode-bound-roles framing aligned to operator's later guidance about session-per-mode discipline). Both files are committed to preserve the work, but they overlap heavily and would be confusing if both landed as canon. Operator should pick one or reconcile during review.
+L	Learning		4	5	medium	Engagement (assistant vs agent) is a useful dimension missing from the persona-shaped framing	The runtime-contract draft introduced an "engagement" dimension distinguishing turn-based dialogue (assistant — clarifying questions valid; yields turn-control) from autonomous run-to-completion (agent — clarifying questions forbidden per bottleneck-respect canon). This dimension is genuinely orthogonal to persona, mode, role, and surface, and is missing from the persona-shaped doc. If the persona-shaped doc is selected as canonical, engagement should be folded in.
+D	Decision		3	5	medium	Recommend persona-shaped-agent-runtime as the canonical doc; runtime-contract as historical context	The persona-shaped doc reflects operator's later directives (five-role taxonomy, sessions-mirror-modes derivation, mode-transitions-require-encoded-handoff derivation) and aligns with the new principle and constraint that just landed in the parallel mode-discipline canon PR. The runtime-contract draft predates that guidance. Recommend keeping persona-shaped as canon and either (a) folding engagement-dimension content into persona-shaped before merge, or (b) keeping runtime-contract as a draft sibling for the engagement-dimension framing if operator wants it preserved.
+H	Handoff		4	5	medium	Runtime canon ready for review; depends on PR A (substrate options) and PR C (mode-discipline canon)	PR D references URIs that land in PR A (klappy://canon/methods/spawned-agent-session-substrate-options) and PR C (klappy://canon/principles/sessions-mirror-modes, klappy://canon/constraints/mode-transitions-require-encoded-handoff). Recommend merging PR A and PR C first; PR D's URIs resolve once they land. Operator should also reconcile the two runtime docs before this PR merges.