[kriszyp]

⊙ Problem

Harper Pro's CLI and installer have printed "Harper" since 5.1.0-beta.1. The build's Perl rewrite still targets JavaScript files that core moved to TypeScript. Retargeting that blanket rewrite would also corrupt multipart boundaries and already-branded strings.

🤔 Restore the deliberate product name

5.0.x shipped "Harper Pro" intentionally (#11). Restore that output rather than keeping the accidental regression. Keep the existing v5.4 release target; an earlier backport remains a separate decision.

💡 Solution

Core reads the running package's productName through PRODUCT_NAME; harper#3078 is merged and included in Pro main. This PR inherits main's core revision unchanged, with no submodule change or companion dependency.

• Declare productName: "Harper Pro" in the distribution manifest.
• Remove the Perl rewrite and its destructive git restore . cleanup. Packaging no longer edits core sources.
• Clone-node imports PRODUCT_NAME for its start, install, existing-install, and fresh-clone messages.

🤔 Visible wording

The [notify] startup line and operations restart response also regain "Harper Pro", as in 5.0.x. Keep this intentional change and mention it in release notes. No documentation companion: command syntax, configuration, and API shapes are unchanged; productName belongs to the distribution.

✅ Verification

• Build, typecheck, required lint, changed-file Prettier, and shell syntax checks pass.
• Full unit gate: 1,958 passing, 2 pending. Branding regression tests cover compiled PRODUCT_NAME, the real CLI's help output, and manifest shadowing in npm pack.
• Consumer-install CI checks the actual installed release tarball's help output, after packaging rewrites the manifest. This is the release-artifact verification route.
• Clone-node integration suites pass, including failure recovery and interrupted-copy resume. The full integration run, with concurrency 2, hit the 1,200-second bound after cluster tests; no failed assertions were reported before timeout. This is incomplete full-suite coverage.

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

Release target: v5.4 — preserves the existing release decision for this branding restoration
Related PRs: #992 independent (changes build scripts, not productName), #1092 independent (replication checkpoints), #956 independent (merged table-drop fix), #981 overlaps (its merged packaging path is checked by the installed-artifact assertion), #998 independent (merged origin cursors), #1001 independent (merged core baseline; no pointer change here), #1065 independent (no core change here), #1062 independent (core sync already in base)
Complexity: easy
PR QA: skipped @ b1e281e — maintenance rebase only; existing CLI and installed-artifact tests cover branding

Deferred findings

• 2fa739f43dc247ac nit maintainability — unitTests/bin/productName.test.mjs — Branding checks depend on surrounding help prose — filed Reduce help-prose coupling in the Pro branding checks #1108

_{Review-Coverage: authored=codex; ran=gemini,claude,cursor-grok; adjudicated=domain; declined=cursor-composer,cursor-kimi,cursor-muse,muse; rounds=7; full=5 @ b1e281e}

_{Review-Attention: study ~14m (critical: cloneNode.ts; decisions: default-command-assertion, lifecycle-log-branding, branding-scope, release-target-vs-evidence; raised: earlier round at this SHA) @ b1e281e}

[gemini-code-assist]

Code Review

This pull request transitions the rebranding of the application to 'Harper Pro' from a build-time script replacement to a dynamic configuration using PRODUCT_NAME from packageUtils.js. It updates package.json, updates log messages in cloneNode.ts to use the dynamic product name, and introduces a new test suite to verify the branding. The review feedback correctly identifies a cross-platform compatibility issue in the test suite where calling execFileSync with npm will fail on Windows, and provides a robust solution to resolve the correct command name based on the platform.

[DavidCockerill]

Restoring the brand is the right call. 5.0.x shipped it on purpose, and a release-note line for the [notify] and restart text covers the visible change. One thing before approval: please get harper#3078 rebased and re-pin core (see inline), because nothing can be pushed here once it's approved. The tarball check from last round is still open and optional.

_{Findings drafted by claude-opus-5-5 via daivid-review, reviewed and posted by @DavidCockerill.}

[DavidCockerill]

Thanks for the help check on the installed tarball. That's where the brand went missing last time, so it's the right place to check it. The core pin still points at edce42a27 and would drop harper#3064 on merge; please rebase harper#3078 and re-pin core, then I'm happy to approve.

_{Findings drafted by claude-opus-5-5, worded by gpt-6-sol via daivid-review, reviewed and posted by @DavidCockerill.}

[DavidCockerill]

LGTM