Skip to content

docs(0.2): AI trust boundary + Node 22 prominence + release-smoke matrix#144

Open
pmclSF wants to merge 1 commit intomainfrom
feat/0.2-clarity-distribution
Open

docs(0.2): AI trust boundary + Node 22 prominence + release-smoke matrix#144
pmclSF wants to merge 1 commit intomainfrom
feat/0.2-clarity-distribution

Conversation

@pmclSF
Copy link
Copy Markdown
Owner

@pmclSF pmclSF commented May 2, 2026

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.

  • Track 7.3 — AI execution trust-boundary doc. New page
    docs/product/ai-trust-boundary.md explicitly documents what
    Terrain 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, and
    ai run --ingest-only, plus the 0.2 → 0.3 sandboxing roadmap.
  • Track 8.1 — Node 22 prominence. README and
    docs/user-guides/getting-started.md now call out the Node 22
    npm-path requirement up front, with explicit brew / go install
    alternatives for CI on Node 20 LTS.
  • Track 8.2 — Release-smoke matrix expansion. Post-publish
    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-Archive on Windows; both verify
    terrain version --json reports 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 ./... clean
  • go vet ./... clean
  • make docs-verify passes
  • actionlint .github/workflows/release.yml reports no new
    issues (existing SC2035 info-level warnings on line 231
    are pre-existing and unrelated)
  • Workflow matrix verified end-to-end on next tagged release
    (cannot exercise pre-merge — needs a real published archive)
  • AI trust-boundary doc reviewed for accuracy of per-command
    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

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>
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 2, 2026

[INFO] Terrain — Informational only

Insufficient data to assess change risk confidently.

Metric Value
Changed files 4 (0 source · 0 test)

Limitations
  • No coverage artifacts provided; protection gaps reflect missing data, not measured absence. Provide --coverage to improve accuracy.
  • Mixed test cultures reduce cross-framework optimization confidence. Consider standardizing on fewer frameworks.

Generated by Terrain · terrain pr --json for machine-readable output

Targeted Test Results

No tests selected — change affects only non-code files.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 2, 2026

Terrain AI Risk Review

Metric Value
AI surfaces 13
Eval scenarios 16
Impacted scenarios 0
Uncovered surfaces 13

Decision: PASS — AI surfaces are covered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant