Document v0 concerns and release branch

[IlyaasK]

Summary

• Fix the README concerns link text now that the target document exists.
• Update release docs to avoid stale main wording and require confirming the repository canonical post-merge branch before tagging.

Why this is v0 work

This closes the v0 docs-correctness gap without changing provider behavior. The provider surface remains intentionally narrow: provider config, kernel_browser_pool, lookup data sources, and browser-pool import.

Intentionally unsupported in v0

• force_destroy remains deferred to v1/future; v0 delete stays durable and non-forceful.
• tfplugingen-framework/codegen remains deferred to v1/future.
• Runtime/session operations remain out of Terraform: no acquire, release, flush, app invocation, screenshots, logs, live view, force recovery, or leased-browser state.
• No project/profile/proxy/extension resources are added.

Tests run

• gofmt -l cmd internal
• go test -short -timeout=2m ./...
• go vet ./...
• terraform fmt -check -recursive examples
• bash scripts/check-docs.sh
• git diff --check release-security-checklist

Acceptance-test status

Acceptance tests were not run for this docs-only slice. They remain an opt-in release gate requiring TF_ACC=1, KERNEL_ACC=1, KERNEL_API_KEY, and KERNEL_PROJECT_ID.

Review gates

• deslop: clean, no accepted findings.
• incremental self-pr review: clean, no accepted findings.
• autoreview: clean, no accepted/actionable findings reported.
• dave-cheney-go-review: clean; docs-only diff does not change Go API, package, or test contracts, and it preserves the durable-only provider boundary.
• eblog-code-review: clean; improves release/deferred-work clarity without adding automation, runtime behavior, or slower feedback loops.
• final agreement pass: clean; docs-only scope matches v0 and defers v1 work explicitly.

Deferred v1 issues

• Consider opt-in force_destroy for kernel_browser_pool (architecture amendment) #24 force_destroy for kernel_browser_pool.
• Generate Terraform Plugin Framework schema/model via tfplugingen-framework codegen #25 Terraform Plugin Framework code generation.

Remaining manual release gates

• Merge the v0 stack onto the canonical branch.
• Run a real acceptance pass with credentials before tagging v0.
• Confirm the canonical branch and tag/release signing ownership before publishing.

---

Note

Low Risk
Documentation-only changes with no runtime, auth, or provider logic modifications.

Overview

README now links to that doc from the Architecture section. docs/release.md replaces stale “clean main” release wording with instructions to tag from the repo’s canonical post-merge branch and to confirm the default branch via gh repo view before release.

^{Reviewed by Cursor Bugbot for commit bf3e263. Bugbot is set up for automated code reviews on this repo. Configure here.}