fix: require explicit spawn lineage for workers - #15
Closed
araa47 wants to merge 4 commits into
Closed
Conversation
Fail closed when a spawn omits parent lineage so delegated workers cannot silently become root L1 workers. This keeps depth labels, wake routing, and completion deferral aligned with the real worker tree while documenting the new v0.0.7 contract. Made-with: Cursor
🧪 Coverage Report
📄 Coverage by file
|
- Stop normalizing `openclaw` to empty string; preserve in spawned_by - Root spawns (L0→L1) now correctly produce depth=1 instead of depth=0 - resolve_spawn_lineage returns parent.depth+1 for known parents, depth=1 for L0 markers (openclaw, self, legacy root) - Add `--spawned-by self` for L0 cc/cx/cu orchestrators: auto-detects or generates L0 pane name from tmux window title - orca list now shows L0 orchestrator headers (e.g. |-🐋 | L0 openclaw) - Update validate_spawn_context to allow L0 markers as spawned_by - Update SKILL.md with L0 cc/cx/cu instructions (self marker) - Fix 5 broken tests, add 13 new tests (606 total, all passing) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Replace normalize_spawned_by/resolve_self_l0_name with ensure_l0_orchestrator that auto-registers L0 entries (openclaw or cc/cx/cu) in state at depth=0 - Workers spawned by L0 now correctly get depth=1 (🐳 L1) via parent lookup - print_tree shows L0 orchestrator entries as group headers with backend info - cmd_kill protects virtual openclaw L0 entries from being killed - cmd_killall/cmd_gc skip L0 orchestrator entries (bookkeeping, not workers) - Validate spawn context before L0 registration to avoid side effects on error - Remove L0 window rename from spawn.rs (now handled by ensure_l0_orchestrator) - Update integration tests to use depth=1/spawned_by=openclaw for seeded workers Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Owner
Author
|
Superseded by #16, which includes all these changes plus test extraction and the kill-instruction fix. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--spawned-byon everyorca spawncall and normalizeroot/root:<scope>markers for top-level orchestrator spawnsL1workers with the wrong emoji, wake target, or completion behavior0.0.7and update docs/tests for the explicit lineage contractTest plan
cargo fmtcargo testcargo clippy -- -D warningsMade with Cursor