docs(plans): refresh plan index and status for 0.51.0 - #297
sambitcreate wants to merge 1 commit into
Conversation
Hermes Review BotConfidence: 5 Engine: SummaryReorganizes completed implementation plans and synchronizes documentation status with the 0.51.0 release and subsequent Confidence Score: 5/5Every relocated plan, cited PR number, internal markdown link, and memory note reference was mechanically verified against the repository filesystem and 📁 Important Files Changed
FindingsNo findings. 📊 Sequence DiagramUnchanged or not applicable for this change. Machine-Readable Findings[]
|
![pullfrog[bot]](https://avatars.githubusercontent.com/in/1768019?s=60&v=4){kind=small}
There was a problem hiding this comment.
ℹ️ One plan-status correction inline; no blocking issues.
Reviewed changes This run reviewed the plan inventory refresh and related historical status updates against the current main base.
- Plan inventory:
docs/plans/README.mdreflects 0.51.0 and later merges, separates active and completed plans, and adds shipped work without standalone plans. - Historical plan records: Completed plan documents are relocated and annotated with merge/release status and follow-ups.
- Project memory and active plans:
.memory/references and ongoing plan summaries are updated to match the refreshed inventory.
GPT Luna ｜ 𝕏
| | [Taracodlab Learnings](taracodlab-learnings-plan.md) | Partial | Phases A–B and D, plus core Phase E, are implemented; the remaining roadmap is open. | | ||
| | [Live Activity freshness chips and Bot deep links](live-activity-freshness-bot-deeplinks-plan.md) | Implemented for review | iOS Live Activities show a bounded tool-call chip and a self-updating "Updated Xs ago" / "Stale" chip; `aiden-otg://bot/{id}/chat` opens the Bot's canonical chat on iOS and Android without creating chats. Android notification chips and physical-device acceptance remain. | | ||
| | [Hermes-inspired Bot run control](hermes-bot-run-control-plan.md) | Active | Telegram bounded queue, cancellation and canonical-chat shipped; shared foreground input admission (`chat-run-input-v1`) shipped on `feature/on-the-go-midflight-ops`; busy-composer Steer/Queue/Redirect and pending `ask_user_question` prompts (`chat-question-prompts-v1`) shipped on iOS + Android. | | ||
| | [Hermes-inspired Bot run control](hermes-bot-run-control-plan.md) | Active | Telegram bounded queue, cancellation and canonical-chat shipped; shared foreground input admission (`chat-run-input-v1`) merged in PR #251; busy-composer Steer/Queue/Redirect and pending `ask_user_question` prompts (`chat-question-prompts-v1`) shipped on iOS + Android. PRs #220 and #223 remain open. | |
This branch has not been deployed
2 participants
Supersedes #274, which conflicted with main and was stale. This refresh carries over #274's verified status updates and re-bases them on current
main(0.51.0 plus later merges, atd2197dfef). I checked each PR's title and description before recording what it did.Moved to
docs/plans/completed/From #274 (0.43.0 / 0.50.0 / older):
Shipped in 0.51.0:
On main after 0.51.0, not yet released:
Each moved plan gets a
Status: Complete — merged in PR #…line that names its remaining follow-ups. The README's active row for rpiv-advisor pointed at a file that had already moved, so that row now lives under Completed.Active plan status updates
rowState/unreadsummary hints (feat(chats): chat row states and honest unread markers #280, revision 18).Shipped without a plan doc (new Completed sub-table)
No plan impact
#262, #288 (beyond the perf note), #291, #292, #293, #294, #295 and #296 are fixes, CVE bumps, flake fixes or papercut removal, so they change no plan status.
Other
.memory/notes now record the completion status, and their plan paths point todocs/plans/completed/.web-access-rehaul-plan.mdlinks to the moved key-pool plan.Checks
docs/plans/*.mdanddocs/plans/completed/*.mdresolves.git diff --checkis clean apart from an existing Markdown hard-break. No test suite readsdocs/plans.🤖 Generated with Claude Code