Update PRD for Go-native Zero direction

[Vasanthdev2004]

Summary

• update the main PRD from TypeScript/Bun assumptions to a Go-native agent core
• switch the planned TUI direction from Ink/React to Bubble Tea/Lip Gloss
• keep npm as a distribution wrapper for native platform binaries
• align the work-split PRD commands and DoD with Go build/test expectations

Validation

• git diff --check

No code was changed, so Go/Bun build and test commands were not run for this docs-only PR.

Summary by CodeRabbit

• Documentation
  • Updated product roadmap and technical architecture to a Go-native core with an npm wrapper/launcher and single-binary distribution.
  • TUI surface standardized to Bubble Tea; milestones and ownerships rebalanced to reflect Go-first baseline.
  • Tool parameter schemas aligned to Go-typed → JSON Schema mappings; model/tool examples converted to Go-style definitions.
  • CI/build and definition-of-done updated to Go-first build/test criteria with npm-wrapper smoke checks.

[github-actions]

Zero automated PR review

Verdict: No blockers found

Blockers

• None found.

Validation

• [pass] Diff hygiene: git diff --check
• [pass] Typecheck: bun run typecheck
• [pass] Tests: bun run test
• [pass] Build: bun run build
• [pass] Smoke build: bun run smoke:build

Scope

Head: dacae01bceae
Changed files (2): docs/PRD.md, docs/WORK_SPLIT_PRD.md

This deterministic review checks validation status and basic diff hygiene. A human reviewer still owns product judgment and design quality.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8976242e-94b8-469d-94c2-2d2fb3df26c5

📥 Commits

Reviewing files that changed from the base of the PR and between 9f8515b and dacae01.

📒 Files selected for processing (1)

• docs/WORK_SPLIT_PRD.md

✅ Files skipped from review due to trivial changes (1)

• docs/WORK_SPLIT_PRD.md

---

Walkthrough

This PR updates two product requirement documents to reflect a platform architecture migration: the codebase shifts from a TypeScript/Bun foundation to a Go-native core with an npm distribution wrapper. The TUI library changes from Ink to Bubble Tea + Lip Gloss, tool schema validation moves from Zod to JSON Schema, type examples transition from TypeScript interfaces to Go structs, and milestone M0/M1/M2 deliverables and acceptance criteria are updated to match Go build/test commands and CI expectations.

Changes

Go-Native Platform Architecture Migration

Layer / File(s)	Summary
Core platform vision and architecture docs/PRD.md	High-level PRD statements (stack line, vision tagline, distribution strategy, and "Why this will work") updated to describe Go-native core with npm installer/launcher wrapper.
Terminal surface (TUI) requirements and implementation docs/PRD.md	TUI technology updated from Ink to Bubble Tea + Lip Gloss; streaming behavior model changed from Ink <Static> component to append-only transcript with live tail; risk R3 mitigation and open decision #1 reworded to reflect Bubble Tea choice.
Tool contract and schema definitions docs/PRD.md	Tool parameter schema validation approach updated from Zod to Go-typed schemas with JSON Schema mapping; Model Registry and Tool Contract type examples rewritten from TypeScript interfaces to Go struct/interface-style definitions with JSON field shapes and types.
M0 milestone definition and acceptance criteria docs/PRD.md, docs/WORK_SPLIT_PRD.md	Milestone M0 deliverables replace Bun/TypeScript setup with Go module setup and basic Bubble Tea TUI; M0 CI/build criteria changed to go test ./... and go build ./cmd/zero plus npm wrapper smoke checks; team ownership and workload bullets updated to Bubble Tea TUI and JSON Schema validation.
M1/M2 milestones and PR Definition of Done docs/WORK_SPLIT_PRD.md	M1 build spike updated from Bun to Go cross-compilation; M1 done criteria and M2 zero doctor checklist adapted to Go commands and general binary/config/provider/connectivity/model checks; PR-level Definition of Done replaces Bun test/typecheck/build requirements with Go test/build commands and npm wrapper checks.

---

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Update PRD for Go-native Zero direction' accurately reflects the main change: updating documentation to describe a Go-native core instead of TypeScript/Bun.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/go-prd-refresh

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (1)

docs/WORK_SPLIT_PRD.md (1)

524-525: ⚡ Quick win

Clarify when Go DoD criteria apply.

The phrasing "when Go code exists" and "when the Go entrypoint exists" is ambiguous. Does it mean "when the PR changes Go code" or "when Go code exists in the repository"? For a Go migration, consider:

• "when PR changes Go code" or
• "unless the PR is docs-only"

This makes it clearer when developers must satisfy the Go test/build requirements.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/WORK_SPLIT_PRD.md` around lines 524 - 525, Update the DoD wording to
remove ambiguity: replace the lines containing "`go test ./...` passes when Go
code exists" and "`go build ./cmd/zero` passes when the Go entrypoint exists"
with explicit criteria such as "`go test ./...` must pass when the PR modifies
any Go code (or add a note: not required for docs-only PRs)" and "`go build
./cmd/zero` must pass when the PR modifies the Go entrypoint (or not required
for docs-only PRs)"; ensure both checklist items mention the exceptions (e.g.,
docs-only) and use "PR modifies" phrasing so it's clear the checks apply only
when the PR changes Go code or the entrypoint.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/WORK_SPLIT_PRD.md`:
- Line 89: Replace the vague phrase "npm wrapper smoke checks" with a short
concrete checklist that developers can implement: verify package.json exists and
has expected name/version, run npm ci to confirm install succeeds, ensure the
wrapper binary/script (npm, npx, or project wrapper) is executable and resolves
to the project's node_modules/.bin entry, run a simple wrapper command (e.g.,
wrapper --version or wrapper --help) and assert exit code 0 and matching
version, and run a basic smoke command from package.json (e.g., npm run build or
a designated "smoke" script) to ensure the install+invoke flow works; update all
three occurrences to reference this checklist so implementers know exactly what
to test.
- Line 98: The acceptance criterion for the Go entrypoint is ambiguous—update
the sentence containing "go build ./cmd/zero" to a single clear requirement:
either require the build to pass for M0 by changing it to "`go build ./cmd/zero`
passes" or mark the entrypoint as optional for M0 by changing it to "Go
entrypoint scaffold exists and builds, or M0 explicitly defers the passing Go
entrypoint to M1"; update the phrase in the document to one of these two precise
options so reviewers know whether a passing build is required in M0 (reference
the exact text `go build ./cmd/zero` in the line to modify).

---

Nitpick comments:
In `@docs/WORK_SPLIT_PRD.md`:
- Around line 524-525: Update the DoD wording to remove ambiguity: replace the
lines containing "`go test ./...` passes when Go code exists" and "`go build
./cmd/zero` passes when the Go entrypoint exists" with explicit criteria such as
"`go test ./...` must pass when the PR modifies any Go code (or add a note: not
required for docs-only PRs)" and "`go build ./cmd/zero` must pass when the PR
modifies the Go entrypoint (or not required for docs-only PRs)"; ensure both
checklist items mention the exceptions (e.g., docs-only) and use "PR modifies"
phrasing so it's clear the checks apply only when the PR changes Go code or the
entrypoint.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 4e911d99-4ebb-428f-9dfd-404f90d9fec3

📥 Commits

Reviewing files that changed from the base of the PR and between 10f749e and 291d5da.

📒 Files selected for processing (2)

• docs/PRD.md
• docs/WORK_SPLIT_PRD.md

[gnanam1990]

Finding:

• [P1] docs/WORK_SPLIT_PRD.md still treats old PR #6 as the M0 baseline, while this PR changes M0 to a Go module, Bubble Tea TUI, go test ./..., and go build ./cmd/zero. It also keeps "Merge or close PR #6" as the first next step. Since the current repo has no go.mod or cmd/zero, and PR #6 was the earlier TS/Bun baseline, this would tell the team to skip the actual Go M0 migration and start M1 too early. Please update this section to say M0 must be reset/rebuilt for Go first, then list the Go foundation PRs before M1 work starts.

[gnanam1990]

Re-reviewed latest head . The M0 planning blocker is fixed: the WorkSplit PRD now treats the earlier TS/Bun baseline as historical, resets M0 for the Go migration, lists Go foundation PRs, and gates M1 until those Go M0 PRs merge. Checks are green and I do not see remaining blockers.