docs(agents): the burst coupling is spent rather than removed, and the production path automerges #25

Merged

jlxq0 merged 1 commit from docs-deploy-facts into main

2026-08-26 14:41:57 +00:00

jlxq0 commented

2026-08-26 14:39:46 +00:00

Owner

Documentation only, from the v0.2.0 deploy. Both entries correct something two sessions held wrongly until someone read the source.

The coupling was spent, not removed. At burst 24 it takes about ten identities to exhaust a 256-session pool where it took thirty-two. Saying it "does not arise" would be read by the next person as a guarantee of the design. And what makes it safe today is the identity population rather than the number: the bucket keys on the Logto sub and every agent on this machine resolves to one identity, so the distinct count is a handful. CALDAV_MCP_INITIALIZE_BURST puts that one command from mattering.

Production is not gated by a human. The manual rule matches clusters/fondue/*-www/**; this application's path is clusters/fondue/caldav-mcp, so it falls through to BASELINE with automerge: true. oddie-apps/platform#589 opened at 14:30 and merged itself at 14:32. A pattern that silently declines is invisible, and so is a merge nobody has to perform.

Gates green: fmt, test (116 + 9). No code change.

Documentation only, from the v0.2.0 deploy. Both entries correct something two sessions held wrongly until someone read the source. **The coupling was spent, not removed.** At burst 24 it takes about ten identities to exhaust a 256-session pool where it took thirty-two. Saying it "does not arise" would be read by the next person as a guarantee of the design. And what makes it safe today is the identity **population** rather than the number: the bucket keys on the Logto `sub` and every agent on this machine resolves to one identity, so the distinct count is a handful. `CALDAV_MCP_INITIALIZE_BURST` puts that one command from mattering. **Production is not gated by a human.** The manual rule matches `clusters/fondue/*-www/**`; this application's path is `clusters/fondue/caldav-mcp`, so it falls through to BASELINE with `automerge: true`. `oddie-apps/platform#589` opened at 14:30 and merged itself at 14:32. A pattern that silently declines is invisible, and so is a merge nobody has to perform. Gates green: fmt, test (116 + 9). No code change.

jlxq0 added 1 commit

2026-08-26 14:39:46 +00:00

docs(agents): the burst coupling is spent rather than removed, and the

CI / cargo (pull_request) Successful in 40s

Details

CI / docker (pull_request) Successful in 51s

Details

126ab5d003

production path automerges

Two corrections from the v0.2.0 deploy, both of which two people held wrongly
before anyone checked.

The burst and MAX_SESSIONS stay coupled at burst 24. The coupling was spent,
not removed: 32 identities to fill the pool becomes about 10. And what makes
that safe today is the identity population rather than the number, since the
bucket keys on the Logto sub and every agent on this machine resolves to one
identity. That is a property of today and the env var puts it one command from
mattering.

Production was described as a manual gate by two sessions. It is not. The
manual rule matches clusters/fondue/*-www/**, and this application's path is
clusters/fondue/caldav-mcp, so it falls through to BASELINE with automerge.
The v0.2.0 bump opened at 14:30 and merged itself at 14:32. Read the rule
against the path, never against the repository.

jlxq0 merged commit f9a0141ed6 into main

2026-08-26 14:41:57 +00:00

jlxq0 deleted branch docs-deploy-facts

2026-08-26 14:41:57 +00:00

jlxq0 referenced this pull request from a commit

2026-08-26 14:41:58 +00:00

Merge pull request 'docs(agents): the burst coupling is spent rather than removed, and the production path automerges' (#25) from docs-deploy-facts into main