docs(plan): drop stale sequential refs from Backlog items 11-14 - #69
Merged
Merged
Conversation
Backlog items 11-14 used sequential enumeration (#64/#65/#66/#67) as intra-doc bookkeeping. Those numbers now collide with actual merged PRs and open issues with completely different scopes: - PR #64 = auto-refresh global_secrets (not "delegations list") - PR #65 = restart context Layer 1 (not "per-agent repo access") - Issue #66 = restart_prompt Layer 2 (not "SDK swallows stderr") - PR #67 = docs sync tick-4 (not "MCP localhost default") Strip the misleading refs and add a footnote explaining the cleanup. If/when any of these items get prioritized, file real GitHub issues. Tracked in cron-learnings tick-3 entry. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
HongmingWang-Rabbit
pushed a commit
that referenced
this pull request
Apr 14, 2026
- docs/edit-history/2026-04-14.md — append tick-5 section covering PR #69 (PLAN.md backlog stale-ref cleanup) and PR #70 (wire 12 modular plugins from PR #63 into the default molecule-dev org template; defaults 3 → 9 plus PM + Security Auditor role extras). - PLAN.md — add tick-5 entries under "Recently launched" noting PR #70 activated the tick-4 plugins and PR #69 cleaned up stale backlog refs. Both merges are docs/template-only. No code surface moved, no new env vars, no test-count drift. CLAUDE.md, .env.example, README.md, and README.zh-CN.md unchanged. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2 tasks
molecule-ai Bot
pushed a commit
that referenced
this pull request
Apr 21, 2026
docs(plan): drop stale sequential refs from Backlog items 11-14
molecule-ai Bot
pushed a commit
that referenced
this pull request
Apr 21, 2026
- docs/edit-history/2026-04-14.md — append tick-5 section covering PR #69 (PLAN.md backlog stale-ref cleanup) and PR #70 (wire 12 modular plugins from PR #63 into the default molecule-dev org template; defaults 3 → 9 plus PM + Security Auditor role extras). - PLAN.md — add tick-5 entries under "Recently launched" noting PR #70 activated the tick-4 plugins and PR #69 cleaned up stale backlog refs. Both merges are docs/template-only. No code surface moved, no new env vars, no test-count drift. CLAUDE.md, .env.example, README.md, and README.zh-CN.md unchanged. Co-Authored-By: Claude Opus 4.6 (1M context) <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.
Closes the cron-learnings follow-up flagged in tick-3.
The refs were intra-doc placeholder enumeration, not GitHub issue links. They now collide with actual merged PRs/issues with different scopes and would mislead any reader who clicks them.
Change
#64/#65/#66/#67from items 11-14If any of items 11-14 get prioritized, file real GitHub issues then.
🤖 Generated with Claude Code