docs(insta): insta build verdict + deploy <dir> Dockerfile requirement — mirror insta-cli #142
Mirror of InsForge/insta-cli#142 (AGENTS.md non-negotiable #4: command/flag changes must be mirrored here). That PR stops the CLI promising a nixpacks lane that insta deploy <dir> does not have; this one stops the agent-facing reference promising it — the reference is the surface agents read to decide what to run, so leaving it saying "nixpacks Dockerfile → deployable" would make agents issue the exact command the CLI PR stops humans from being told.
Requested by the r2d2 review on #142 (Critical: "the required skills/insta/cli-reference.md mirror is not updated").
The new truth, mirrored
| Surface | Before | After |
|---|---|---|
insta build row | "the Dockerfile that would be used (yours, or nixpacks-generated …)" | only a Dockerfile in the dir makes it deployable; a nixpacks-detected dir gets a ⚠ Dockerfile check and needs-attention (exit 0); the --explain nixpacks Dockerfile is for inspection, not standalone (it COPYs .nixpacks/ support files) — never save it as Dockerfile |
insta deploy row | "needs a Dockerfile" | requires one in the dir, no nixpacks lane on this path; names the three options the CLI's error now prints (write a Dockerfile / --image / connect the repo on GitHub, whose server-side lane builds Dockerfile-less repos with nixpacks) |
| Deploy code block | insta deploy ./app only | insta build ./app first, then deploy; the no-Dockerfile outcome spelled out |
| Feature note | "Fly remote builder" | "Fly remote builder of the dir's own Dockerfile" |
references/deploy.md step 1 | "no buildpacks yet — no Dockerfile → use --image, or add one" | no nixpacks lane on this path, but the GitHub-connected lane exists for Dockerfile-less repos; same do-not-save-the---explain-Dockerfile warning |
No other commands touched. Version gate stated as CLI ≥ 0.0.48 (the release that will carry #142; the reference already uses that marker for setup agent --project).
Checks
- Repo CI (
no unresolved merge-conflict markers) run locally: clean. - Grep for the retired phrasing (
would be used,buildpacks yet,nixpacks-generated) acrossinsta/: no hits.
Merge alongside insta-cli#142; neither should land without the other.
🤖 Generated with Claude Code
Summary by cubic
Mirrors insta-cli#142 so the agent-facing docs stop promising the nixpacks lane that insta deploy <dir> no longer has.
insta buildnow requires a Dockerfile in the dir for adeployableverdict; nixpacks-detected dirs without one stop atneeds-attention(exit 0) on CLI 0.0.48+.- The nixpacks
--explainoutput is flagged inspection-only and must never be saved asDockerfile. insta deploy <dir>docs spell out the in-dir Dockerfile requirement and the three fallback options the CLI prints on failure.references/deploy.mdgets the same correction in its source-mode step 1, replacing the stale "no buildpacks yet" note.