ID: PF-20261103-F01
Title: Retitle thread by reply; visible likes and flags
Kind: feature
Workflow: blocked
Created: 2026-11-03
Evidence: locally-verified
Estimate: 0.80

Request:
Comment `title: some text here` and, with authority, change the thread's title; roll it into the same visibility layer as likes and flags, which should be visible and currently are not really.

Sources:
- https://zenmemes.com/threads/thread-20261103051304-2fa9fbd6

Done when:
An authorized reply with a `title:` line changes the thread title everywhere it is shown; an unauthorized one posts unchanged with no effect; readers see likes, flags and title changes on the thread without being signed in.

Notes:
Register status at migration: none (direct intake 2026-11-03, outside the October 21 batch); workflow state: blocked — Steps 1–3 approved and all eight stages implemented on `feat/reply-title-directive` (Step 4 summary (docs/plans/reply_title_directive/reply_title_directive_step4_implementation_summary.md)); awaiting merge, deployment and the production retry; delivery evidence: locally verified 2026-11-03 (PHP suites, Chromium replay of the maintainer's flow, 16-theme signals check), deployment and production acceptance pending.
Existing `records/thread-subjects/` family is system-only and fills empty subjects only; reaction counts exist in the read model but are not rendered on cards. Write path (src/ForumRewrite/Write/LocalWriteService.php) · Root card (templates/partials/thread_root_card.php).
Next action: Verify deployment of the merged reply-title code and perform the production retry; the maintainer replies `title: …` on an own zenmemes.com thread with flags at defaults and confirms the new title on the thread, board and Recent plus `Title set by ilyag` on the root card. Both flags are on the Feature Flags page (Forum experience). Follow-ups: suggested titles from unauthorized repliers; static tag pages are not invalidated on retitle (same as label writes today).
Estimate 0.80 is the source-informed Step 1 projection for Option B (docs/plans/effort_estimation_trial.md#cycle-v3reply_title_directive); there is no inherited feedback estimate. Recommended workflow: staged Railspike.
Implementation: docs/plans/reply_title_directive/reply_title_directive_step4_implementation_summary.md
History: docs/plans/production_feedback_register.md#pf-20261103-f01
2026-11-04 catch-up: merge and push are recorded in the implementation summary, with merged-tree checks. Remove merge from the outstanding next action. Deployment and the maintainer's production retry remain unverified; retain blocked and locally-verified. Continue with deploy/production verification only within existing authorization. Commit: 48ab2906 (merged-tree verification); plan records merge 699ebd26. Evidence: docs/plans/reply_title_directive/reply_title_directive_step4_implementation_summary.md#merge-verification--2026-11-03t193724z. Proposal: docs/feedback/triage/2026-11-04_proposals.txt