Follow-up from PR #54 (per-parent-task delegation tree).
The cross-process linkage (parent_task_id) depends on the orchestrator CLI forwarding its env to
the MCP delegate child it spawns — a load-bearing assumption verified manually for claude but
not asserted by any hermetic or standing live test. If a future CLI version stops forwarding env
(or a roster adds TANGLEBRAIN_TASK_ID to an orchestrator's invoke.scrub_env), every delegate
silently rolls up as unlinked with no signal.
Suggested
Add a gated live smoke check (behind TANGLEBRAIN_LIVE, like the other live tests) that runs a real
orchestrator → delegate_local and asserts the delegate record's parent_task_id matches the
parent task record's task_id. Keeps the assumption honest across CLI upgrades.
Low priority — the feature degrades safely (unlinked, never an error) if the assumption breaks.
Follow-up from PR #54 (per-parent-task delegation tree).
The cross-process linkage (
parent_task_id) depends on the orchestrator CLI forwarding its env tothe MCP delegate child it spawns — a load-bearing assumption verified manually for claude but
not asserted by any hermetic or standing live test. If a future CLI version stops forwarding env
(or a roster adds
TANGLEBRAIN_TASK_IDto an orchestrator'sinvoke.scrub_env), every delegatesilently rolls up as
unlinkedwith no signal.Suggested
Add a gated live smoke check (behind
TANGLEBRAIN_LIVE, like the other live tests) that runs a realorchestrator →
delegate_localand asserts the delegate record'sparent_task_idmatches theparent task record's
task_id. Keeps the assumption honest across CLI upgrades.Low priority — the feature degrades safely (unlinked, never an error) if the assumption breaks.