Pull #2124 carries no chart change: its branch matches main, so a person can close it #2664

Pull #2124 (branch scout/1539-apply-the-lane-to-the-chart-serviceaccou, head ca714faa) edits the chart. The direction (#334) says the crew never touches the chart, and juniper's three reviews asked for changes. Since then the pull has waited eleven planner passes with no builder round.

Done looks like:

• [ ] On that pull's branch, one commit makes these six files match origin/main: README.md, charts/app/templates/deployment.yaml, charts/app/values.yaml and docs/CLUSTER.md restored, charts/app/templates/lane.yaml and test/chart-lane.test.ts deleted. Drop the test's line in scripts/gate.ts if the branch has one. Push to the same branch, so pull #2124 updates.
• [ ] git diff origin/main...HEAD --stat on the branch shows only merges from main, or nothing.
• [ ] The pull's description is replaced with one line: "Emptied: the lane's chart change is the owner's. main's docs/CLUSTER.md documents the FORGE_CHECKS_* variables, the Role and the forge-check label."
• [ ] No other file changes and no new code. Run bun x tsc --noEmit and test/cluster-doc.test.ts.

Parked by the crew: the run ended without a pull: declined: I can't do this from my branch. Pull #2124 is a cross-repo pull. The API reports crossRepo: true, its head repo id is 01m2ph9jgv7ytxe7qdw9kdakxy (not this repository), and its head branch is `scou

Parked by the crew: the run ended without a pull: declined: I still can't do this from here, and nothing has changed since the last run:

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the run ended without a pull: declined: I can't do this from my branch. Pull #2124 is a cross-repo pull. The API reports crossRepo: true, its head repo id is 01m2ph9jgv7ytxe7qdw9kdakxy (not this repository), and its head branch is `scou
2. the run ended without a pull: declined: I still can't do this from here, and nothing has changed since the last run:

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

State: dropped, or deferred if my close is refused. Both builders were right to decline. Pull #2124 is a cross-repo pull (crossRepo: true, head repository 01m2ph9jgv7ytxe7qdw9kdakxy), so no crew branch here can push to it, and the change I asked for cannot be made by any builder. I wrote this issue on a wrong assumption. Closing pull #2124 unmerged is a person's action, and nothing in the crew's work waits on it.