[kriszyp]

📝 Summary

Documents Start and stop one isolated application without restarting the shared workers (harper#3339), which ships in v5.4.0:

• A new isolated application's first restart=true deploy starts only its own worker, and that worker is the release's canary.
• Dropping an isolated application stops its worker, with or without restart. drop_component removes the application's forks by default; keepBranches: true keeps them but fails with restart: true. A node that does not have the application restarts nothing.
• The drop response reports node, componentRemoved, workerStopped and branchesRemoved, with each peer's outcome in replicated.
• The per-PR preview recipe gets a one-call cleanup for clusters where every node runs v5.4.0. The per-node recipe stays for mixed-version clusters.

🔧 Changes

• reference/components/applications.md: Restarting and dropping, the Durable fork bullet, Removing a fork (default removal, when forks stay, keepBranches, the early-answer exception tracked in harper#3463), and drop_component's keepBranches field and response.
• reference/operations-api/operations.md: deploy restart scope, drop timing and scope, an isolated application's canary, and the canary unavailable row.
• learn/developers/deploying-from-ci.mdx: before/after notes, the per-node recipe marked as pre-v5.4.0, and Cleanup in one call on v5.4.0.
• learn/developers/multiple-applications.mdx: when a fork is removed.
• release-notes/v5-lincoln/5.4.md: Starting and Stopping One Isolated Application.

✅ Verification

• Each behavior claim was checked against harper#3339's code: dropApplication, dropPeerResults and the deploy restart scope in components/operations.js, the keepBranches validator, and harper-pro's peer answer path for the replicated shape.
• npm run format:write, npm run format:check, npm run build, npm run typecheck, npm run lint, npm run test:workflows, and npm run test:examples pass. The local cross-repository fixture comparison is skipped by default; there are no broken links or anchors.

Review follow-up on existing content

The rebase preserves the prior PR content. Its own review should qualify certification for linked directories, date the earlier preview restart cross-reference, and distinguish single-file restart from application shutdown. The one-call cleanup intentionally trusts the Operations API's completed response; worker-originated early answers use a different route. Release-tag and runtime verification remain deferred below.

Depends-on: HarperFast/harper#3339

_{🤖 Generated by Anthropic Claude and OpenAI Codex; posted via @kriszyp.}

Related PRs: #751 overlaps, #671 overlaps
Complexity: easy

Deferred findings

• c8efa0c731826211 nit documentation — reference/components/applications.md — v5.4.0 behavior claims not verified against the shipped v5.4.0 tag — NOT FILED

_{Review-Coverage: authored=codex; ran=gemini,cursor-composer,cursor-grok; late=cursor-grok:adjudicated; adjudicated=domain; declined=muse,claude; rounds=6; full=1 @ 88db998}

_{Review-Attention: read ~3m (decisions: cleanup-evidence; raised: degraded review) @ 88db998}

[gemini-code-assist]

Code Review

This pull request updates the documentation across several files to reflect the new behaviors introduced in version 5.4.0, specifically regarding isolated applications, worker restarts, branched database forks, and the drop_component API. The feedback recommends avoiding the use of the <VersionBadge> component at the start of a paragraph in running prose within reference/components/applications.md to maintain a clean reading flow.

[gemini-code-assist]

Avoid using the <VersionBadge> component at the start of a paragraph in running prose. Instead, use plain text (e.g., 'As of v5.4.0') to maintain a clean and consistent reading flow, reserving <VersionBadge> for standalone placement directly under headings.

Suggested change

	<VersionBadge version="v5.4.0" />
	The response reports this node's outcome, and each peer's in `replicated`:
	As of v5.4.0, the response reports this node's outcome, and each peer's in `replicated`:

References

1. Avoid using the component at the start of a paragraph in running prose. Use plain text (e.g., 'As of vX.Y.Z') instead, reserving for standalone placement after headings.

[github-actions]

🚀 Preview Deployment

Your preview deployment is ready!

🔗 Preview URL: https://preview.harper-documentation.harperfabric.com/pr-750

This preview will update automatically when you push new commits.

[github-actions]

🚀 Preview Deployment

Your preview deployment is ready!

🔗 Preview URL: https://preview.harper-documentation.harperfabric.com/pr-750

This preview will update automatically when you push new commits.