Review authors-location-optimization-plan for merge-readiness into deploy branch

You are being dispatched from flower Brief #238: Review authors-location-optimization-plan for merge-readiness into deploy branch

Recall pointer:
- Use recall_brief with id 238 for the full folder if you need provenance.

Target:
- project: lounge (/Users/mikeferrara/Documents/code/lounge)
- branch: choose an appropriate branch
- worktree: not specified
- kind: fresh

Current brief spec:
# Merge-readiness review: `authors-location-optimization-plan` → deploy branch

## Goal
Confirm and document the merge of the `authors-location-optimization-plan` branch into the deploy branch `wip/reddit-scraper-refactor`, and give the orchestrator the exact merge steps. **Operator has green-lit merging the design docs now** (see resolved decisions). First brief in the post-#225 merge-readiness campaign; scoped to this branch only.

## Ground truth (refine daemon, 2026-07-04 — re-verify at run time)
- **Design-docs-only branch.** Single commit ahead of deploy (`3fc73eae`) is pure documentation: 9 files, +4586/-0, all under `docs/authors-optimization/` (README + 00-PRODUCTION-FACTS, 10-perf-and-indexing, 20-proximity-search, 30-location-quality, 40-favorites-filter, 50-favorite-locations-and-settings, 60-frontend-ux-spec, 70-ux-review-notes). No code, migrations, or tests.
- **Merges clean.** `git merge-tree wip/reddit-scraper-refactor authors-location-optimization-plan` → no conflicts. Additive docs in a new dir → zero runtime risk.
- **MAIN's ~10 dirty files are unrelated strays**, not implementation of the plan: `BACKLOG.md` (+6, tracked mod) + untracked `.codex-security/`, `.env.bak.conductor-api`, `.phpactor.json`, `CACHE_NO_TTL_AUDIT.md`, `REDDIT_USER_UPDATE_QUOTAS_AND_SUBSCRIPTIONS_PLAN.md`, `docs/{media-pdq-implementation-todo,reddit-media-dedupe-migration-spec,subreddit-r4r-index-followup,subscription-plan-admin-followup}.md`. Nothing staged. These do NOT gate the merge (it carries only the 1 docs commit) but should be triaged to clean MAIN's tree.

## Deliverable
A concise merge-readiness report (the merge decision is already made — this documents/confirms and hands the orchestrator an executable path):
1. **Confirm characterization** — re-verify branch is still design-docs-only, merges clean, no code/migrations/tests (flag any drift from this snapshot).
2. **Exact merge path** — the precise steps the orchestrator runs per the merge protocol: get a clean working tree → merge `authors-location-optimization-plan` into `wip/reddit-scraper-refactor` → migrate (no-op, no migrations) → full suite → verify on real MySQL. Note explicitly: this publishes the design docs; the plan is NOT yet implemented (implementation is future work, out of scope here).
3. **Stray-file triage (advisory)** — a short per-file recommendation for MAIN's ~10 dirty files (keep+commit / move / gitignore / delete), flagged as a SEPARATE housekeeping step, not part of this merge. No mutations performed.

## Constraints
- **READ-ONLY review.** Do NOT commit, stage, merge, rebase, or modify anything in the MAIN checkout — it is the live served environment.
- The actual merge is a **separate orchestrator action** following the merge protocol — NOT part of this review deliverable.

## Method
- `git log --oneline wip/reddit-scraper-refactor..authors-location-optimization-plan`; `git show --stat <commit>`.
- `git merge-tree --write-tree wip/reddit-scraper-refactor authors-location-optimization-plan` to confirm clean apply.
- `git -C <MAIN> status --porcelain=v2 -b`; `git diff --stat` / `--staged --stat` to characterize the dirty tree.

## Acceptance criteria
- Report confirms branch = design-docs-only + clean merge (or flags any change from this snapshot).
- Exact, runnable merge steps handed to the orchestrator.
- Advisory triage list for the ~10 stray files, marked separate from the merge.
- Zero mutations to MAIN or any branch.

## Refinement decisions (resolved 2026-07-04)
- **Merge now:** merge the design docs as-is now — ready, low-risk (operator, Q "Merge design-only branch?"). Plan implementation is future work, not part of this merge.
- **Scope:** #238 stays scoped to `authors-location-optimization-plan` only (operator, Q "Campaign scope"). Orchestrator spins sibling merge-readiness briefs for the remaining branches (wt4/daisyui-removal-audit, wt1/reddit-location-ner, wip/media-consolidation, wt2, wt3).

Recent/key trace events:
[4] status_change lounge-refine: (no body)
[5] refinement lounge-refine: Refine daemon gathered live ground truth (2026-07-04). Decisive finding: **`authors-location-optimization-plan` is a design-docs-only branch.**

- The single commit ahead of deploy (`3fc73eae`) is **pure documentation** — 9 files, +4586/-0, all under `docs/authors-optimization/` (README + 00-PRODUCTION-FACTS, 10-perf-and-indexing, 20-proximity-search, 30-location-quality, 40-favorites-filter, 50-favorite-locations-and-settings, 60-frontend-ux-spec, 70-ux-review-notes). **No code, no migrations, no tests.**
- **`git merge-tree wip/reddit-scraper-refactor authors-location-optimization-plan` → no conflicts.** Committed content applies cleanly; additive docs in a new directory → zero runtime risk to merge.
- The ~10 "dirty" files in MAIN are **unrelated stray artifacts, NOT implementation of the plan**: only `BACKLOG.md` is a tracked mod (+6); the rest are untracked strays — `.codex-security/`, `.env.bak.conductor-api`, `.phpactor.json` (tooling/agent artifacts), `CACHE_NO_TTL_AUDIT.md`, `REDDIT_USER_UPDATE_QUOTAS_AND_SUBSCRIPTIONS_PLAN.md`, and 4 stray `docs/*.md` planning notes. Nothing staged. These do NOT gate the branch merge (it carries only the 1 docs commit) but should be triaged separately to clean MAIN's tree.
- Stashes (`stash@{0}` wt1, `stash@{1}` wt2) belong to other worktrees — irrelevant here.

**Implication:** merge-readiness of the *committed* work = READY (docs-only, clean). The real decision is product-level — merge the design docs now vs hold until the plan is implemented in code. Surfacing both that and campaign scope as questions.
[6] agent_question lounge-refine: authors-location-optimization-plan turns out to be DESIGN DOCS ONLY — its one commit is 9 markdown files (4586 lines) under docs/authors-optimization/, with no code, migrations, or tests, and it merges into wip/reddit-scraper-refactor with zero conflicts (additive docs, no runtime risk). Merging it just publishes the design to the deploy branch. How do you want to handle it?
[7] agent_question lounge-refine: This is the first brief of the post-#225 merge-readiness campaign. Keep #238 scoped to authors-location-optimization-plan only (orchestrator spins sibling briefs for wt4/daisyui-removal-audit, wt1/reddit-location-ner, wip/media-consolidation, wt2, wt3), or expand #238 into a full per-branch merge-readiness sweep across all remaining worktrees now?
[8] plan_proposed lounge-refine: # Merge-readiness review: `authors-location-optimization-plan` → deploy branch

## Goal
Determine whether the `authors-location-optimization-plan` branch is ready to merge into the deploy branch `wip/reddit-scraper-refactor`, with a clear verdict + exact path. First brief in the post-#225 merge-readiness campaign.

## Ground truth (refine daemon, 2026-07-04 — re-verify at run time)
- **Design-docs-only branch.** Single commit ahead of deploy (`3fc73eae`) is pure documentation: 9 files, +4586/-0, all under `docs/authors-optimization/` (README + 00-PRODUCTION-FACTS, 10-perf-and-indexing, 20-proximity-search, 30-location-quality, 40-favorites-filter, 50-favorite-locations-and-settings, 60-frontend-ux-spec, 70-ux-review-notes). No code, migrations, or tests.
- **Merges clean.** `git merge-tree wip/reddit-scraper-refactor authors-location-optimization-plan` → no conflicts. Additive docs in a new dir → zero runtime risk.
- **MAIN's ~10 dirty files are unrelated strays**, not implementation of the plan: `BACKLOG.md` (+6, tracked mod) + untracked `.codex-security/`, `.env.bak.conductor-api`, `.phpactor.json`, `CACHE_NO_TTL_AUDIT.md`, `REDDIT_USER_UPDATE_QUOTAS_AND_SUBSCRIPTIONS_PLAN.md`, `docs/{media-pdq-implementation-todo,reddit-media-dedupe-migration-spec,subreddit-r4r-index-followup,subscription-plan-admin-followup}.md`. Nothing staged. These do NOT gate the merge (it carries only the 1 docs commit) but should be triaged to clean MAIN's tree.

## Deliverable
A concise merge-readiness report:
1. **Confirm characterization** — re-verify branch is design-docs-only, merges clean, no code/migrations/tests.
2. **Verdict + exact path** — READY to merge (documentation, zero runtime risk) with the exact merge steps the orchestrator should run (merge protocol: clean tree → merge → migrate [no-op here] → full suite → verify on real MySQL). Explicitly note: because it's design-only, "merge" = publishing the design docs to deploy; the plan is NOT yet implemented in code.
3. **Stray-file triage (advisory, default ON)** — a short per-file recommendation for MAIN's ~10 dirty files (keep+commit / move / gitignore / delete), flagged as a SEPARATE housekeeping step, not part of this merge. No mutations performed.

## Constraints
- **READ-ONLY.** Do NOT commit, stage, merge, rebase, or modify anything in the MAIN checkout — it is the live served environment.
- The actual merge, if green-lit, is a **separate orchestrator action** following the merge protocol — NOT part of this review.

## Method
- `git log --oneline wip/reddit-scraper-refactor..authors-location-optimization-plan`; `git show --stat <commit>`.
- `git merge-tree --write-tree wip/reddit-scraper-refactor authors-location-optimization-plan` to confirm clean apply.
- `git -C <MAIN> status --porcelain=v2 -b`; `git diff --stat` / `--staged --stat` to characterize the dirty tree.

## Acceptance criteria
- Report confirms branch = design-docs-only + clean merge (or flags any change from this snapshot).
- Clear READY / NOT-READY verdict with exact merge steps.
- Advisory triage list for the ~10 stray files, marked separate from the merge.
- Zero mutations to MAIN or any branch.

## Open questions (fold answers before planned — see brief questions)
1. **Merge-now vs implement-first** — default: merge the design docs as-is now (ready, low-risk). Alt: hold until the plan is implemented in code.
2. **Campaign scope** — default: keep #238 to this branch only (orchestrator spins sibling briefs for wt4/wt1/media-consolidation/wt2/wt3). Alt: expand into a full per-branch sweep now.
[9] participant_joined operator:mike: (no body)
[10] operator_answer operator:mike: {"choice":"Merge the design docs as-is now — ready and low-risk (recommended)"}
[11] operator_answer operator:mike: {"choice":"Keep #238 to this branch only; sibling briefs for the rest (recommended)"}
[12] note_added operator:mike: Please issue a follow up brief to explore the docs that are coming along with authors-location-optimization-plan to see what it's even doing/about and if we should build a brief to address/build out what it describes in a worktree
[13] spec_snapshot lounge-refine: # Merge-readiness review: `authors-location-optimization-plan` → deploy branch

## Goal
Determine whether the `authors-location-optimization-plan` branch is ready to merge into the deploy branch `wip/reddit-scraper-refactor`, with a clear verdict + exact path. First brief in the post-#225 merge-readiness campaign.

## Ground truth (refine daemon, 2026-07-04 — re-verify at run time)
- **Design-docs-only branch.** Single commit ahead of deploy (`3fc73eae`) is pure documentation: 9 files, +4586/-0, all under `docs/authors-optimization/` (README + 00-PRODUCTION-FACTS, 10-perf-and-indexing, 20-proximity-search, 30-location-quality, 40-favorites-filter, 50-favorite-locations-and-settings, 60-frontend-ux-spec, 70-ux-review-notes). No code, migrations, or tests.
- **Merges clean.** `git merge-tree wip/reddit-scraper-refactor authors-location-optimization-plan` → no conflicts. Additive docs in a new dir → zero runtime risk.
- **MAIN's ~10 dirty files are unrelated strays**, not implementation of the plan: `BACKLOG.md` (+6, tracked mod) + untracked `.codex-security/`, `.env.bak.conductor-api`, `.phpactor.json`, `CACHE_NO_TTL_AUDIT.md`, `REDDIT_USER_UPDATE_QUOTAS_AND_SUBSCRIPTIONS_PLAN.md`, `docs/{media-pdq-implementation-todo,reddit-media-dedupe-migration-spec,subreddit-r4r-index-followup,subscription-plan-admin-followup}.md`. Nothing staged. These do NOT gate the merge (it carries only the 1 docs commit) but should be triaged to clean MAIN's tree.

## Deliverable
A concise merge-readiness report:
1. **Confirm characterization** — re-verify branch is design-docs-only, merges clean, no code/migrations/tests.
2. **Verdict + exact path** — READY to merge (documentation, zero runtime risk) with the exact merge steps the orchestrator should run (merge protocol: clean tree → merge → migrate [no-op here] → full suite → verify on real MySQL). Explicitly note: because it's design-only, "merge" = publishing the design docs to deploy; the plan is NOT yet implemented in code.
3. **Stray-file triage (advisory, default ON)** — a short per-file recommendation for MAIN's ~10 dirty files (keep+commit / move / gitignore / delete), flagged as a SEPARATE housekeeping step, not part of this merge. No mutations performed.

## Constraints
- **READ-ONLY.** Do NOT commit, stage, merge, rebase, or modify anything in the MAIN checkout — it is the live served environment.
- The actual merge, if green-lit, is a **separate orchestrator action** following the merge protocol — NOT part of this review.

## Method
- `git log --oneline wip/reddit-scraper-refactor..authors-location-optimization-plan`; `git show --stat <commit>`.
- `git merge-tree --write-tree wip/reddit-scraper-refactor authors-location-optimization-plan` to confirm clean apply.
- `git -C <MAIN> status --porcelain=v2 -b`; `git diff --stat` / `--staged --stat` to characterize the dirty tree.

## Acceptance criteria
- Report confirms branch = design-docs-only + clean merge (or flags any change from this snapshot).
- Clear READY / NOT-READY verdict with exact merge steps.
- Advisory triage list for the ~10 stray files, marked separate from the merge.
- Zero mutations to MAIN or any branch.

## Open questions (fold answers before planned — see brief questions)
1. **Merge-now vs implement-first** — default: merge the design docs as-is now (ready, low-risk). Alt: hold until the plan is implemented in code.
2. **Campaign scope** — default: keep #238 to this branch only (orchestrator spins sibling briefs for wt4/wt1/media-consolidation/wt2/wt3). Alt: expand into a full per-branch sweep now.
[14] refinement lounge-refine: # Merge-readiness review: `authors-location-optimization-plan` → deploy branch

## Goal
Confirm and document the merge of the `authors-location-optimization-plan` branch into the deploy branch `wip/reddit-scraper-refactor`, and give the orchestrator the exact merge steps. **Operator has green-lit merging the design docs now** (see resolved decisions). First brief in the post-#225 merge-readiness campaign; scoped to this branch only.

## Ground truth (refine daemon, 2026-07-04 — re-verify at run time)
- **Design-docs-only branch.** Single commit ahead of deploy (`3fc73eae`) is pure documentation: 9 files, +4586/-0, all under `docs/authors-optimization/` (README + 00-PRODUCTION-FACTS, 10-perf-and-indexing, 20-proximity-search, 30-location-quality, 40-favorites-filter, 50-favorite-locations-and-settings, 60-frontend-ux-spec, 70-ux-review-notes). No code, migrations, or tests.
- **Merges clean.** `git merge-tree wip/reddit-scraper-refactor authors-location-optimization-plan` → no conflicts. Additive docs in a new dir → zero runtime risk.
- **MAIN's ~10 dirty files are unrelated strays**, not implementation of the plan: `BACKLOG.md` (+6, tracked mod) + untracked `.codex-security/`, `.env.bak.conductor-api`, `.phpactor.json`, `CACHE_NO_TTL_AUDIT.md`, `REDDIT_USER_UPDATE_QUOTAS_AND_SUBSCRIPTIONS_PLAN.md`, `docs/{media-pdq-implementation-todo,reddit-media-dedupe-migration-spec,subreddit-r4r-index-followup,subscription-plan-admin-followup}.md`. Nothing staged. These do NOT gate the merge (it carries only the 1 docs commit) but should be triaged to clean MAIN's tree.

## Deliverable
A concise merge-readiness report (the merge decision is already made — this documents/confirms and hands the orchestrator an executable path):
1. **Confirm characterization** — re-verify branch is still design-docs-only, merges clean, no code/migrations/tests (flag any drift from this snapshot).
2. **Exact merge path** — the precise steps the orchestrator runs per the merge protocol: get a clean working tree → merge `authors-location-optimization-plan` into `wip/reddit-scraper-refactor` → migrate (no-op, no migrations) → full suite → verify on real MySQL. Note explicitly: this publishes the design docs; the plan is NOT yet implemented (implementation is future work, out of scope here).
3. **Stray-file triage (advisory)** — a short per-file recommendation for MAIN's ~10 dirty files (keep+commit / move / gitignore / delete), flagged as a SEPARATE housekeeping step, not part of this merge. No mutations performed.

## Constraints
- **READ-ONLY review.** Do NOT commit, stage, merge, rebase, or modify anything in the MAIN checkout — it is the live served environment.
- The actual merge is a **separate orchestrator action** following the merge protocol — NOT part of this review deliverable.

## Method
- `git log --oneline wip/reddit-scraper-refactor..authors-location-optimization-plan`; `git show --stat <commit>`.
- `git merge-tree --write-tree wip/reddit-scraper-refactor authors-location-optimization-plan` to confirm clean apply.
- `git -C <MAIN> status --porcelain=v2 -b`; `git diff --stat` / `--staged --stat` to characterize the dirty tree.

## Acceptance criteria
- Report confirms branch = design-docs-only + clean merge (or flags any change from this snapshot).
- Exact, runnable merge steps handed to the orchestrator.
- Advisory triage list for the ~10 stray files, marked separate from the merge.
- Zero mutations to MAIN or any branch.

## Refinement decisions (resolved 2026-07-04)
- **Merge now:** merge the design docs as-is now — ready, low-risk (operator, Q "Merge design-only branch?"). Plan implementation is future work, not part of this merge.
- **Scope:** #238 stays scoped to `authors-location-optimization-plan` only (operator, Q "Campaign scope"). Orchestrator spins sibling merge-readiness briefs for the remaining branches (wt4/daisyui-removal-audit, wt1/reddit-location-ner, wip/media-consolidation, wt2, wt3).
[15] status_change lounge-refine: (no body)

Recommended linked context:
{
    "todos": [],
    "scratchpads": []
}

Execution notes:
- Treat the brief as the source of truth.
- Keep work scoped to this dispatch request.
- Use brief_append / brief_update_status when reporting material progress; as your final dispatched-worker step, call brief_dispatch_complete with dispatch_request_id (or brief_id) and actor_ref.
- Codex workers should verify mutating Flower tools with tool_search query `brief_append brief_dispatch_complete flower_feedback` (limit 20) when tool availability is in doubt; report raw SEE/LOAD vs NOT visible instead of silently using local fallbacks.
- Add a git commit trailer `Brief: #238` to every commit for this brief so flower can exact-link commits back to the brief.