Skip to content

S1a (rev-3 amendment): build returns to the picker — plan · build · develop · research #868

Closed

Description

@aarontrowbridge

Important

Problem — S1 (#862) removed build from the picker per the spec's original D1 ('auto implied'). Real usage (2026-09-07, Aaron): build is the plain-work mode — authoring proposal decks, one-off fixes — distinct from develop's campaign machinery. Removing it was wrong; it's used daily.
Approach — The spec amendment (spec-20260907-011500 rev 3, D1 revised): the picker lists plan · build · develop · research in that order; build is a named, selectable tile AND remains the default posture (marked default, not implied-absent). develop/research stay the campaign postures; the plan-exit recommendation (S2, landed #864) never targets build — build is the resting state, not a recommendation target. No auto-router mode.

Acceptance Criteria

  • The agent_order default becomes ["plan","build","develop","research"] (the S1 landed config changes)
  • build renders as a named tile with the default marker (replacing the implied-absent marker; i18n keys updated ×18)
  • The S1 tests updated (the implied-marker tests become default-marker tests; the alias/rename tests unchanged)
  • The drift gate passes (overlay manifest hashes for whatever the marker/i18n edit touches)

Small slice — the S1 machinery (agent_order config, app-side sort, resolveModeId) is all landed; this amends its defaults.

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

    afkImplementable without human interaction

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions