NS3: Narrow terminal UI and panel grammar #3
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
OUTCOME: The terminal client stays usable on narrow iPhone viewports and every auxiliary surface uses one transient panel model instead of desktop splits.
WHY NOW: PRODUCT.md makes narrow viewport awareness central; panels are the UI seam for files, git, diagnostics, LSP, jobs, terminal, and Pi.
AUTHORITY: PRODUCT.md; req: ui/001-002; req: session/003
SLICES:
MEMBERSHIP MECHANISM: Gitea fallback via this parent checklist plus explicit parent link in each child issue body.
AGENT AUTHORITY DEFAULTS:
BLOCKERS: none
PROOF: On a narrow terminal, users can open, filter, select, close, and return from panels without layout overflow or permanent split assumptions.
TEST STANDARD: Each child slice must carry its test weight: regular tests prove the intended payoff works, and adversarial tests cover realistic failure, boundary, or regression cases. Prefer protocol/headless/replay/fixture tests over brittle UI snapshots unless rendering behavior is the claim. See req: testing/001 through req: testing/004.
NON-GOALS: No desktop split-first UI, no full window manager, no theming system, no dashboard surface.
GOAL: Implement this Northstar by completing its linked child slices without leaving the product/refusal boundary in PRODUCT.md. Close this parent only when every child is closed and the PROOF above is demonstrated.
NS3 complete.
Children closed:
Proof/evidence:
zig build test: passzig build: passzig build run -- --help: passredgate lint/redgate health: passBoundary held: no concrete file/git/LSP/job/Pi panels, desktop split-first UI, telemetry, hosted reporting, or broad benchmark suite added.