Resolve node 184 open question in fix-hera-plan-dag-hygiene design.md - #915
Merged
Conversation
…ollow-up)
Aaron decided (relayed via the hera-leaks coordinator) to cancel planned node
184 ("2a-team" under sherlock-mvp) rather than assign it a project. Folds into
the retroactive Part 2 cleanup already planned for fix-hera-plan-dag-hygiene
(#914) — no code change, CancelHeraPlannedNode already exists.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
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
Follow-up to #914 (merged). Aaron decided — relayed via the "hera-leaks" coordinator (hera message #3875) — to cancel planned node 184 ("2a-team" under orchestrator "sherlock-mvp") rather than assign it a project, resolving the open question left in
fix-hera-plan-dag-hygiene's design.md.design.md's Open Questions + Migration Plan sections to record the resolution and foldCancelHeraPlannedNode(184)into the same retroactive Part 2 cleanup already planned for that change.CancelHeraPlannedNodealready exists (used by the same PR for nodes 343/358); node 184 just needs the same call once someone with host access runs the (already-prepared, backup-first) migration script.Test plan
make pre-pr: build/vet/fmt-check/lint-pr clean; vuln stdlib-only (advisory, same asmaster); full test suite green except the twointernal/agentprofile-env tests, which are the documented pre-existing hera-worker-sandbox env-contamination artifact (unrelated to this doc-only diff).🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com