Repository source: docs/plans/zenmemes_meta_feedback_2026-10-21_mini_triage.md
October 21 feedback: mini-triage
Historical triage snapshot: use the production feedback register for current status, next actions and evidence reconciliation. The rows and recommendation below preserve the original assessment; they are not a second current-status list.
Checklist · parent post · full thread.
F = feature request; B = bug. Each report is linked below. Scores preserve the checklist’s feedback-only estimates, not new calibrated forecasts; F02 also has a source-informed 0.10 estimate. Workflows reflect brief local source review, not new runtime or production checks. F02 and B03 are already implemented locally. Other completion checks are proposed, not verified.
One-shot means a bounded direct fix with required verification. Railspike means uncertainty, design choices, or dependencies warrant staged planning and approvals. This triage starts no implementation and does not resume paused reply work. If a one-shot uncovers broader behavior changes, reassess before expanding it.
| Item / report | Score | Workflow | Why / source | Done when |
|---|---|---|---|---|
| F01: Reply focus · reply-20261021175726-73beca3d | 0.15 | Railspike | Reply submission navigates to the canonical reply; focus and phone-keyboard behavior overlap paused reply work. Source (source unavailable). | Post once, retain usable reply focus; failure/retry preserves text and sends no duplicate. |
| F02: Identity-ready notice · reply-20261021175826-902c5145 | 0.03 | One-shot | Completed shared status cleanup; no new interface needed. Source (source unavailable). | No ready notice or empty gap; pending/error and Account results remain useful. |
| F03: Text-entry macros · reply-20261021180225-ffc44b89 | 0.5 | Railspike | Insertion rules, selection handling, and intended entry points are undefined. Source (source unavailable). | Agree a small macro set; insertion preserves surrounding text, selection, and undo. |
| F04: Simple recent activity · reply-20261021180354-1a31022c | 0.5 | Railspike | Existing Activity exposes record kinds and source metadata; choose audience and useful events before redesign. Source (source unavailable). | Ordinary readers can find recent content and open it without technical detail. |
| F05: QR appearance · reply-20261021180542-57b8fc3f | 0.25 | One-shot | Invitation QR currently draws black on white; first confirm the reported QR surface, then bound the visual change. Source (source unavailable). | QR stands out across themes and phone/desktop; quiet zone and scanning still work. |
| F06: LCD color choices · reply-20261021181124-47b0956c | 0.4 | Railspike | LCD has a fixed palette; choose palette scope and preference behavior before adding controls. Source (source unavailable). | Chosen palettes remain readable; selection persists and existing themes work. |
| F07: Default port fallback · reply-20261021180905-9bf88f1f | 0.2 | One-shot | Startup selects one address; bounded retries can preserve explicit-address behavior. Source (source unavailable). | Occupied default ports advance within a fixed range; actual URL, exhaustion, and shutdown behave correctly. |
| F08: View query coverage · reply-20261021181111-3d37d8d5 | 0.6 | Railspike | Broad audit across database-backed pages; stage the inventory and bounded additions. Source (source unavailable). | Coverage and exclusions are documented; each added control opens the correct read-only query. |
| F09: Compact query buttons · reply-20261021181111-3d37d8d5 | 0.15 | One-shot | Shared query partial already supports compact buttons; reuse it on agreed surfaces. Source (source unavailable). | Consistent square buttons retain accessible names and open the correct query across affected themes. |
| F10: Query-dialog improvements · reply-20261021181111-3d37d8d5 | 0.75 | Railspike | The report does not identify specific dialog failures; reproduce before choosing changes. Source (source unavailable). | Record reproduced problems and verify their fixes, including keyboard, phone layout, and recovery. |
| F11: Easy-op discovery · reply-20261021181246-675f949e | 0.25 | Railspike | An Account approval button and .test-self-approval exist, but their equivalence to “easy-op” is unconfirmed. Source (source unavailable). | Identify the intended flag; expose one useful discovery path while preserving approval restrictions. |
| B01: Composer jumping · reply-20261021175826-902c5145 | 0.75 | Railspike | Several causes are reported; existing focus and expansion paths need a reproducible root-cause review. Source (source unavailable). | Reproduce each jump and verify corrected geometry through loading, focus, drafts, and recovery. |
| B02: Textarea edge alignment · reply-20261021175826-902c5145 | 0.25 | One-shot | Compact and expanded states use different CSS geometry; start with measured board-composer bounds. Source (source unavailable). | Top/left/right edges stay fixed during expansion across phone/desktop themes; other content does not overflow. |
| B03: Saved draft starts collapsed · reply-20261021180138-eddd96a4 | 0.15 | One-shot | Completed bounded state change; draft text no longer implies initial engagement. Source (source unavailable). | Restored draft stays compact until focus, preserving text, selection, warnings, and retry. |
| B04: Slow reply feedback · reply-20261021175854-431cbb06 | 1.5 | Railspike | Reply preparation, signing, finalization, and navigation are separate stages; the live bottleneck is unknown. Source (source unavailable). | Measure the delay, improve the identified stage, and verify prompt feedback plus one accepted reply and retry. |
| B05: QDB temporarily busy · reply-20261021180434-90201f38 | 0.75 | Railspike | FrontController has several 503 paths; the reported production cause has not been reproduced. Source (source unavailable). | Identify the failing route and cause; verify ordinary QDB use and controlled recovery without hiding errors. |
Best independent next pick: F07, default port fallback. F09 is another bounded cleanup. F01 should be reconciled with the paused reply workflow; F08/F09/F10 overlap and should share an inventory. Prioritize B05 sooner if QDB is currently unavailable, after confirming its live status.