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

NS5: Syntax and LSP coding intelligence #5

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

OUTCOME: Syntax highlighting, diagnostics, and LSP navigation/actions are built-in coding primitives that work through the protocol and panel model.

WHY NOW: PRODUCT.md makes coding central; mobile usability requires diagnostics/symbols/LSP without plugin setup or desktop-only affordances.

AUTHORITY: PRODUCT.md; req: coding/002-005; req: ui/002; req: governance/002

SLICES:

  • #28 NS5 slice: Add source-patched Tree-sitter highlighting v1
  • #29 NS5 slice: Implement LSP process lifecycle and document sync
  • #30 NS5 slice: Show LSP diagnostics through panels/status
  • #31 NS5 slice: Add LSP navigation and symbol panels
  • #32 NS5 slice: Add rename and code actions
  • #42 NS5 slice: Add viewport-aware LSP hover, signature help, and parameter navigation

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 fixture/fake language server and at least one Tree-sitter language prove highlighting, diagnostics, hover, signature help, parameter navigation, go-to-definition, references, symbols, rename, and code actions through panels without hidden installers.

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 language-server installer, no runtime grammar package manager, no full plugin ecosystem, no broad language registry before one path is proven.

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: Syntax highlighting, diagnostics, and LSP navigation/actions are built-in coding primitives that work through the protocol and panel model. WHY NOW: PRODUCT.md makes coding central; mobile usability requires diagnostics/symbols/LSP without plugin setup or desktop-only affordances. AUTHORITY: PRODUCT.md; req: coding/002-005; req: ui/002; req: governance/002 SLICES: - [x] #28 NS5 slice: Add source-patched Tree-sitter highlighting v1 - [x] #29 NS5 slice: Implement LSP process lifecycle and document sync - [x] #30 NS5 slice: Show LSP diagnostics through panels/status - [x] #31 NS5 slice: Add LSP navigation and symbol panels - [x] #32 NS5 slice: Add rename and code actions - [x] #42 NS5 slice: Add viewport-aware LSP hover, signature help, and parameter navigation 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 fixture/fake language server and at least one Tree-sitter language prove highlighting, diagnostics, hover, signature help, parameter navigation, go-to-definition, references, symbols, rename, and code actions through panels without hidden installers. 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 language-server installer, no runtime grammar package manager, no full plugin ecosystem, no broad language registry before one path is proven. 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:11 +00:00
tmk241 added the northstargoal labels 2026-06-20 23:28:11 +00:00
tmk241 commented 2026-06-21 02:51:31 +00:00
Author
Owner
Copy Link
Copy Source

All current NS5 child slices are implemented and closed: #28 syntax profiles, #29 LSP lifecycle/document sync, #30 diagnostics, #31 navigation/symbol panels, #32 rename/code actions, and #42 viewport-aware hover/signature/parameter navigation. Clean-tree verification after final child: zig build test, zig build, zig build run -- --help, redgate lint/health all pass at d1141c89a2.

All current NS5 child slices are implemented and closed: #28 syntax profiles, #29 LSP lifecycle/document sync, #30 diagnostics, #31 navigation/symbol panels, #32 rename/code actions, and #42 viewport-aware hover/signature/parameter navigation. Clean-tree verification after final child: zig build test, zig build, zig build run -- --help, redgate lint/health all pass at d1141c89a2b4.
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#5
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?