docs(0.2): AI trust boundary + Node 22 prominence + release-smoke matrix#144
Open
docs(0.2): AI trust boundary + Node 22 prominence + release-smoke matrix#144
Conversation
Bundle of three Track 7 / Track 8 deliverables for the parity-gated 0.2.0 release plan. Track 7.3 — AI execution trust-boundary doc Adds docs/product/ai-trust-boundary.md spelling out what Terrain executes vs. what it parses, where the LLM call actually happens (inside the eval framework, not Terrain), the per-command trust surface for `analyze`, `ai list/doctor`, `ai run`, and `ai run --ingest-only`, plus the 0.2 → 0.3 sandboxing roadmap. Closes the "is this safe?" question that the launch-readiness review flagged as insufficiently documented. Track 8.1 — Node 22 prominence Documents the Node 22 npm-path requirement up front in README and docs/user-guides/getting-started.md, with explicit brew / `go install` alternatives for CI images on Node 20 LTS. Avoids the silent install-time failure mode the review caught. Track 8.2 — Release-smoke matrix expansion Extends the post-publish smoke job from linux/amd64-only to also cover darwin/arm64 (Apple Silicon — the modern Mac default) and windows/amd64 (the most likely Windows shape). Matrix uses the POSIX tar.gz extract path on Linux/macOS and a pwsh Expand-Archive path on Windows; both verify `terrain version --json` reports the tagged version. Catches per-platform "wrong build / wrong version string" regressions that previously could only surface after a user installed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
[INFO] Terrain — Informational only
Limitations
Generated by Terrain · Targeted Test ResultsNo tests selected — change affects only non-code files. |
Terrain AI Risk Review
Decision: PASS — AI surfaces are covered. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bundle of three Track 7 / Track 8 deliverables for the parity-gated
0.2.0 release plan. All three close items the launch-readiness
review flagged as insufficiently documented or insufficiently
verified.
docs/product/ai-trust-boundary.mdexplicitly documents whatTerrain executes vs. parses, where the LLM call actually
happens (inside the eval framework, not Terrain), per-command
trust surface for
analyze,ai list/doctor,ai run, andai run --ingest-only, plus the 0.2 → 0.3 sandboxing roadmap.docs/user-guides/getting-started.mdnow call out the Node 22npm-path requirement up front, with explicit brew /
go installalternatives for CI on Node 20 LTS.
smoke job goes from linux/amd64-only to also cover darwin/arm64
(Apple Silicon) and windows/amd64. Matrix uses POSIX tar.gz on
Linux/macOS and pwsh
Expand-Archiveon Windows; both verifyterrain version --jsonreports the tagged version.Why these three together
They're independent in code but co-located in the plan: all three
are "honest about how this thing actually installs and runs"
items. Bundling minimizes review thrash on a doc-and-CI-config
PR. None changes Go code; the only Go-relevant change is the
release workflow.
Test plan
go build ./...cleango vet ./...cleanmake docs-verifypassesactionlint .github/workflows/release.ymlreports no newissues (existing SC2035 info-level warnings on line 231
are pre-existing and unrelated)
(cannot exercise pre-merge — needs a real published archive)
claims against current code paths
Plan tracker
Closes Track 7.3, 8.1, 8.2 from the parity-gated 0.2.0 plan.
Remaining 0.2.0 work (per plan): Track 3.3-3.5, 5.1, 5.3, 5.6, 6.x,
7.1-7.2/7.4-7.5, 9.x, 10.2-10.8.
🤖 Generated with Claude Code