tmk241/mim
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

NS11 slice: Make file and Pi panels discoverable #80

New Issue
Closed
opened 2026-06-21 18:44:00 +00:00 by tmk241 · 1 comment
tmk241 commented 2026-06-21 18:44:00 +00:00
Owner
Copy Link
Copy Source

OBJECTIVE: Add discoverable Normal-mode paths for opening the file panel and Pi panel so users are not stuck guessing how to access core workbench surfaces.

AUTHORITY: Parent #76 NS11; PRODUCT.md protocol-first terminal editor; KEYMAP.md panel grammar; user report that file panel and Pi panel access are not discoverable.

AGENT AUTHORITY:

  • Delivery authority: local-commit
  • Tracker authority: this issue may be commented and closed when acceptance passes
  • Handoff state: committed clean, tracker commented/closed

PARENT: #76 by parent checklist fallback plus explicit parent reference in this body.

SCOPE: keymap/leader entries for file and Pi panels; status/help discoverability; terminal E2E proof of opening, navigating, and closing those panels.

BOUNDARIES: Do not redesign every panel command, implement a native client, or add plugin/config surfaces. Keep existing protocol panel commands intact.

ACCEPTANCE: from Normal mode, a documented mobile SSH path opens file panel; a documented mobile SSH path opens Pi panel or Pi run prompt/panel; panel close/navigation is visible; terminal E2E proves both paths and captures visible artifacts.

REGRESSION CLASS: core panels exist but are hidden behind protocol-only commands or undocumented bindings; new shortcuts collide with common editing keys.

EVIDENCE ARTIFACTS: terminal E2E screenshots/transcripts/keystrokes for file and Pi panel access.

REQUIREMENT IMPACT: protects/updates panel and input requirements.

VERIFICATION: zig build test; zig build terminal-e2e; redgate lint/health if requirements change.

BLOCKERS: none.

OBJECTIVE: Add discoverable Normal-mode paths for opening the file panel and Pi panel so users are not stuck guessing how to access core workbench surfaces. AUTHORITY: Parent #76 NS11; PRODUCT.md protocol-first terminal editor; KEYMAP.md panel grammar; user report that file panel and Pi panel access are not discoverable. AGENT AUTHORITY: - Delivery authority: local-commit - Tracker authority: this issue may be commented and closed when acceptance passes - Handoff state: committed clean, tracker commented/closed PARENT: #76 by parent checklist fallback plus explicit parent reference in this body. SCOPE: keymap/leader entries for file and Pi panels; status/help discoverability; terminal E2E proof of opening, navigating, and closing those panels. BOUNDARIES: Do not redesign every panel command, implement a native client, or add plugin/config surfaces. Keep existing protocol panel commands intact. ACCEPTANCE: from Normal mode, a documented mobile SSH path opens file panel; a documented mobile SSH path opens Pi panel or Pi run prompt/panel; panel close/navigation is visible; terminal E2E proves both paths and captures visible artifacts. REGRESSION CLASS: core panels exist but are hidden behind protocol-only commands or undocumented bindings; new shortcuts collide with common editing keys. EVIDENCE ARTIFACTS: terminal E2E screenshots/transcripts/keystrokes for file and Pi panel access. REQUIREMENT IMPACT: protects/updates panel and input requirements. VERIFICATION: `zig build test`; `zig build terminal-e2e`; redgate lint/health if requirements change. BLOCKERS: none.
tmk241 added the sliceready-for-agent labels 2026-06-21 18:44:00 +00:00
tmk241 commented 2026-06-21 19:27:11 +00:00
Author
Owner
Copy Link
Copy Source

Closing receipt for #80.

Implemented in local commit 9ef2f97 (Expose file and Pi panels):

  • Space f is visible in the leader rail and opens the existing files panel.
  • Space P is visible in the leader rail and opens a Pi/local trusted tool panel using the shared panel model.
  • Space p remains the coding symbol rail, avoiding a regression from the NS11 symbol work.
  • KEYMAP.md now documents file panel, Pi panel, and the Space p symbol rail without stale ambiguity.
  • Added unit coverage for leader discovery and the Pi panel render path.
  • Added browser-terminal E2E coverage that opens/closes both file and Pi panels.

Verification:

  • zig build ✅
  • zig build test ✅
  • zig build terminal-e2e ✅
  • zig build run -- --help ✅
  • zig build --prefix /tmp/mim-install verify-install-code ✅
  • redgate list /opt/repositories/mim/REQUIREMENTS.md && redgate lint /opt/repositories/mim/REQUIREMENTS.md && redgate health /opt/repositories/mim/REQUIREMENTS.md ✅
Closing receipt for #80. Implemented in local commit `9ef2f97` (`Expose file and Pi panels`): - `Space f` is visible in the leader rail and opens the existing files panel. - `Space P` is visible in the leader rail and opens a Pi/local trusted tool panel using the shared panel model. - `Space p` remains the coding symbol rail, avoiding a regression from the NS11 symbol work. - KEYMAP.md now documents file panel, Pi panel, and the `Space p` symbol rail without stale ambiguity. - Added unit coverage for leader discovery and the Pi panel render path. - Added browser-terminal E2E coverage that opens/closes both file and Pi panels. Verification: - `zig build` ✅ - `zig build test` ✅ - `zig build terminal-e2e` ✅ - `zig build run -- --help` ✅ - `zig build --prefix /tmp/mim-install verify-install-code` ✅ - `redgate list /opt/repositories/mim/REQUIREMENTS.md && redgate lint /opt/repositories/mim/REQUIREMENTS.md && redgate health /opt/repositories/mim/REQUIREMENTS.md` ✅
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
goal
Issue has a Pi goal contract
 northstar
Parent outcome for v1 product work
 ready-for-agent
Scoped and unblocked for agent implementation
 slice
Executable vertical child issue
No Label ready-for-agent slice
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
tmk241
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: tmk241/mim#80
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?