docs: align tui slash command specs

Author: wangtsiao

specs/L2/goal/L2-DES-GOAL-001-ralph-loop-goals.md

@@ -6,18 +6,18 @@ active_baseline: no
 supersedes:
 superseded_by:
 owner: Assistant
-last_updated: 2026-05-23
+last_updated: 2026-05-25
 ---
 
 # L2-DES-GOAL-001 — Ralph Loop Goals
 
 ## Purpose
 
-Refine the Ralph Loop goal requirement into a durable, bounded, autonomous goal loop that can be controlled by the user, observed by clients, resumed after restart, and executed by the server without polluting the visible transcript with hidden continuation prompts.
+Refine the Ralph Loop goal requirement into a durable, optionally bounded, autonomous goal loop that can be controlled by the user, observed by clients, resumed after restart, and executed by the server without polluting the visible transcript with hidden continuation prompts.
 
 ## Background / Context
 
-A normal chat turn is request-response: the user submits input, the program works, and the turn stops. A Ralph Loop goal changes that interaction model. The user sets a durable objective once, and the program continues across turns while the goal is active, verified incomplete, unpaused, and within budget.
+A normal chat turn is request-response: the user submits input, the program works, and the turn stops. A Ralph Loop goal changes that interaction model. The user sets a durable objective once, and the program continues across turns while the goal is active, verified incomplete, unpaused, and within any configured budget or stop policy.
 
 The goal feature must remain user-owned. The model may work toward the objective and report completion or blockers, but it must not silently rewrite the objective, expand the budget, or hide why the loop is continuing.
 
@@ -48,11 +48,11 @@ Historical goal records remain auditable. A new goal may replace a prior non-ter
 
 The goal loop should:
 
-- Persist the objective, status, budget, usage, progress, and blocker state.
+- Persist the objective, status, optional budget, usage, progress, and blocker state.
 - Inject hidden goal context into model invocations while the goal is active.
 - Start autonomous continuation turns only when the session is idle and policy permits.
 - Account token and time usage incrementally.
-- Stop automatically when complete, blocked, paused, canceled, or budget-limited.
+- Stop automatically when complete, blocked, paused, canceled, or limited by a configured budget or stop policy.
 - Explain to the user why work continues or why it stopped.
 
 ## State Model
@@ -103,7 +103,7 @@ canceled
 
 ## User Sovereignty
 
-The user owns objective text, explicit budget, pause/resume, cancellation, clear, and replacement.
+The user owns objective text, explicit optional budget, pause/resume, cancellation, clear, and replacement.
 
 Model-facing goal tools should be narrower than client or slash-command controls. The model may report:
 
@@ -209,6 +209,8 @@ Runtime state may be lost on restart. Recovery reconstructs durable goal state f
 
 Budget accounting should happen incrementally rather than only at turn end.
 
+The first milestone does not assign a default token, time, or turn budget when the user creates a goal through `/goal <objective>`. When no explicit budget is configured, accounting still records usage for display, recovery, and future limits, but absence of a budget must not by itself transition the goal to `budget_limited`.
+
 Accounting points:
 
 - Turn start: capture baselines.
@@ -226,7 +228,7 @@ goal_token_delta = non_cached_input_tokens + output_tokens
 
 Cached input tokens are excluded because they represent reused context rather than newly consumed context cost for the current goal. If a provider reports reasoning tokens separately, the model usage normalization layer must state whether they are already included in `output_tokens`. Goal accounting must not double-count reasoning tokens.
 
-Budget transitions should be atomic at the projection layer. A successful accounting operation should increment usage and switch `active` to `budget_limited` in one logical operation when the limit is reached.
+Budget transitions should be atomic at the projection layer. A successful accounting operation should increment usage and switch `active` to `budget_limited` in one logical operation when a configured limit is reached.
 
 ## Continuation Loop
 
@@ -277,7 +279,8 @@ Conceptual hidden context:
 <goal_context>
   <status>active</status>
   <untrusted_objective>...</untrusted_objective>
-  <budget tokens_used="12500" token_budget="50000" tokens_remaining="37500" />
+  <usage tokens_used="12500" turns_used="4" />
+  <budget configured="false" />
   <progress>...</progress>
   <instructions>
     Continue working toward the active session goal.
@@ -291,6 +294,7 @@ Rules:
 
 - User-provided objective text must be XML-escaped.
 - User-provided objective text should be placed inside an explicitly untrusted tag such as `untrusted_objective`.
+- If no budget is configured, hidden goal context should state that no explicit budget is configured or omit limit fields; it must not fabricate a default budget.
 - Hidden goal context must not render as an ordinary transcript turn.
 - The context snapshot must be auditable through JSONL records or context snapshot references.
 - The hidden context may be serialized with provider-specific roles during request construction, but that serialization does not make it a transcript item.
@@ -361,8 +365,8 @@ The `/goal` slash command is the primary TUI entry point for goal control.
 
 The TUI should support:
 
-- Opening a current-goal panel with objective, status, progress, blockers, verification, and budget.
-- Creating a goal when none exists.
+- Opening a current-goal panel with objective, status, progress, blockers, verification, and budget where available.
+- Creating a goal directly from `/goal <objective>` when none exists, with no default budget prompt.
 - Explicitly replacing an existing non-terminal goal after confirmation.
 - Pausing and resuming goal continuation.
 - Canceling, clearing, or user-marking completion.
@@ -393,6 +397,7 @@ After restart, the server must not blindly continue just because the last durabl
 - Autonomous continuation uses the normal execution engine and produces normal turn records.
 - Hidden goal context is auditable but not rendered as a user transcript turn.
 - Budget accounting must not double-count cached input or separately reported reasoning tokens.
+- A goal created without an explicit budget has no default token, time, or turn budget.
 - Every subscribed client receives canonical goal updates when any client or model-facing tool changes the goal.
 
 ## Traceability
@@ -419,3 +424,5 @@ After restart, the server must not blindly continue just because the last durabl
 | Revision | Date | Author | Change Type | Notes |
 |---:|---|---|---|---|
 | 1 | 2026-05-23 | Assistant | Initial | Initial Ralph Loop goal architecture with JSONL source of truth, optional SQLite projection, bounded continuation loop, budget accounting, model-tool limits, and `/goal` integration. |
+| 1 | 2026-05-25 | Human | Refinement | Set first-milestone `/goal <objective>` creation to default to no explicit budget. |
+| 1 | 2026-05-25 | Assistant | Refinement | Clarified that budget fields are optional, usage accounting still occurs without a configured budget, and hidden context must not fabricate a default budget. |

specs/L2/tui/L2-DES-TUI-002-modern-tui-shell-layout.md

@@ -6,7 +6,7 @@ active_baseline: no
 supersedes:
 superseded_by:
 owner: Assistant
-last_updated: 2026-05-23
+last_updated: 2026-05-25
 ---
 
 # L2-DES-TUI-002 — Modern TUI Shell Layout
@@ -33,6 +33,7 @@ This document defines the high-level visual structure and responsive behavior. S
 - `L2-DES-TUI-003` defines composer and input-mode behavior.
 - `L2-DES-TUI-004` defines streaming transcript and state rendering.
 - `L2-DES-TUI-005` defines terminal lifecycle safety.
+- `L2-DES-TUI-006` defines the full transcript alternate-screen overlay entered by `Ctrl+T`.
 
 ## Design Requirement
 
@@ -214,6 +215,7 @@ Clients may optimistically render local input, but canonical state comes from th
 | related-to | L2-DES-TUI-003 | 1 | specs/L2/tui/L2-DES-TUI-003-composer-and-input-modes.md | Composer and input mode behavior fills the shell's bottom regions. |
 | related-to | L2-DES-TUI-004 | 1 | specs/L2/tui/L2-DES-TUI-004-streaming-transcript-and-state.md | Streaming transcript cells and state indicators populate the shell. |
 | related-to | L2-DES-TUI-005 | 1 | specs/L2/tui/L2-DES-TUI-005-terminal-lifecycle-safety.md | Terminal lifecycle behavior constrains inline and alternate-screen shell modes. |
+| related-to | L2-DES-TUI-006 | 1 | specs/L2/tui/L2-DES-TUI-006-full-transcript-alternate-screen.md | Defines the alternate-screen transcript review surface entered from the inline shell. |
 | specified-by | TBD | TBD | specs/L3/tui/TBD.md | L3 behavior has not been authored yet. |
 
 ## Revision Notes
@@ -225,3 +227,4 @@ Clients may optimistically render local input, but canonical state comes from th
 | 1 | 2026-05-23 | Human | Refinement | Clarified that `┃` is a single leading marker, not a rail repeated through the full cell. |
 | 1 | 2026-05-23 | Human | Refinement | Updated working indicator examples to use the spinner frame style and kept consecutive read calls on separate Explore lines. |
 | 1 | 2026-05-23 | Human | Refinement | Clarified that multi-line composer and user-message background bands may repeat `┃` on content lines, but not on padding rows. |
+| 1 | 2026-05-25 | Assistant | Refinement | Linked the shell layout to the `Ctrl+T` full transcript alternate-screen design. |

specs/L2/tui/L2-DES-TUI-003-composer-and-input-modes.md

@@ -6,7 +6,7 @@ active_baseline: no
 supersedes:
 superseded_by:
 owner: Assistant
-last_updated: 2026-05-23
+last_updated: 2026-05-25
 ---
 
 # L2-DES-TUI-003 — Composer And Input Modes
@@ -261,6 +261,7 @@ Slash-command inline rendering:
 - Parameters or placeholder text following the matched slash command use muted foreground color.
 - If the typed slash command does not match an existing command, the composer should not apply matched-command coloring.
 - Inline command coloring is presentational only. Command parsing and validation still happen when the user confirms or submits the command.
+- For `/goal`, free-form text after the command is the objective. Pressing Enter submits that objective directly to the goal command instead of opening a budget prompt or create wizard.
 
 Example matched slash command with parameter hint:
 
@@ -346,3 +347,5 @@ Rules:
 | 1 | 2026-05-23 | Human | Refinement | Removed `/diff` from the slash-command catalog. |
 | 1 | 2026-05-23 | Human | Refinement | Changed `/btw` from active-turn injection to a side conversation in an ephemeral fork. |
 | 1 | 2026-05-23 | Human | Refinement | Added `/goal` as the TUI entry point for Ralph Loop goals. |
+| 1 | 2026-05-25 | Human | Refinement | Clarified that `/goal <objective>` submits the following text as the objective without a default budget prompt. |
+| 1 | 2026-05-25 | Assistant | Refinement | Added composer-level handling guidance for direct `/goal` objective submission. |

specs/L2/tui/L2-DES-TUI-004-streaming-transcript-and-state.md

@@ -299,7 +299,7 @@ Rules:
 - The `Run` cell replaces or follows the `Running` cell when the command completes.
 - `Run` output is compressed by default.
 - The `┗` relationship marker connects the command title to its output summary.
-- Pressing `Ctrl+T` enters full-screen alternate mode for reviewing the full transcript and full output.
+- Pressing `Ctrl+T` enters the full-screen alternate transcript mode defined by `L2-DES-TUI-006` for reviewing the full transcript and full output.
 - The compressed output should show enough lines to explain the result and must indicate hidden line counts.
 
 ### Context And Compaction Cells
@@ -310,14 +310,14 @@ Compaction lifecycle cells must use these exact visible labels:
 
 ```text
 ┃ Manual Compaction Started
-┃ Automatically Compaction Started
+┃ Automatic Compaction Started
 ┃ Compaction Done
 ```
 
 Rules:
 
 - `Manual Compaction Started` appears when compaction starts because the user requested it, such as through `/compact`.
-- `Automatically Compaction Started` appears when compaction starts because context pressure crossed the configured threshold.
+- `Automatic Compaction Started` appears when compaction starts because context pressure crossed the configured threshold.
 - `Compaction Done` appears when a compaction event completes successfully and the active context snapshot has been updated.
 - These cells are transcript-area status cells, not assistant messages, user messages, or model-visible context content.
 - Inline rendering should preserve the exact label text. Counts, token estimates, or summary inspection affordances may be available in an expanded detail view, but must not change the inline label.
@@ -414,7 +414,7 @@ The TUI should map canonical server events into visible state.
 | `question.requested` | Question prompt appears and bottom status shows waiting for answer. |
 | `background_process_updated` | Background process strip and transcript state update. |
 | `usage_updated` | Header/context or turn usage display updates. |
-| `context_updated` with compaction start | Transcript area shows `Manual Compaction Started` or `Automatically Compaction Started` based on compaction trigger source. |
+| `context_updated` with compaction start | Transcript area shows `Manual Compaction Started` or `Automatic Compaction Started` based on compaction trigger source. |
 | `context_updated` with compaction completion | Transcript area shows `Compaction Done` and context pressure display updates. |
 | `context_updated` without lifecycle change | Context pressure display updates. |
 | `error_reported` | Error cell appears with phase and recovery action. |
@@ -519,6 +519,7 @@ Rules:
 | related-to | L2-DES-TOOL-001 | 1 | specs/L2/tool/L2-DES-TOOL-001-built-in-tool-system.md | Tool lifecycle, command descriptions, and result summaries feed tool cells. |
 | related-to | L2-DES-APP-004 | 1 | specs/L2/app/L2-DES-APP-004-observability-architecture.md | Diagnostic fields provide recovery and phase display. |
 | related-to | L2-DES-CONTEXT-002 | 1 | specs/L2/context/L2-DES-CONTEXT-002-context-compaction.md | Compaction lifecycle records render as transcript-area status cells. |
+| related-to | L2-DES-TUI-006 | 1 | specs/L2/tui/L2-DES-TUI-006-full-transcript-alternate-screen.md | Defines full transcript alternate-screen projection, live-tail sync, and pager controls. |
 | specified-by | TBD | TBD | specs/L3/tui/TBD.md | L3 behavior has not been authored yet. |
 
 ## Revision Notes
@@ -534,3 +535,4 @@ Rules:
 | 1 | 2026-05-23 | Human | Refinement | Clarified that multi-line user-message background bands may repeat `┃` on content lines while padding rows remain background-only. |
 | 1 | 2026-05-23 | Human | Refinement | Reconciled active work and interruption examples with the current transcript and working-indicator visual grammar. |
 | 1 | 2026-05-25 | Human | Refinement | Added exact transcript-area labels for manual compaction start, automatic compaction start, and compaction completion. |
+| 1 | 2026-05-25 | Assistant | Refinement | Linked `Ctrl+T` full transcript review to `L2-DES-TUI-006`. |

specs/L2/tui/L2-DES-TUI-005-terminal-lifecycle-safety.md

@@ -6,7 +6,7 @@ active_baseline: no
 supersedes:
 superseded_by:
 owner: Assistant
-last_updated: 2026-05-23
+last_updated: 2026-05-25
 ---
 
 # L2-DES-TUI-005 — Terminal Lifecycle Safety
@@ -25,6 +25,7 @@ The TUI runs inside a user's terminal. It may change terminal modes, render live
 - `L1-REQ-APP-007` requires inline mode and alternate full-screen mode where appropriate.
 - `L1-REQ-TUI-007` requires stable layout across resize events.
 - `L2-DES-TUI-002` defines the TUI shell used by inline and alternate-screen modes.
+- `L2-DES-TUI-006` defines one concrete alternate-screen overlay entered by `Ctrl+T`.
 
 ## Design Requirement
 
@@ -84,6 +85,7 @@ Rules:
 - Exiting alternate-screen mode must restore the normal screen and terminal modes.
 - The same logical shell layout should be used inside alternate-screen mode.
 - If alternate-screen entry fails, the TUI should fall back to inline mode or fail with an understandable message.
+- Overlay-style alternate-screen surfaces, including full transcript review and the resume session browser, should return control to inline rendering through a single cleanup path that leaves alternate screen and schedules a fresh inline frame.
 
 ## Startup Rules
 
@@ -167,10 +169,12 @@ The message should be emitted only when useful and should not expose internal de
 | related-to | L1-REQ-APP-007 | 1 | specs/L1/L1-REQ-APP-007-tui.md | Inline and alternate-screen modes are high-level TUI requirements. |
 | related-to | L1-REQ-TUI-007 | 1 | specs/L1/L1-REQ-TUI-007-responsive-layout-readability.md | Resize handling must preserve layout and safe exit behavior. |
 | related-to | L2-DES-TUI-002 | 1 | specs/L2/tui/L2-DES-TUI-002-modern-tui-shell-layout.md | Defines the shell layout whose live region must be cleaned up safely. |
+| related-to | L2-DES-TUI-006 | 1 | specs/L2/tui/L2-DES-TUI-006-full-transcript-alternate-screen.md | Defines a concrete alternate-screen overlay and its return-to-inline lifecycle. |
 | specified-by | TBD | TBD | specs/L3/tui/TBD.md | L3 behavior has not been authored yet. |
 
 ## Revision Notes
 
 | Revision | Date | Author | Change Type | Notes |
 |---:|---|---|---|---|
 | 1 | 2026-05-23 | Assistant | Initial | Initial terminal lifecycle safety design. |
+| 1 | 2026-05-25 | Assistant | Refinement | Linked terminal lifecycle safety to the current full transcript overlay and resume-browser alternate-screen cleanup path. |