docs(SUP-1772): plan jarvOS packaging roadmap

[levineam]

Thinking Path

1. SUP-1772 needs to turn SUP-1765's packaging research into an actionable roadmap, not another broad product note.
2. The safest first artifact is a durable public architecture doc because the work is planning-scoped and should be reusable by future contributors.
3. The roadmap should preserve the key guardrail from SUP-1765: jarvOS is local middleware and OpenClaw is one runtime adapter.
4. Install profiles should make optional subsystems explicit instead of letting Paperclip, GBrain, Obsidian, or lossless-claw look like hard dependencies.
5. The version plan should be sequenced by user confidence: packaging clarity, CLI/doctor, local-openclaw, full profile, clean-machine confidence.
6. Follow-up issues should be split by execution boundary so implementation can happen without mixing docs, CLI migration, runtime setup, and full-profile health checks.

What Changed

• Added docs/architecture/packaging-and-install-profiles.md.
• Defined required jarvOS core dependencies versus optional profile dependencies.
• Specified install profiles: minimal, local-openclaw, codex, claude, hermes, and full.
• Planned the staged roadmap for v0.2, v0.3, v0.4, v0.5, and v1.0.
• Sized the biggest implementation changes and identified execution-ready follow-up slices.
• Referenced SUP-1765 as the source research and kept the public/private boundary explicit.

Verification

• markdownlint '**/*.md' --ignore 'node_modules/**' --ignore '.github/**' --config .markdownlint.json passed.
• npm test passed.
• npm run release:check:candidate reached smoke-test pass but reported the pre-existing release-tag condition: v0.1.0 already exists.
• git diff --name-only origin/main..HEAD contains only docs/architecture/packaging-and-install-profiles.md.

Risks

• Low risk: documentation only.
• This PR intentionally does not implement CLI/profile manifests yet; the doc identifies those as separate execution slices.
• PR docs(SUP-1768): align jarvOS category framing #45 may add a related product-category doc. This PR adds a separate packaging roadmap file and does not touch overlapping files.

Model Used

OpenAI GPT-5 Codex, Paperclip engineering heartbeat with local repo verification and GitHub PR creation.

Checklist

• Changes are scoped to SUP-1772.
• SUP-1765 research is referenced.
• Roadmap includes v0.2, v0.3, v0.4, v0.5, and v1.0.
• Install profiles are explicit.
• Follow-up implementation slices are identified without implementing them in this PR.
• No secrets, private notes, or local machine config were added.

Summary by CodeRabbit

Release Notes

• Documentation
  • Added comprehensive guide for jarvOS packaging and installation profiles, covering available installation options, core system requirements, command-line interface for configuration and management, and system verification procedures.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds comprehensive architectural documentation for jarvOS packaging and install profiles. The document establishes packaging philosophy, enumerates six install profiles with doctor checks, defines a machine-readable manifest contract, and provides a concrete versioned roadmap (v0.2–v1.0) with execution-ready follow-up issues and adoption constraints.

Changes

Packaging and Install Profiles Roadmap

Layer / File(s)	Summary
Packaging Philosophy and Required Core docs/architecture/packaging-and-install-profiles.md	Document front-matter and metadata; jarvOS packaging/install philosophy with product boundary framing; Required Core scope definition and baseline generated files that all profiles depend on.
Install Profiles and CLI Shape docs/architecture/packaging-and-install-profiles.md	Install profile catalog (minimal, local-openclaw, codex, claude, hermes, full) with explicit includes/excludes and per-profile doctor checks; expected CLI usage shape and command rename from jarvos-bootstrap to jarvos.
Profile Manifest Contract and Execution Roadmap docs/architecture/packaging-and-install-profiles.md	Machine-readable profile manifest contract with recommended directory/file layout and sample JSON schema; versioned v0.2–v1.0 execution roadmap with goals, deliverables, and Done-when acceptance criteria.
Implementation Plan and Adoption Constraints docs/architecture/packaging-and-install-profiles.md	Biggest Implementation Changes table with size and risk assessment; execution-ready follow-up issues with scope and completion criteria; explicit out-of-scope constraints; reusable adoption pattern and checklist.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Suggested labels

jarvis-managed

Poem

🐰 A roadmap drawn with care so clear,
Six profiles waiting, never fear,
From core to doctor, checks aligned,
A packaging pattern well-designed!

🚥 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 'docs(SUP-1772): plan jarvOS packaging roadmap' clearly and specifically describes the main change: adding documentation that plans the jarvOS packaging roadmap.
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 SUP-1772/jarvos-packaging-roadmap

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 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/architecture/packaging-and-install-profiles.md`:
- Line 138: The sentence "Purpose: expose jarvOS context to Claude Desktop or
Claude Code style clients." should use compound-modifier hyphenation; update it
to read "Purpose: expose jarvOS context to Claude Desktop or Claude Code-style
clients." to hyphenate "Code-style" as a compound modifier (locate the exact
string "Purpose: expose jarvOS context to Claude Desktop or Claude Code style
clients." in the document and replace it).

🪄 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 237ebd02-d372-4947-b8cc-9ba46494a950

📥 Commits

Reviewing files that changed from the base of the PR and between 4e46ff7 and d418272.

📒 Files selected for processing (1)

• docs/architecture/packaging-and-install-profiles.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use compound-modifier hyphenation for “Code-style”.

“Claude Code-style clients” reads more cleanly and avoids grammar lint noise.

Suggested patch

-Purpose: expose jarvOS context to Claude Desktop or Claude Code style clients.
+Purpose: expose jarvOS context to Claude Desktop or Claude Code-style clients.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Purpose: expose jarvOS context to Claude Desktop or Claude Code style clients.
	Purpose: expose jarvOS context to Claude Desktop or Claude Code-style clients.

🧰 Tools

🪛 LanguageTool

[grammar] ~138-~138: Use a hyphen to join words.
Context: ...context to Claude Desktop or Claude Code style clients. Includes: - everything ...

(QB_NEW_EN_HYPHEN)

🤖 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/architecture/packaging-and-install-profiles.md` at line 138, The
sentence "Purpose: expose jarvOS context to Claude Desktop or Claude Code style
clients." should use compound-modifier hyphenation; update it to read "Purpose:
expose jarvOS context to Claude Desktop or Claude Code-style clients." to
hyphenate "Code-style" as a compound modifier (locate the exact string "Purpose:
expose jarvOS context to Claude Desktop or Claude Code style clients." in the
document and replace it).