Corrects setup path to script/setup

The merge-upstream script and skill referenced a top-level ./setup,
but this repo's setup entrypoint is script/setup (no top-level setup),
so the command failed verbatim. Addresses PR #473 review.

Author: myabc

.claude/skills/syncing-primer-fork/SKILL.md

@@ -75,16 +75,16 @@ On macOS pass `gsed` as the 2nd arg (the script auto-detects, but be explicit).
 The script: fetches upstream, builds `bump/primer-upstream-ref` (reset to the
 SHA) and `bump/primer-upstream` (from `origin/main`), merges with `--no-commit`,
 rescopes `@primer/view-components` → `@openproject/primer-view-components` in
-`.changeset/*.md`, then runs `./setup`, stages, and stops at an interactive
+`.changeset/*.md`, then runs `script/setup`, stages, and stops at an interactive
 `git commit`.
 
-**The merge step is conflict-tolerant (`|| true`), but the later `./setup` is
-not.** `./setup` runs `bundle install` and `npm install`; when a `Gemfile`,
+**The merge step is conflict-tolerant (`|| true`), but the later `script/setup` is
+not.** `script/setup` runs `bundle install` and `npm install`; when a `Gemfile`,
 `*.gemspec`, or `package.json` conflicts (almost always — fork scope/version vs
 upstream), the conflict markers make those installs fail → `set -e` aborts the
 script *before* stage/commit. That's expected: the changeset rescope has already
 run, and you're left mid-merge. **Resolve conflicts (step 3) first, then run
-`./setup` yourself**, then stage and commit.
+`script/setup` yourself**, then stage and commit.
 
 ### 3. Resolve conflicts by package manager
 
@@ -98,16 +98,16 @@ automatically (fork wins). For the rest:
 | `package.json` (root or `demo/`) | **npm** | Resolve `package.json`, then `npm install` in that dir to regenerate `package-lock.json` |
 | component source, `.changeset/*.md`, `previews/`, docs | — | Resolve normally; keep upstream's new components |
 
-`./setup` does both (`bundle install` + `npm install`, root and `demo/`, then
-`rake docs:build`), so once conflicts are resolved a single `./setup` refreshes
+`script/setup` does both (`bundle install` + `npm install`, root and `demo/`, then
+`rake docs:build`), so once conflicts are resolved a single `script/setup` refreshes
 every lockfile and the generated docs. The mirror repo (octicons) instead uses
 yarn at the root plus npm for `octicons_angular`.
 
 After resolving, re-stage, run setup, and commit:
 
 ```bash
 git add -A
-./setup             # regenerates lockfiles + docs from the merged sources
+script/setup             # regenerates lockfiles + docs from the merged sources
 git add -A
 git commit          # finishes the deferred merge commit
 ```
@@ -122,7 +122,7 @@ for vp in $(git log upstream/main --grep="Release tracking" --not main --reverse
 done
 script/merge-upstream <TARGET> gsed
 # resolve conflicts: Gemfile→bundle install, package.json→npm install, others normal
-./setup && git add -A && git commit
+script/setup && git add -A && git commit
 ```
 
 ## Common Mistakes
@@ -160,7 +160,7 @@ differences to account for:
   `Version Packages` (octicons).
 - **Package managers / lockfiles:** view_components uses Ruby Bundler
   (`Gemfile.lock`, `demo/Gemfile.lock`) plus npm (`package-lock.json`,
-  `demo/package-lock.json`), driven by `./setup`; octicons uses yarn at the root
+  `demo/package-lock.json`), driven by `script/setup`; octicons uses yarn at the root
   plus npm for `octicons_angular`.
 - **npm scope:** `@primer/view-components` → `@openproject/primer-view-components`
   (octicons: `@primer/octicons` → `@openproject/octicons`).

script/merge-upstream

@@ -41,7 +41,7 @@ find .changeset/ -name "*.md" -exec "${SED_INPLACE[@]}" \
   's/@primer\/view-components\([^-]\)/@openproject\/primer-view-components\1/g' {} +
 
 # Reinstall deps and rebuild generated docs from the merged sources.
-./setup
+script/setup
 
 git add Gemfile.lock demo/Gemfile.lock package-lock.json demo/package-lock.json .changeset/