Repository navigation
Mark the October 27 security plan merged - #724
sambitcreate wants to merge 2 commits into
Conversation
There was a problem hiding this comment.
Important
The merged-stack status is accurate, but the plan's acceptance ledger remains stale and should be reconciled before this documentation update merges.
Reviewed changes the plan-index row and security-plan status line were checked against the referenced pull requests, release inventory, and the plan's remaining acceptance gates.
- Plan index — Changes the October 27 security remediation entry from in progress to merged, distinguishing shipped, unreleased, and separately tracked acceptance work.
- Plan status — Records #604 and #606 through #614 as merged, #605 as closed, and preserves the release/device-acceptance distinction.
@v0 or keep the SHA fresh with Dependabot | Fix all ➔ | Fix 👍s ➔ | View workflow run | Using GPT Sol | 𝕏
…edger Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018VA6RHWP6kkCRLYaa5exc8
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes since the prior Pullfrog review, I checked the dated merge ledger and remaining acceptance gates against GitHub’s PR metadata and the plan’s completion criteria.
- Recorded the merged stack — Added each landed slice’s exact head, merge commit, and merge date, while identifying the older execution entries as pre-merge snapshots.
- Preserved outstanding acceptance — Kept packaged-app, physical-device, live-network/proxy/custom-TLS, release, deferred protocol, and publisher-verification work open rather than treating merge as full acceptance.
@v0 or keep the SHA fresh with Dependabot | View workflow run | Using GPT Sol | 𝕏

Requested by sbt · project thread
Summary
The October 27 security remediation stack has landed. #608 through #614 merged on November 3, 2026, after #604, #606 and #607 (in 0.63.0). #605 was closed because Telegram is being removed. This updates the plan's status line and its row in
docs/plans/README.mdto match. The plan stays indocs/plans/because release and device acceptance are still separate steps.Docs only, no code changes.
Generated by Claude Code