Skip to content

Bridge 2b: contributions, corrections and the setup checklist - #150

Merged
KodeStar merged 16 commits into
mainfrom
docs/bridge-2b
Oct 20, 2026
Merged

KodeStar merged 16 commits into
mainfrom
docs/bridge-2b

Conversation

@KodeStar

@KodeStar KodeStar commented Oct 20, 2026 •

Copy link
Copy Markdown
Owner

Bridge Phase 2b docs: the Bridge Accounts page (GitHub sign-in, agent credential), the setup checklist, sharing a book with the community, suggesting corrections (the dialog, its checks, what is filed and how duplicates are guarded), the contributions module, park and notification texts (sign-in and credential changes resume, budget raises and restarts), the meta.correct and sidecars.contribute API, and the developer pages for the Bridge contributions flow.

Build: npm run build green. Reviewed with /simplify and /code-review max against the code on every round; every quoted string checked against the server and Bridge branches. No screenshot of the corrections dialog exists in the manifest, so none were regenerated.

Pairs with KodeStar/audiosilo-meta#2703, KodeStar/audiosilo-meta-community#428, KodeStar/audiosilo-server#157, KodeStar/audiosilo-frontend#118, KodeStar/audiosilo-bridge#6, #150, KodeStar/audiosilo#72.

…ions

User Guide: Running a Bridge follows the setup checklist's order; new Bridge
accounts and Contributing from your server pages; the console's Setup card,
Share with the community, Suggest corrections and module-off behaviour.
Developer docs: the new Contributions page, accepts/setup negotiation, the
module-owned job kinds and their codes, the agent credential hand-off, GitHub
configuration, the API reference, and meta's correction-batch form and
App-filed intake. Screenshots: the new admin/bridge-setup.png, and the Bridge
shots recaptured with a setup checklist and the Contributions module on.
…ng at most once, per-credential saved time, live monthly budget
…s checked in the console, parked descriptions woken by a page change
…me on restart, sign-in resumes

A meta.correct request is the record and its changes, whatever the evidence, so suggesting them again after a lost answer finds the issue; a confirmed filing clears it. A restart carries on every job parked on a raised budget with no Retry. A GitHub sign-in or a new agent credential on the Accounts tab resumes its parked job, while a share asks to sign in and share again. Also: the Verify notification title, recordMove for followMove, restart re-admitting the availability parks, and the share lookup's partial pages and 401 wording.
…rks re-admit only on a changed cap, contrib_unavailable after a failed refresh
…part from no sign-in

The contrib_unavailable park, the share and Suggest corrections failures and the
contribute=issue refusal before any spend now say when the Bridge is signed in
but GitHub couldn't be reached to refresh the sign-in (accounts.ErrUnrefreshed,
contrib.ErrSignInUnrefreshed). A 401 on a token already past its own expiry no
longer refuses the sign-in. The console and the Accounts tab show such a Bridge
as unable to share until a refresh succeeds.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant