Repository navigation
Closed
Copy link
Labels
agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.status: readyTriaged, unblocked, and fully specified; eligible to pick up.Triaged, unblocked, and fully specified; eligible to pick up.
Description
Refs: #8633
Phase 4 of #8633 (design record: #8633 (comment), items K8, K14, K17 and C5). Filed for #10212.
Intended outcome
The shared interview page shows a question's basis as written, through the one markdown renderer, folded like the 1:1 page's "Why", instead of prefixing its own Basis: label to the whole field. The field already opens with Checked against: and carries its own Basis: label (plugins/planning/skills/interview/context/question-shape.md:27), so today the page reads Basis: Checked against: ....
State on main (a6ab693)
- Done: one safe DOM markdown renderer in
plugins/planning/shared/web/question-shape.js(union dialect), and the page-localmd/inlineandrich/inline/linksremoved: feat(planning): render both interview pages' markdown through one renderer in question-shape.js #10924, closing feat\(planning\): bring the one-on-one interview page in line with the shared page - part 2 of 4 #10210. - Done: the repository for links comes from the server state (
plugins/planning/shared/web/app.js:562passesCore.state.repoandCore.state.committoQuestionShape.markdown), not a page-local regex: feat(planning): render both interview pages' markdown through one renderer in question-shape.js #10924. - Open:
plugins/planning/shared/web/app.js:5691still setsk.basis.textContent = a.basis ? \Basis: ${a.basis}` : ""`, plain text with the extra label.
Acceptance criteria
- The shared page's answer card renders
basisthroughQuestionShape.markdownwith no addedBasis:prefix. - The rendered basis is folded behind a toggle, as the 1:1 page folds it behind "Why".
- A shared browser test (
plugins/planning/shared/tests/ui_claude_proposals.jsor its successor) asserts a fixture basis openingChecked against:renders without a doubledBasis:label. - The shared Python suites and the touched shared browser suites pass.
Metadata
Metadata
Assignees
Labels
agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.status: readyTriaged, unblocked, and fully specified; eligible to pick up.Triaged, unblocked, and fully specified; eligible to pick up.
Type
Fields
No fields configured for Task.
Activity
github-actions commentedon Oct 29, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood: the shared interview page should render a question's
basisthrough the shared markdown renderer, folded behind a toggle like the 1:1 page's "Why". It should drop the extraBasis:prefix that currently producesBasis: Checked against: .... The acceptance criteria are exact, including a browser test for the doubled label. Nothing is missing, and I found no duplicate among the open issues.Automated triage, applied by the lanes App.