NS7 slice: Add installable server binary path #38
Reference in New Issue
Block a user
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?
OBJECTIVE: Provide the simplest documented way to install the selected binary on a server reachable by SSH.
AUTHORITY: Parent #7
NS7: V1 release hardening and rollout; PRODUCT.md; REQUIREMENTS.md (PRODUCT.md; req: governance/001-005; all v1 requirement rows as release gates).AGENT AUTHORITY:
PARENT: #7 via explicit issue link and parent checklist.
SCOPE: The smallest source/docs/tests needed to make this behavior real and verified.
BOUNDARIES: No package manager integration unless later proven necessary.
ACCEPTANCE: A clean checkout can build and install/copy a binary;
mim --versionor equivalent verifies the installed artifact.VERIFICATION: Run the cheapest command that proves acceptance. Include regular tests for the intended payoff and adversarial tests for realistic failure, boundary, or regression cases. If no implementation test command exists yet, create/record the canonical command in AGENTS.md as part of the slice.
BLOCKERS: none
GOAL: Implement this vertical slice to the ACCEPTANCE above, keep the repo clean, cite relevant
req:anchors in code/tests where applicable, and close only after verification passes.Implemented in commits
162634cb7aand30faf3765f.Verification:
Regular tests: added install-min/install-code/install-full build steps that copy the selected named profile to /bin/mim; added verify-install-* steps that execute the installed artifact with --version. INSTALL.md documents the server copy path and version check; AGENTS.md records the canonical verification command.
Adversarial test: initial receipt caught incorrect --prefix ordering; docs were corrected to Zig global option order (
zig build --prefix <dir> verify-install-code) and reverified on clean tree with the copied binary present under the requested prefix.Boundary: simple Zig build install/copy and --version proof only. No package manager, service manager, bootstrap installer, remote provisioning, signing, or release upload added.