Slack-Colibri bridge: update proposal for v0 production status (#21)

## Summary

Updates the Slack-Colibri bridge proposal (merged in #20) to reflect
that v0 has shipped and is operational. Tightens the narrative from
"design we propose" to "this is what's running, here's where things need
to go to be maintained".

Status: v0 forward path **live since 2026-05-31** on
[`@feelingofcomputing.bsky.social`](https://bsky.app/profile/feelingofcomputing.bsky.social)
(`did:plc:4gcxakknd6hxtnhf33miwsob`). Community owned by a separate
identity (`did:plc:j7nm3lrd5h7fm3sfhcv3lhfv`) — the **inverse pattern**
the original proposal described under *Inverse pattern: community owner
pre-creates channels* is what shipped.

## What the update reflects

- **Live features** (bulleted): messages, mentions (with DID
resolution), threaded replies, reactions add/remove, edits + deletions,
file attachments (image/video/audio inline, 5 MB cap with placeholder
for oversize), lossless `com.feelingofcomputing.bridge.slackRaw`
archive.
- **Code section** linking the slack-sync monorepo (worker + backfill +
Slack manifest); auto-deploy via Cloudflare Workers Builds on push to
`main`.
- **Lexicon namespace** renamed `com.feelingof.bridge.*` →
`com.feelingofcomputing.bridge.*` since FoC owns
feelingofcomputing.com/.org/.net.
- **Architecture diagram updated**: no D1 cache in v0; `slackRaw` is the
de-facto idempotency boundary.
- **Maintenance section** describes where bridge config lives (in-source
`CHANNEL_MAP` + `SLACK_USER_DID_MAP`, mirrored in JSON sidecars for the
backfill) and how the community owner extends it for new channels.
- **Speculative future-work content removed**: the `slackOrigin` /
`slackChannel` / `slackUser` lexicon designs (we don't intend to write
these — the in-source maps are sufficient at FoC scale), the v2
claim-flow and OAuth narrative, and the "we propose to ship X" framing.
Replaced with a "Known gaps" section that lists what's observably
missing as facts, not as a commitment.

Diff is `-291 / +86` against `main` (one commit on top, scope is just
the post-merge update — the original proposal landed in #20).

## Test plan

- [x] Live bridge operational on `@feelingofcomputing.bsky.social`; can
be observed end-to-end by posting in any bridged Slack channel and
watching the record land on the bot's PDS, then in Colibri.
- [x] Backfill validated against the new identity (4 weeks bridged
2026-05-05 → 2026-06-01, 0 failures).
- [ ] Reviewer eyeballs that the *Identity* and *Maintenance* sections
match their understanding.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: tomlarkworthy