Skip to content

refactor(planning): move the interview server's settings file onto ADR 0075 #12754

Description

@kyle-sexton

Parent

Refs #12646 (follow-up, not a slice: no acceptance criterion of the epic covers it).

Depends on

  • none: on the frontier now

Outcome

The 1:1 interview page's server reads its settings through the ADR 0075 scopes (plugin default, userConfig, docs/conventions/planning.yaml, its .local override) instead of its own .claude/interview-surface.json chain, with a one-time notice for an existing file.

Demo: with only a docs/conventions/planning.yaml setting, the interview page applies it; an old .claude/interview-surface.json produces a notice and is not read.

Decisions

  • D5: The interview server's own settings file moves to ADR 0075 in a separate issue; resolveSurface reads today's sources unchanged.
  • Q14: medium moves onto ADR 0075 scopes; ~/.claude/rendered-views.md is no longer read.

Key interfaces

ADR 0075 (config cascade); the shared config-cascade module.

Done when

  • The interview server no longer reads .claude/interview-surface.json for values; a test covers the notice.
  • The planning plugin's tests pass.

Out of scope

  • The rendered-views medium setting (epic slices)

Activity

  1. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
  2. added theissue type on Nov 3, 2026
  3. melodic-automation-lanes commented on Nov 3, 2026

    @melodic-automation-lanes
    Contributor

    The work-resolve-issue run that agent-ready started failed or was cancelled before it reported, or it stopped or the token broker refused it because its workflow files differ from main's. work-unblock removed and added agent-ready back to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.

  4. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
  5. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  6. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  7. removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions