Feature plan: Step 1 · Step 2 · Step 3 · Step 4

Debug mode: enabled (inherited from Step 3) Effort study: railspike-effort / v3/compose_keyboard_fit (ledger); standing enrollment P2 Extended estimates: enabled

Cycle estimate: 0.20

Step 3 approved 2026-11-02 ("approved step 3"). Branch feat/compose-keyboard-fit from main 2a7d356f8; planning commit 6e043cb6e.

Step 4 entry checkpoint

Stage identities and original stage-work estimates copied from Step 3 (not new ratings): S1 full composer order 0.07; S2 phone body height and footprint 0.08; S3 acceptance, records and closeout 0.05. Not summed.

Pending requests

• Theme chrome overflow (Word 97, Midnight, Sticker, Arena) at 375px: separate work, pending.

• Forum reply saying the posted Railspike steps are superseded: separate, maintainer's call, pending.

— Claude · 2026-11-02 UTC · Model: claude-fable-5-1

Stage 1 - Full composer order

Original estimate: 0.07 Retrospective stage-work assessment: 0.07

• Changes:

  • templates/partials/composer.php: in full mode the Title input and its normalization status, then the tools block (tags, event), now render after .compose-form-actions; header comment updated. Field names, attributes and the submit contract are unchanged. Compact and reply modes render the same markup as before.

  • tests/browser/composers.mjs: order assertion is now body, Post row, Title, tools.

  • tests/LocalAppSmokeTest.php: /compose/thread order assertion; the paned board New Thread dialog (/forte) has body before Post before Title; the compact board form has no Title and no tools.

• Verification:

  • Partial renders through TemplateRenderer::renderFragment before and after the change: compact board, QDB add and reply (data-phone-reply) output byte-identical; full output differs only in order. Passed.

  • php tests/run.php LocalAppSmokeTest: 160 run, 157 passed. The three failures (private lobby surfaces, private forte session recovery, repository archive filename) are recorded by the runner as long-standing since 2026-10-27 and 2026-10-30 and are unrelated. Passed for this stage.

  • node tests/browser/composers.mjs: passed. compose_disclosure.mjs: passed. reply_compose_focus.mjs: passed (Chromium, four themes).

  • board_compose_focus.mjs: failed with a waitForLoadState('networkidle') timeout. Reproduced identically on the planning commit 6e043cb6e in a separate worktree, so it is pre-existing and environmental, not caused by this stage. Not chased.

  • Paned dialog order: checked through the server-rendered /forte assertion rather than a Chromium visit; the dialog includes the same partial in full mode.

• Notes:

  • Only compose.css and the partial reference .compose-title; no script locates the Title by position.

  • Engines: Chromium only. No Playwright WebKit or Firefox build is installed in this environment.

• Estimate details: original scope one partial and two test files; uncertainty low; no revisions. Retrospective matches the original.

— Claude · 2026-11-02 UTC · Model: claude-fable-5-1

Stage 2 - Phone body height and footprint

Original estimate: 0.08 Retrospective stage-work assessment: 0.10

• Changes:

  • public/assets/compose.css: under 640px the full composer's body (New post page and the paned New Thread dialog's form) is 5.5rem high, the compact form's height, with vertical resize; the reserved hidden picker footprint on the compose page is not kept on phones. Wider screens unchanged.

  • tests/browser/compose_layout_stability.mjs: a phone fit pass over the 13 permitted themes at 375 by 667, 375 by 300 and 1280 by 1000. On phones it asserts no horizontal overflow, Title below Post, body top to Post bottom within 300px, nothing reserved between body and Post, and, after focusing the body and scrolling it into view as a phone does, Post's bottom edge inside the viewport and above the tab bar when shown. At 1280 it asserts the tall body and the reserved footprint remain. New --phone-fit-only switch runs just that pass, like the existing --shared-only; PHONE_FIT_SCREENSHOT_DIR saves a screenshot per case.

• Verification:

  • node tests/browser/compose_layout_stability.mjs --phone-fit-only: 39 of 39 cases passed in Chromium. Body top to Post bottom 157 to 166px on phones, 276 to 313px on desktop.

  • Screenshots at 375 by 667 (Light, Word 97) and 375 by 300 (Light, Sticker) reviewed: body, Post row, Title, tags chip in that order; nothing runs off the right edge. Before focus at 300px tall the heading leaves Post below the fold; the focus assertion covers what a phone does next.

  • node tests/browser/composers.mjs: passed again with the new CSS.

  • git diff --check: clean.

  • The test's full mode (without the switch) fails at its first waitForLoadState('networkidle') with a 30s timeout. Reproduced identically on the planning commit in the baseline worktree, so it is pre-existing and environmental (a client script polls every two seconds), not caused by this stage. Not chased; the new pass avoids network-idle waits.

• Notes:

  • Engines: Chromium only; no Playwright WebKit or Firefox build installed here. The real-phone replay is Stage 3.

  • The paned dialog rule is harmless on desktop and only matters if the paned board is used under 640px.

• Estimate details: original scope the phone rules and a theme loop; uncertainty low for layout. Retrospective 0.10 rather than 0.08 because the pre-existing network-idle failure forced the --phone-fit-only switch and a baseline reproduction. No scope change.

— Claude · 2026-11-02 UTC · Model: claude-fable-5-1

Stage 3 - Acceptance, records and closeout

Original estimate: 0.05 Retrospective stage-work assessment: 0.05

• Changes:

  • docs/concepts/shared_composer.md: new entry (purpose, scenario, sources); all six source paths verified to exist.

  • docs/plans/ui_copy_audit_checklist.md: entry recording no copy change and the pending device check.

  • docs/plans/effort_estimation_trial.md: cycle closeout; docs/plans/README.md entry was added in the planning commit.

• Verification:

  • Full PHP suite php tests/run.php (what ./v3 test runs): 1768 run, 1760 passed, 8 failed. Six are marked long-standing by the runner (approval seed cache, two private lobby/forte surfaces, archive filename, platform docs static release, read-model builder timing). The other two (reaction record format parity, read-model schema statements) fail identically on a clean main worktree at 2a7d356f8. None touch the composer; recorded, not chased.

  • Browser tests run for this cycle, Chromium only: composers.mjs pass, compose_disclosure.mjs pass, reply_compose_focus.mjs pass, compose_layout_stability.mjs --phone-fit-only 39 of 39 pass. board_compose_focus.mjs and the full compose_layout_stability.mjs time out on networkidle on the baseline too.

  • Device replay (Step 2 known user): pending. The maintainer's iPhone SE in Firefox and Safari, keyboard open, one-line and 30-line draft, Post visible and a thread created; error path keeps the draft with Post visible. No emulator evidence is substituted for it.

• Notes:

  • Deployment is outside this cycle; nothing beyond the normal deploy is needed. No schema, API, dependency or navigation-icon change.

• Estimate details: original scope records and a suite run; uncertainty low apart from the device result. Retrospective matches the original.

Closeout and study outcome

• Delivered scope: Option A at scope v1.1. Full composer order body, Post row, Title, tags and event; phone body at the compact height with no reserved picker footprint; tests, concept entry and records. Reply and compact composers unchanged (byte-identical renders).

• Revisions: starting 2a7d356f8 on main; branch feat/compose-keyboard-fit; planning 6e043cb6e; Stage 1 439000c06; Stage 2 e27587b9f; Stage 3 is this commit. Three planned, three completed stages; no splits, no corrective work beyond the test switch noted in Stage 2.

• Dependency delta: zero.

• Omissions and limits: real-phone acceptance pending; Chromium only (no WebKit or Firefox build here); an attached image preview still sits between body and Post (accepted in Step 2); theme chrome overflow and keyboard docking remain separate requests.

• Effort study: 0.20 original projection, reaffirmed at every checkpoint; 0.20 retrospective scope assessment (separately judged, not the stage sum). Stage-work originals 0.07 / 0.08 / 0.05, retrospectives 0.07 / 0.10 / 0.05. Claude (claude-fable-5-1), single exposed rater; no measured labor. Maintainer comfortable-fit judgment and study acceptance pending; accepted-outcome count unchanged. Merge not implied.

— Claude · 2026-11-02 UTC · Model: claude-fable-5-1

Maintainer merge acceptance — 2026-11-02

• The maintainer said "great job, please merge and push". That authorizes merging and pushing; it is not the iPhone SE device check, which stays pending.

• main (99522a996, 14 commits ahead of the cycle base) merged into the branch without conflicts. Combined-tree checks: LocalAppSmokeTest 162 run, 159 passed (the same three long-standing failures); composers.mjs passed; compose_layout_stability.mjs --phone-fit-only 39 of 39 passed. Chromium only.

• Merged to main with a merge commit and pushed to origin/main.

— Claude · 2026-11-02 UTC · Model: claude-fable-5-1