[kriszyp]

⊙ Problem

Document stuck base copies, purge-bound retention copies and unnamed origins for 5.4 says three replication changes first ship in v5.4.0. They are also coming to the 5.3 line, through Stop forcing base copies that never finish and Record each transaction log's purge bound. A 5.3 operator reading these pages would be told stuckCopy is not available to them.

🤔 Is it right to say v5.3.6 before the release exists?

Yes, in a draft. Do not merge until both code PRs merge and the v5.3.6 tag has the code (git show v5.3.6:replication/copyStall.ts). If it ships later, change these badges.

💡 Solution

• In overview.md, the purge-bound rule and derived names for unnamed origins now read as available from v5.3.6. So does stuckCopy in clustering.md.
• refused stays v5.4.0. On 5.3, state is only retrying or held, and the refused entry has its own badge.
• operating-replication.mdx matches: the idle-database sentence and the stuckCopy field.
• The 5.4 notes name the 5.3.6 backport and its exception. Their upgrade note now applies only when upgrading from before 5.3.6, since both lines store the same purge record.

🤔 Should 5.3.md also warn about the extra copy on upgrade?

Left out. That page sends patch notes to the GitHub releases page, and the reference covers the case. It would be one bullet to add.

⚖️ Alternatives

• Two badges per heading (v5.3.6 and v5.4.0): both would read "Added in", which contradicts itself. Backports here use the lowest version.

✅ Verification

• Checked each claim in the latest backport PR commits: STATE_NAMES has only retrying and held; the attempt limit, hold bounds, 60-second quiet period, log lines, 64-name cap and naming match the pages.
• npm run build, format:check, lint, typecheck and test:examples pass.
• Not run: the 5.3.6 to 5.4.0 upgrade. Reading both PRs showed the same record.

Refs HarperFast/harper-pro#1262

_{🤖 Generated by Claude Opus 5.5 (Claude Code); posted via @kriszyp.}

Related PRs: #788 overlaps (moves these reference pages to the code repos; its sources need the same version split), #791 overlaps (wrote the v5.4.0 text this corrects)
Complexity: easy

Origin — the dispatch brief this PR was written from

Document the 5.3 backport of base-copy liveness

Documentation for the base-copy liveness behavior was added by documentation#791 with version badges saying it first ships in v5.4.0. The same behavior is being backported to the 5.3 line by harper-pro#1262 and harper#4014, so it is expected in the next 5.3 patch release (5.3.6).

Update the badges and any "Before v5.4" wording in the pages #791 touched so they are accurate for both lines: the purge-bound retention copy, derived names for unnamed origins, and the cluster_status stuckCopy field exist on 5.3 from that patch.

One real difference to state: on 5.3 stuckCopy has only the states retrying and held. The refused state and the owner-refusal behavior need declarative sharding, which is 5.4 only.

Hold merging until harper-pro#1262 merges and the patch version is confirmed. Link: HarperFast/harper-pro#1262

_{Dispatch: task docs-harper-pro-1262 · queued by task:harper-pro-1249-v53-port · ran by claude/opus/high · worker kzyp-xps-1}

_{Ready-For-Promotion: 3dbf213 urgency=normal late=none}

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

_{Review-Attention: skim ~2m (decisions: badge-split-inline, backport-note-location) @ 3dbf213}

[github-actions]

🚀 Preview Deployment

Your preview deployment is ready!

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

This preview will update automatically when you push new commits.

[github-actions]

🧹 Preview Cleanup

The preview deployment for this PR has been removed.