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

NS7: V1 release hardening and rollout #7

New Issue
Open
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: mim can be built, installed, tested, and dogfooded by actual users as a prod-ready v1 without surprising configuration or hidden dependencies.

WHY NOW: The PRODUCT.md proof is real user choice over Neovim for small iPhone SSH fixes; rollout needs reliable builds, profile boundaries, tests, install path, and supportable diagnostics.

AUTHORITY: PRODUCT.md; req: governance/001-005; all v1 requirement rows as release gates

SLICES:

  • #37 NS7 slice: Implement named build profiles
  • #38 NS7 slice: Add installable server binary path
  • #39 NS7 slice: Create v1 E2E fixture suite
  • #40 NS7 slice: Add performance and failure diagnostics gates
  • #41 NS7 slice: Dogfood one real iPhone SSH fix and close v1 gaps

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: external real iPhone SSH dogfood receipt is required for #41. Local build/test/install proof is complete; closure needs either a pasted DOGFOOD.md receipt from an actual iPhone SSH edit or explicit tracker acceptance change.

PROOF: A fresh server checkout can build named profiles, run tests, install the binary, perform the mobile SSH dogfood scenario, and diagnose common failures without hidden setup.

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 native app, cloud service, telemetry, package manager, runtime config ecosystem, or compatibility promise beyond documented v1 boundaries.

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: `mim` can be built, installed, tested, and dogfooded by actual users as a prod-ready v1 without surprising configuration or hidden dependencies. WHY NOW: The PRODUCT.md proof is real user choice over Neovim for small iPhone SSH fixes; rollout needs reliable builds, profile boundaries, tests, install path, and supportable diagnostics. AUTHORITY: PRODUCT.md; req: governance/001-005; all v1 requirement rows as release gates SLICES: - [x] #37 NS7 slice: Implement named build profiles - [x] #38 NS7 slice: Add installable server binary path - [x] #39 NS7 slice: Create v1 E2E fixture suite - [x] #40 NS7 slice: Add performance and failure diagnostics gates - [ ] #41 NS7 slice: Dogfood one real iPhone SSH fix and close v1 gaps 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: external real iPhone SSH dogfood receipt is required for #41. Local build/test/install proof is complete; closure needs either a pasted DOGFOOD.md receipt from an actual iPhone SSH edit or explicit tracker acceptance change. PROOF: A fresh server checkout can build named profiles, run tests, install the binary, perform the mobile SSH dogfood scenario, and diagnose common failures without hidden setup. 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 native app, cloud service, telemetry, package manager, runtime config ecosystem, or compatibility promise beyond documented v1 boundaries. 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:46:44 +00:00
Author
Owner
Copy Link
Copy Source

Tracker accounting update: NS7 is blocked only on #41 external dogfood evidence.

I changed the stale BLOCKERS: none field on #7 and #41 to reflect the real blocker: the required DOGFOOD.md receipt from an actual iPhone SSH edit, or an explicit tracker acceptance change. No implementation blocker is currently known from local verification.

Current local proof at f5c81155ea remains:

  • zig build test: pass
  • zig build v1-smoke: pass
  • zig build: pass
  • verify-install-code path documented and previously passing

Not closing #7 or #41: PRODUCT.md proof still requires the real mobile SSH dogfood receipt.

Tracker accounting update: NS7 is blocked only on #41 external dogfood evidence. I changed the stale `BLOCKERS: none` field on #7 and #41 to reflect the real blocker: the required DOGFOOD.md receipt from an actual iPhone SSH edit, or an explicit tracker acceptance change. No implementation blocker is currently known from local verification. Current local proof at f5c81155ea5f remains: - zig build test: pass - zig build v1-smoke: pass - zig build: pass - verify-install-code path documented and previously passing Not closing #7 or #41: PRODUCT.md proof still requires the real mobile SSH dogfood receipt.
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#7
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?