docs(release): archive cutover is 0.0.44; runbook and client copy follow

[Jacksondr5]

0.0.43 went out through the old npm pipeline before #262 merged, so 0.0.44 is J5's first release-archive release. The docs, the J5 Release gate and some messages still named 0.0.43 as the cutover, the release runbook still described npm publishing, and two client-runtime messages still said "T3 Code".

• Cutover: the last npm version is now 0.0.43 and the first archive release 0.0.44, in the J5 Release resolve gate and release notes, FORK.md cases 15, 40 and 41, the install, updating, background-service and migration guides, the install.sh error, and code comments. The only version comparison in code is the release gate (patch < 44). Other version strings are unrelated provider ranges or test fixtures, and are unchanged.
• Runbook: the GitHub Actions section of docs/j5/runbooks/macos-packaging.md now describes the archive flow: bump, push j5/release-<version>, J5 Signed macOS Build, dispatch J5 Release with the run ID, what gets published, and the resolve rules. It no longer describes npm trusted publishing.
• Version on j5/main: the 0.0.44 bump (e359d62346) only lived on j5/release-0.0.44, so j5/main still reported 0.0.43. This PR carries that bump, and the runbook gains a step to bring each release's bump back to j5/main. README.md also names 0.0.43 as the last npm release.
• Branding: compatibility.ts and pullRequestDiffHttp.ts use product-neutral wording ("Update the server on …", "quit and reopen the app"), and both are recorded in BRANDING.md's audit sites.

Verified: tests for resolver, pullRequestDiffHttp, update, bootService and install (75 passed), tsc clean for client-runtime, server and scripts, format clean, bash -n scripts/install.sh, and the workflow YAML parses and its script passes node --check.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated release and migration guidance: archive-based releases begin at version 0.0.44, and npm-era versions through 0.0.43 may require migration.
  • Revised packaging and release instructions to describe publishing signed release archives instead of npm packages.
• Bug Fixes
  • Updated compatibility and credential error messages to use product-neutral wording when guiding users to update the server or reopen the app.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: Jacksondr5/j5code/.coderabbit.yaml

Review profile: CHILL

Plan: Essentials

Run ID: 840e64ec-15b1-4309-8d8d-13fd8b98abe3

📥 Commits

Reviewing files that changed from the base of the PR and between a664da8 and 5749a13.

📒 Files selected for processing (6)

• README.md
• apps/desktop/package.json
• apps/server/package.json
• apps/web/package.json
• docs/j5/runbooks/macos-packaging.md
• packages/contracts/package.json

Included review availability: This review used your included allowance. 3 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.

---

📝 Walkthrough

Walkthrough

The release workflow and documentation set 0.0.44 as the first release-archive version and identify versions through 0.0.43 as npm-era. Legacy-service references use the updated range. Shared-client error messages use product-neutral wording.

Changes

Release archive transition

Layer / File(s)	Summary
Release archive boundary .github/workflows/j5-release.yml, docs/j5/runbooks/macos-packaging.md, apps/desktop/package.json, apps/server/package.json, apps/web/package.json, packages/contracts/package.json, scripts/lib/j5-branding.ts, FORK.md	The workflow and runbook set 0.0.44 as the minimum release-archive version and describe the release process. Package versions, release records, and the package-history comment reflect the updated boundary.
Migration thresholds and instructions .github/workflows/j5-release.yml, README.md, FORK.md, docs/user/install.md, docs/user/migrating-to-release-archives.md, docs/user/updating.md, scripts/install.sh	Migration guidance and installer messaging identify npm-era versions through 0.0.43 and use 0.0.44 for archive-version checks.
Legacy service version references apps/server/src/cli/update.ts, apps/server/src/cli/update.test.ts, apps/server/src/cloud/bootService.ts, apps/server/src/cloud/bootService.test.ts, apps/server/src/cloud/j5/legacyBootService.ts, docs/user/background-service.md, FORK.md	Comments and documentation identify versions through 0.0.43 as using legacy service names. The update example uses version 0.0.44.

Product-neutral client messages

Layer / File(s)	Summary
Shared-client error wording packages/client-runtime/src/connection/compatibility.ts, packages/client-runtime/src/connection/resolver.test.ts, packages/client-runtime/src/state/pullRequestDiffHttp.ts, packages/client-runtime/src/state/pullRequestDiffHttp.test.ts, BRANDING.md	Compatibility and credential error messages use “the server” and “the app” instead of naming T3 Code. Tests and the copy audit reflect the wording.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Suggested reviewers: juliusmarminge

Merge Risk: ⚪ Minimal · up to 5749a

No current release-boundary or client-behavior issue warrants blocking merge. The 0.0.43 archive example is clearly a local test record, not a claim of a public release.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 11 files. (6 skipped: …	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title clearly summarizes the main changes: the 0.0.44 archive cutover, the release runbook update, and the client-runtime wording changes.
Description check	✅ Passed	The description clearly explains the cutover, runbook changes, version bump, branding updates, and verification results. It does not use the template headings or checklist, but it provides the require…

Full details: Docstring Coverage

Explanation

Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 11 files. (6 skipped: 6 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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