Skip to content

planning: interview page shows a pending terminal permission prompt (UX-3) and decides Enter on Save buttons (UI-14) #12365

Closed
1 of 1 issue completed

Description

@kyle-sexton

Refs: #7303

Summary

These two items remain from the interview web view review in #7303. Every other slice of that review has shipped.

  1. UX-3: the page cannot tell when the terminal is waiting on a permission prompt. Since fix(planning): interview page answer controls, withheld questions, and apply idempotence #7280, the page tells the user to approve any prompt in the terminal while no watcher has polled yet (listener.idleFor === null). A real fix needs the watcher or the session to report a pending prompt to the page. This stays parked under the 2026-10-12 decision until that capability exists. Keep the fix(planning): interview page answer controls, withheld questions, and apply idempotence #7280 hint until then.
  2. UI-14: plain Enter does nothing on Save-type buttons. This is deliberate, for dictation. It was decided on 2026-10-12: "Keep plain Enter as a no-op on Save-type buttons (UI-14)? → Keep it" (decision). Only the record is missing.

Done when

Related

Activity

  1. added
    priority: lowNice-to-have, cosmetic, or speculative; opportunistic.
    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.
    status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.
    on Nov 2, 2026
  2. github-actions commented on Nov 2, 2026

    @github-actions
    Contributor

    Proposed work class: work-class: scoped
    Basis: automated intake triage; the lanes App applied this class.

    Size: Small
    Complexity: Low
    Uncertainty: Knowable
    Flags: intent
    Blocked by: none

    I understand two leftovers from #7303. UX-3 stays parked until the watcher or session can report a pending permission prompt, and the #7280 hint stays. UI-14 needs a keep-or-change decision on plain Enter for Save-type buttons, which is deliberate for dictation.

    Open question:

    1. Should plain Enter on Save-type buttons stay a no-op (keep) or submit (change)? RECOMMENDED: keep, and record it in plugins/planning/surface/deferred.md. The behavior is deliberate for dictation, and the issue gives no reason to reverse it.

    To answer, post a comment that starts with this line:

    **Decision recorded.** UI-14: keep
    

    Automated triage, applied by the lanes App.

  3. added
    status: needs-decisionAwaiting a human or maintainer judgment call.
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 2, 2026
  4. melodic-automation-lanes commented on Nov 2, 2026

    @melodic-automation-lanes
    Contributor

    The triage verdict left this issue at status: needs-decision:

    • flagged: intent
    • held by status: needs-decision
    • no lanes App verdict comment shows whether an earlier verdict was flagged
  5. removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.
    on Nov 2, 2026
  6. melodic-automation-lanes commented on Nov 2, 2026

    @melodic-automation-lanes
    Contributor

    Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.

    Intended outcome: UI-14 is decided as keep, recorded in plugins/planning/surface/deferred.md, and UX-3 stays parked with the #​7280 hint unchanged.

    Related work

    Open questions

    1. Should plain Enter on Save-type buttons stay a no-op (keep) or submit (change)? The owner has not recorded a decision.
      RECOMMENDED: keep, and record it in plugins/planning/surface/deferred.md Basis: judgment: the issue calls the behavior deliberate for dictation and gives no reason to reverse it; the page tests use Ctrl+Enter to save (plugins/planning/surface/tests/ui_c.js:172)
    2. Is the UX-3 item to be dropped from this issue's done-when, since it cannot be completed until the watcher or session can report a pending prompt?
      RECOMMENDED: yes, leave UX-3 parked in deferred.md and track it separately once that capability exists Basis: judgment: the issue says UX-3 stays parked under the 2026-10-12 decision, so an unattended run cannot finish or check it

    Sources read

    • /home/runner/work/claude-code-plugins/claude-code-plugins/refine-data/context.json: the issue has no recorded owner decision and comments is empty
    • plugins/planning/surface/tests/ui_c.js:172: existing page tests save with Control+Enter
    • plugins/planning/surface/deferred.md: exists; a grep of plugins/planning found no UI-14 or UX-3 entry

    To answer, post a comment that starts with this line:

    **Decision recorded.** <answer>
    

    Automated refinement by the lanes App. Answer with a comment whose first line is **Decision recorded.**.

  7. added
    status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.
    and removed
    status: needs-decisionAwaiting a human or maintainer judgment call.
    on Nov 2, 2026
  8. kyle-sexton commented on Nov 2, 2026

    @kyle-sexton
    MemberAuthor

    Label note: status: needs-decision changes to status: confirmed. Neither item has a decision left open.

    • UI-14 was decided on 2026-10-12: "Keep plain Enter as a no-op on Save-type buttons (UI-14)? → Keep it" (#7303 comment). That comment is a session-written decision record posted from the kyle-sexton account. It says "The owner approved applying independently verified recommendations on 2026-10-12", and its own verification note says "UI-14 'keep it' rests on judgment about dictation". The answer is a verified recommendation applied under that approval, not the owner's own wording on UI-14. What remains is the record this issue's done-when names: the decision written into plugins/planning/surface/deferred.md, citing that comment. No UI-14 entry is in that folder on main yet.
    • UX-3 is parked, not undecided. This issue says: "A real fix needs the watcher or the session to report a pending prompt to the page. This stays parked under the 2026-10-12 decision until that capability exists. Keep the fix(planning): interview page answer controls, withheld questions, and apply idempotence #7280 hint until then." That capability does not exist yet.

    The intake triage comment and the refinement comment both ask whether to keep or change UI-14; the 2026-10-12 record already answered that. The refinement also asks whether to drop UX-3 from the done-when. This issue's done-when already keeps UX-3 as a parked line ("Until then, this item stays parked and the #7280 hint stays"), so it stays as written. This issue does not wait on a decision.

    Posted by the issue-triage session. This was generated by AI.

  9. self-assigned this
    on Nov 3, 2026
  10. kyle-sexton commented on Nov 3, 2026

    @kyle-sexton
    MemberAuthor
    No description provided.
  11. added a commit that references this issue on Nov 3, 2026
  12. kyle-sexton commented on Nov 4, 2026

    @kyle-sexton
    MemberAuthor

    Delivered: closing as completed.
    Agent choice, not an owner answer.

    Checked against origin/main (8f87fee):

    When that capability exists, the deferred.md:37 row is the entry to pick it up from.

  13. kyle-sexton commented on Nov 4, 2026

    @kyle-sexton
    MemberAuthor

    Closing as completed on the delivery record above: UI-14 is recorded by #12769, and the UX-3 park is recorded in deferred.md with the #7280 hint kept.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

priority: lowNice-to-have, cosmetic, or speculative; opportunistic.status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

Type

Fields

Work status

needs-owner-decision

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions