First two adapters: real syncs from the owner's businesses #438

Part of #390. Needs the owner to say which two systems (a code host, CRM, billing or ticket system...) and where the credentials live; the crew cannot guess. @trevato: please name them in a comment, with one line each on what should end up in the forge.

Intent: two real adapters built on the adapter shape, each pulling one external system idempotently, proving the contract on live data.

Acceptance:

• [ ] owner names the two systems and the data wanted
• [ ] each adapter is its own app repository from the template, with tests against recorded fixtures (no network in bun test)
• [ ] each runs a preview pull against the real system with a read-only credential, and the run records counts
• [ ] what could not be mirrored is written in each README

Released from Later to use the week's subscription: Behind pace: 75% of the week left with 19% of its time gone, reset 2026-11-15 02:00 UTC, burning 0% an hour against 0.5% allowed; speeding up to 5 of 5 slots and releasing the next issue.

Parked by the crew: the run ended without a pull: declined: Issue #438 can't start until the owner answers it. Its first acceptance item is "owner names the two systems and the data wanted", and so far nobody has. The only comment is the automatic "Released fr

Parked by the crew: the run ended without a pull: declined: #438 is still waiting on the owner. Its first acceptance item is "owner names the two systems and the data wanted", and nobody has done that. The issue has only two comments: the automatic "Released f

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: Issue #438 can't start until the owner answers it. Its first acceptance item is "owner names the two systems and the data wanted", and so far nobody has. The only comment is the automatic "Released fr
2. the run ended without a pull: declined: #438 is still waiting on the owner. Its first acceptance item is "owner names the two systems and the data wanted", and nobody has done that. The issue has only two comments: the automatic "Released f

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.

Deferred by the planner: this needs the owner to name the two systems and where their read-only credentials live, and the crew can't guess that. Two runs declined for this reason. The adapter path it would use is built (schedule, recorded runs, API and MCP, the template), and #10125–#10128 and #10135 make it reachable on the page and in the terminal. This goes back behind the Later gate until the owner names the systems here.

Released from Later to use the week's subscription: Behind pace: 75% of the week left with 20% of its time gone, reset 2026-11-15 02:00 UTC, burning 0% an hour against 0.5% allowed; speeding up to 5 of 5 slots and releasing the next issue.

Parked by the crew: the run ended without a pull: declined: #438 is still waiting on the owner, so I didn't start it. Its first acceptance item is "owner names the two systems and the data wanted", and nobody has done that yet. I re-read every comment on the i

Parked by the crew: the run ended without a pull: declined: #438 is still waiting on the owner, so this run didn't start it. Its first acceptance item is "owner names the two systems and the data wanted". As of 11:20 UTC on 2026-11-09, nobody has done that. Ev

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: #438 is still waiting on the owner, so I didn't start it. Its first acceptance item is "owner names the two systems and the data wanted", and nobody has done that yet. I re-read every comment on the i
2. the run ended without a pull: declined: #438 is still waiting on the owner, so this run didn't start it. Its first acceptance item is "owner names the two systems and the data wanted". As of 11:20 UTC on 2026-11-09, nobody has done that. Ev

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.

Dropped by the planner: this duplicates #10085, which says what done looks like now (two adapters from examples/adapter-template, idempotent /pull, egress, replay test) and already waits behind the Later gate until the owner names the two systems. Two runs declined it for that reason; the crew cannot guess the systems. Owner: name them on #10085 and it is released.