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

NS6: Pi and local tool bridge #6

New Issue
Closed
opened 2026-06-20 23:28:12 +00:00 by tmk241 · 1 comment
tmk241 commented 2026-06-20 23:28:12 +00:00
Owner
Copy Link
Copy Source

OUTCOME: Pi and trusted local tools can inspect and assist the active session through the same local socket protocol without turning mim into a plugin host.

WHY NOW: PRODUCT.md wants Pi-like assistance as a local protocol client while refusing plugin creep and remote control planes.

AUTHORITY: PRODUCT.md; req: session/002; req: session/004; req: governance/002-003

SLICES:

  • #33 NS6 slice: Add compact mimctl context output
  • #34 NS6 slice: Add explicit tool command path with protocol logging
  • #35 NS6 slice: Add Pi panel/context integration
  • #36 NS6 slice: Guard local socket scope and not-built diagnostics

MEMBERSHIP MECHANISM: Gitea fallback via this parent checklist plus explicit parent link in each child issue body.

AGENT AUTHORITY DEFAULTS:

  • Delivery authority: local-commit
  • Tracker authority: child issues may be commented and closed when their acceptance passes; this parent may be commented as children complete.
  • Handoff state: committed clean, tracker commented/closed for completed child slices.

BLOCKERS: none

PROOF: A local tool can query compact context, request an explicit editor action, and leave observable/replayable protocol evidence; absent tools and excluded build profiles fail clearly.

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 remote service, no plugin API, no autonomous hidden edits, no required Pi dependency for mim-min or mim-code.

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.

OUTCOME: Pi and trusted local tools can inspect and assist the active session through the same local socket protocol without turning `mim` into a plugin host. WHY NOW: PRODUCT.md wants Pi-like assistance as a local protocol client while refusing plugin creep and remote control planes. AUTHORITY: PRODUCT.md; req: session/002; req: session/004; req: governance/002-003 SLICES: - [x] #33 NS6 slice: Add compact mimctl context output - [x] #34 NS6 slice: Add explicit tool command path with protocol logging - [x] #35 NS6 slice: Add Pi panel/context integration - [x] #36 NS6 slice: Guard local socket scope and not-built diagnostics MEMBERSHIP MECHANISM: Gitea fallback via this parent checklist plus explicit parent link in each child issue body. AGENT AUTHORITY DEFAULTS: - Delivery authority: local-commit - Tracker authority: child issues may be commented and closed when their acceptance passes; this parent may be commented as children complete. - Handoff state: committed clean, tracker commented/closed for completed child slices. BLOCKERS: none PROOF: A local tool can query compact context, request an explicit editor action, and leave observable/replayable protocol evidence; absent tools and excluded build profiles fail clearly. 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 remote service, no plugin API, no autonomous hidden edits, no required Pi dependency for `mim-min` or `mim-code`. 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.
tmk241 added this to the v1 milestone 2026-06-20 23:28:12 +00:00
tmk241 added the northstargoal labels 2026-06-20 23:28:12 +00:00
tmk241 commented 2026-06-21 03:45:28 +00:00
Author
Owner
Copy Link
Copy Source

NS6 parent proof is complete; closing parent.

Children:

  • #33 compact mimctl context output: closed
  • #34 explicit tool command path with protocol logging: closed
  • #35 Pi panel/context integration: closed
  • #36 local socket scope and not-built diagnostics: closed

Verification on clean tree f5c81155ea:

  • zig build test: pass
  • zig build v1-smoke: pass
  • zig build run -- profile: pass
  • zig build run -- remote: expected failure with mim: remote not built in this profile
  • redgate lint / health: pass

Parent PROOF demonstrated: local tools can query compact context and request explicit editor/tool actions through the local protocol; protocol/replay evidence exists in the implemented paths; absent/excluded capabilities fail clearly. Boundaries preserved: no remote service, no plugin API, no autonomous hidden edits, and no required Pi dependency for minimal/coding profiles.

NS6 parent proof is complete; closing parent. Children: - #33 compact mimctl context output: closed - #34 explicit tool command path with protocol logging: closed - #35 Pi panel/context integration: closed - #36 local socket scope and not-built diagnostics: closed Verification on clean tree f5c81155ea5f: - zig build test: pass - zig build v1-smoke: pass - zig build run -- profile: pass - zig build run -- remote: expected failure with `mim: remote not built in this profile` - redgate lint / health: pass Parent PROOF demonstrated: local tools can query compact context and request explicit editor/tool actions through the local protocol; protocol/replay evidence exists in the implemented paths; absent/excluded capabilities fail clearly. Boundaries preserved: no remote service, no plugin API, no autonomous hidden edits, and no required Pi dependency for minimal/coding profiles.
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 goal northstar
Milestone
No items
No Milestone v1
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#6
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?