chore: review two preserved historical branches

[mherod]

Preserved historical branches

End-of-day audit found two pre-session commits that are not patch-equivalent to current main and have no matching PR. Both branches remain intact; the linked worktree is clean. Their continued intent is unclear, so this is an ownership/intent review before publication, not an implementation-ready request.

Owner: @mherod.

Branch	Commit	Existing change
codex/dependabot-major-isolation	34d05bb9a864b3d154a2ef8121973b1cda0a227d (7 August)	Removes the grouped major-update rule from .github/dependabot.yml.
codex/docs-pushpatrol-guardrails	3fee9be992b1e86b7400da224c8c7c9b2289ef26 (31 July)	Adds local delivery/dependency-validation guidance to CLAUDE.md.

Next action

1. Review each commit against current policy and confirm whether its original intent is still wanted. Current main retains the major-update group; the older delivery guidance is absent.
2. For wanted work, update it against current main, validate normally, publish the named branch and open exactly one PR. Preserve the old branch until that PR exists.
3. For abandoned work, record that decision before any scoped branch/worktree cleanup. Do not infer abandonment from age or a clean checkout.

Resume on the existing local checkout:

cd /Users/matthew.herod/Development/get-cookie
git switch main
git show 34d05bb9a864b3d154a2ef8121973b1cda0a227d
git show 3fee9be992b1e86b7400da224c8c7c9b2289ef26

The second branch's existing worktree is /Users/matthew.herod/.codex/worktrees/get-cookie-pushpatrol-guidance; keep it registered while the decision is unresolved. Neither branch was rewritten, deleted or included in today's MCP/browser delivery.

Completion: both branches have either a reviewed PR with remote parity or an explicit owner decision that the work is obsolete. This follow-up records the classification gap; it does not claim the local changes are shipped.