Design CLI and TUI controls for context curation

[ScottMorris]

Summary

Define the first user-facing controls for reviewing and curating active context from the CLI and TUI.

Scope

• decide the minimum CLI surface for inspecting and excluding context items
• decide the minimum TUI surface for selection, visibility, and reversal
• keep the first version small enough to ship before broader transcript-style tooling

Questions

• should the first control surface target notes only, or also hints and scopes?
• which flows matter most: inspect, exclude, restore, and pin?
• should curation operate on the active item, the selected item, or both?
• how should the UI explain the difference between stored history and active context?

Acceptance

• documented v1 CLI surface
• documented v1 TUI surface
• explicit non-goals for the first release