Decisions render: spaced standing answers, and an answered question keeps every option

Before (main) and after (this branch) for the open question, the answered question with a typed note, and a multi-question set.

8 Oct 2026 · branch decisions-render-spacing-answered · captured against propflow-stage · at 6bc3c3b9312+local

Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.

1 · BEFORE (main): an open question, the two standing answers flush under a hairline

Gera: "the buttons are too close to each other … and then there's a horizontal line for some reason." The two bottom cards touch, and a rule sits above them.

Asserted in the captured DOM — I'm not sure — go find out · Take it to the engineering bridge

BEFORE (main): an open question, the two standing answers flush under a hairline
⚠ Provenance. Captured from commit 16522495f81, read from the worktree the server was started from (/Users/miniclaw/code/PropFlow/propflowai-worktrees/decisions-before-main) — the server could not report its own commit, so this is the weaker of the two sources. ⚠ That is the current tip of origin/main. If this section is labelled a BEFORE, it is not one — it is showing today's main, which already carries the change.
Sections 2–6 and notes

2 · AFTER: the same question, the standing answers spaced like the real ones

The standing answers stack with the same gap as the question's own options and are set apart by a quiet OR instead of a border. Still one radiogroup, one tab stop.

Asserted in the captured DOM — OR · I'm not sure — go find out · Take it to the engineering bridge

AFTER: the same question, the standing answers spaced like the real ones

3 · BEFORE (main): an answered single question with a typed note

The record is a Question / Answer card. The options that were not picked are gone, so a teammate reading the link cannot see what was turned down.

Asserted in the captured DOM — RECORDED ANSWER · yes merge it.

BEFORE (main): an answered single question with a typed note
⚠ Provenance. Captured from commit 16522495f81, read from the worktree the server was started from (/Users/miniclaw/code/PropFlow/propflowai-worktrees/decisions-before-main) — the server could not report its own commit, so this is the weaker of the two sources. ⚠ That is the current tip of origin/main. If this section is labelled a BEFORE, it is not one — it is showing today's main, which already carries the change.

4 · AFTER: every option, the chosen one marked, the typed words beneath

Gera: "you would be able to see the other options and then what you selected and typed." The same read-only list the multi-question stepper has used since #7375: the pick keeps its filled state and a CHOSEN mark, the rest dim, and the note is set beneath as a quote.

Asserted in the captured DOM — RECORDED ANSWER · CHOSEN · ADDED WITH THIS ANSWER · yes merge it.

AFTER: every option, the chosen one marked, the typed words beneath

5 · BEFORE (main): a multi-question set, answered

The stepper already listed every option; the standing answers carried the same hairline and flush stacking.

Asserted in the captured DOM — CHOSEN

BEFORE (main): a multi-question set, answered
⚠ Provenance. Captured from commit 16522495f81, read from the worktree the server was started from (/Users/miniclaw/code/PropFlow/propflowai-worktrees/decisions-before-main) — the server could not report its own commit, so this is the weaker of the two sources. ⚠ That is the current tip of origin/main. If this section is labelled a BEFORE, it is not one — it is showing today's main, which already carries the change.

6 · AFTER: the multi-question set

Same spacing fix inside the stepper; a typed note on a stepper question uses the same quote block as the single-question record.

Asserted in the captured DOM — CHOSEN · OR

AFTER: the multi-question set

Reference design

No August render of this file showed the other options on an answered question; those were a compact card with the choice only. The every-option record is #7375 (063ed205b6e, 2026-09-08), which only reached the stepper. This PR ports it to the single-question path.

PropFlow Docs