Point the project-gardener skill at the organization project

[jhgaylor]

.agents/skills/fountain-project-gardener/references/project-policy.md names users/BinaryBourbon/projects/1. The board has been copied to github.com/orgs/managoat/projects/1 with its fields, views and all 237 items.

Needs: the policy file and the skill description updated to the org project, and a decision on the old board — close it as moved, or leave it read-only as history. Do not delete it while anything still links to it.

[jhgaylor]

PR #1825 points the policy file at orgs/managoat/projects/1. The decision half is still open, and there is a fact that changes it.

The old board is not sitting still. Both boards auto-added items today:

	users/BinaryBourbon/projects/1	orgs/managoat/projects/1
Items	247	249
#1822, #1823	present	absent
PRs #1820, #1745, #1754, #1760	absent	present

New issues are landing on the old board and not on the new one. Recent pull requests landed on the new one. So "leave it read-only as history" is not what it is currently doing, and the org board is already missing the two newest issues.

Two things to fix, not one:

1. Turn off the old board's auto-add, then close it as moved or leave it read-only. Either is fine once it stops capturing.
2. Backfill whatever it captured after the copy at 11:29 today. Deprecate @agentshit/fountain-sdk with a pointer to the new name #1822 and Docs use example skill sources that do not exist #1823 are the two I found.

Both are Projects settings, so they need a signed-in browser or a token carrying the project scope. On this machine only the BinaryBourbon gh account has it; jhgaylor does not.

[jhgaylor]

Backfilled. The org board is now a superset of the old one: nothing on users/BinaryBourbon/projects/1 is missing from orgs/managoat/projects/1.

old board: 247 items
org board: 259 items
on old, missing from org: (none)

It was two items, #1822 and #1823. The board's own workflows set Status on add — Triage for the open one, Done for the closed one — so no fields needed setting by hand.

One correction to what I said earlier. The old board looks like it has already stopped capturing. It took #1822 and #1823 at 12:06 and nothing since; #1828, opened around 12:44, went to the org board only, as did every PR merged this afternoon. So the drift I reported was a window, not an ongoing leak. Still worth confirming the auto-add is actually off in that board's settings rather than merely quiet — I cannot read a Projects workflow's enabled state from the API, only infer it from what arrives.

Once you have confirmed that, the remaining half of this issue is the disposition: close the old board as moved, or leave it read-only as history. Either is safe now that the contents match.

[jhgaylor]

Auto-add on users/BinaryBourbon/projects/1 is confirmed off — the workflow is disabled with its managoat/fountain / is:issue,pr is:issue is:open filter intact but inert.

Verified by what arrives rather than by the setting alone. The old board is frozen at 247 items while the org board has grown to 291 since, and nothing on the old board is missing from the new one:

old board: 247 items
org board: 291 items
on old, missing from org: (none)

So the two halves of this issue are done: the gardener points at the org board (#1825), and the drift is closed and cannot reopen.

What is left is the disposition — close the old board as moved, or leave it read-only as history. Either is safe now that the contents match and nothing is being added.

[jhgaylor]

Both halves done.

The gardener points at the org board — #1825 rewrote references/project-policy.md to orgs/managoat/projects/1, recorded the old board as history that must not be mutated, and replaced the identity note that named a specific signed-in account.

The old board is closed as moved.

old  users/BinaryBourbon/projects/1   closed: true   247 items
new  orgs/managoat/projects/1         closed: false  291 items

It carries a description saying where it went: "Moved to orgs/managoat/projects/1 on 2026-09-10. Read-only history; do not add or edit." Closing a Project archives it rather than deleting it — all 247 items stay readable at the same URL and it can be reopened, so nothing is lost.

Its auto-add was disabled first, and the freeze was verified by what arrives rather than by the setting: the old board stayed at 247 while the org board grew to 291, with nothing on the old one missing from the new. The two issues it had captured, #1822 and #1823, were backfilled and the board's own workflows set their Status correctly on add (Triage for the open one, Done for the closed one).

One thing worth keeping in mind for the gardener: the policy file still describes the old board as surviving with its auto-add live, which was true when #1825 was written and is no longer. Not worth a PR on its own; it will be right the next time that file is edited.