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

NS9: Newed-matched production colorscheme #57

New Issue
Open
opened 2026-06-21 09:14:24 +00:00 by tmk241 · 0 comments
tmk241 commented 2026-06-21 09:14:24 +00:00
Owner
Copy Link
Copy Source

OUTCOME: mim adopts a production-ready terminal colorscheme aligned with /opt/repositories/newed/newed-theme (newed night) across editor text, syntax, panels, diagnostics, hover/signature, jobs, and status chrome while preserving mobile/narrow-viewport usability and terminal compatibility.

WHY NOW: The keymap/production editor work now has enough surface area that visual hierarchy matters. The user explicitly wants a colorscheme matching newed, and mim currently has almost no color/theme surface.

AUTHORITY: PRODUCT.md mobile-first terminal editor boundary; KEYMAP.md panel/hover/tool surfaces; REQUIREMENTS.md ui/input/coding/testing/governance rows; /opt/repositories/newed/newed-theme/REQUIREMENTS.md; /opt/repositories/newed/newed-theme/src/default_theme.rs, palette.rs, style.rs, adapt.rs, and highlight.rs.

SLICES:

  • #58 NS9 slice: Add source-patched newed palette tokens and terminal adaptation
  • #59 NS9 slice: Apply newed colors to editor chrome, cursor, selection, and search
  • #60 NS9 slice: Theme syntax highlighting with newed highlight groups
  • #61 NS9 slice: Theme diagnostics, lint, jobs, and provider identity
  • #62 NS9 slice: Theme panels, hover, signature help, and command rails
  • #63 NS9 slice: Add terminal color-mode probes and accessibility guardrails
  • #64 NS9 slice: Final visual dogfood and newed parity receipt

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 acceptance passes; this parent may be commented as children complete and updated to maintain the child checklist.
  • Handoff state: committed clean, tracker commented/closed for completed child slices.

BLOCKERS: none for slicing. Final aesthetic parity requires visual/dogfood review in a real terminal.

PROOF: In a fresh terminal, mim renders with a coherent newed-matched palette; syntax, diagnostics, panels, hover/signature, selection, search matches, jobs, dirty state, and status chrome are distinguishable on narrow viewports; truecolor/256-color/16-color/mono modes degrade legibly; and visual fixtures/dogfood receipts show no hidden config/plugin/runtime-theme dependency.

TEST STANDARD: Each child slice must include deterministic render/protocol tests where possible plus adversarial terminal/color-mode cases. Use visual dogfood only for final aesthetic parity, not as the only correctness proof.

NON-GOALS: No runtime theme config files, theme marketplace, plugin system, external dependency on the newed repo at runtime, native app styling, screenshots as brittle primary tests, or copying large unrelated newed architecture into mim.

GOAL: Implement this Northstar by completing its linked child slices. Close this parent only when every child is closed and the PROOF above is demonstrated.

OUTCOME: `mim` adopts a production-ready terminal colorscheme aligned with `/opt/repositories/newed/newed-theme` (`newed night`) across editor text, syntax, panels, diagnostics, hover/signature, jobs, and status chrome while preserving mobile/narrow-viewport usability and terminal compatibility. WHY NOW: The keymap/production editor work now has enough surface area that visual hierarchy matters. The user explicitly wants a colorscheme matching newed, and mim currently has almost no color/theme surface. AUTHORITY: PRODUCT.md mobile-first terminal editor boundary; KEYMAP.md panel/hover/tool surfaces; REQUIREMENTS.md ui/input/coding/testing/governance rows; `/opt/repositories/newed/newed-theme/REQUIREMENTS.md`; `/opt/repositories/newed/newed-theme/src/default_theme.rs`, `palette.rs`, `style.rs`, `adapt.rs`, and `highlight.rs`. SLICES: - [x] #58 NS9 slice: Add source-patched newed palette tokens and terminal adaptation - [x] #59 NS9 slice: Apply newed colors to editor chrome, cursor, selection, and search - [x] #60 NS9 slice: Theme syntax highlighting with newed highlight groups - [x] #61 NS9 slice: Theme diagnostics, lint, jobs, and provider identity - [x] #62 NS9 slice: Theme panels, hover, signature help, and command rails - [x] #63 NS9 slice: Add terminal color-mode probes and accessibility guardrails - [ ] #64 NS9 slice: Final visual dogfood and newed parity receipt 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 acceptance passes; this parent may be commented as children complete and updated to maintain the child checklist. - Handoff state: committed clean, tracker commented/closed for completed child slices. BLOCKERS: none for slicing. Final aesthetic parity requires visual/dogfood review in a real terminal. PROOF: In a fresh terminal, `mim` renders with a coherent newed-matched palette; syntax, diagnostics, panels, hover/signature, selection, search matches, jobs, dirty state, and status chrome are distinguishable on narrow viewports; truecolor/256-color/16-color/mono modes degrade legibly; and visual fixtures/dogfood receipts show no hidden config/plugin/runtime-theme dependency. TEST STANDARD: Each child slice must include deterministic render/protocol tests where possible plus adversarial terminal/color-mode cases. Use visual dogfood only for final aesthetic parity, not as the only correctness proof. NON-GOALS: No runtime theme config files, theme marketplace, plugin system, external dependency on the newed repo at runtime, native app styling, screenshots as brittle primary tests, or copying large unrelated newed architecture into mim. GOAL: Implement this Northstar by completing its linked child slices. Close this parent only when every child is closed and the PROOF above is demonstrated.
tmk241 added the goalnorthstar labels 2026-06-21 09:17:09 +00:00
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
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#57
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?