partySourceGate ran on every PUT/move at party-depth-or-below and rejected with 409 whenever the party lacked a registry row — including edits of files already filed under working/<party>/…. The gate is an ONBOARDING guard (don't let a typo'd/unregistered party folder be introduced), not a write gate: once the party directory exists on disk the party is established, so editing within it must succeed. Allow when <project>/<peer>/<party>/ already exists; keep the 409 only for introducing a brand-new unregistered party. This was surfaced by the browse markdown editor 409ing on save for an existing file under a party folder whose ssr/ row was missing or differently-cased. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| apps | ||
| archive | ||
| auth | ||
| cache | ||
| config | ||
| convert | ||
| fs | ||
| handler | ||
| jsonschema | ||
| listing | ||
| policy | ||
| tlsutil | ||
| zddc | ||
| zipfs | ||