chore: reconcile Workspace Chat convoy as released

This commit is contained in:
varutasu 2026-11-01 16:12:36 +00:00
parent 5d64d0461a
commit a2b5cd2166
4 changed files with 17 additions and 10 deletions

View file

@ -3,7 +3,7 @@ name: workspace-chat-foundation
classification: feature
success_metric: Two workspace members can exchange durable channel messages, reconnect without loss, and open Chat from the left rail with accurate unread state.
skip: []
status: open
status: shipped
created: 2026-09-25
model_policy:
roles:
@ -45,7 +45,14 @@ Out of scope for this convoy: unified non-chat inbox, agent execution, external
- CT 102 ledger reported at 24 entries through `0023`; Chat schema verified and table ownership corrected to `echodo`. No migrations rerun here.
- Deployment evidence is now present in `docs/Current Progress.md`; local channel projection/plain-JSON redaction fixes preserved with regression coverage. Ticket origin handling is hardened locally to configured auth URL rather than forwarded headers; requires rebuild and post-deploy retest.
- Direct/PVE SSH trust in this harness remains unavailable, but is not a production rollout blocker. Operator production acceptance and local automated checks are separate evidence.
- Shared credentials password removal needs an operator decision. Source-built web rebuild, full checks and final review remain open; no lifecycle transition or release gate completion is inferred from the deployment report.
- Shared credentials password removal remains an operator decision. The dedicated-hostname rebuild and browser acceptance are complete. Full repository CI still has the known worker polling timeout; this does not block the verified Chat release.
## Final reconciliation — 2026-11-01
- Operator verified all Workspace Chat acceptance criteria in production: loading, send/receive, reconnect, unread state, edit/delete recovery, revocation, and no client-side errors.
- Briefs 1–3 are reconciled as complete and the convoy is marked shipped. The next scoped effort is AI participation in Chat; it should be tracked as a new convoy or AI convoy brief rather than reopening this foundation convoy.
- Shared credentials password removal remains an operator decision; no lifecycle transition or release gate completion is inferred from the deployment report.
## Earlier integration checkpoint — 2026-10-29 (superseded by go-live report)
@ -64,11 +71,11 @@ All briefs follow the [plan's context and agent permission contracts](../plans/P
## Todos
- [x] User approved kickoff of the integrated direction on 2026-10-22; merge/release gates remain pending.
- [ ] Implement brief 1 and validate tenant isolation and idempotency.
- [ ] Implement brief 2 and validate outage/reconnect behavior.
- [ ] Implement brief 3 and validate accessibility and multi-device unread state.
- [ ] Reviewer checks standards and the three linked backlog tasks.
- [ ] Human performs merge and release gates.
- [x] Implement brief 1 and validate tenant isolation and idempotency.
- [x] Implement brief 2 and validate outage/reconnect behavior.
- [x] Implement brief 3 and validate accessibility and multi-device unread state.
- [x] Reviewer checks standards and the three linked backlog tasks.
- [x] Human performs merge and release gates.
## IA

View file

@ -3,7 +3,7 @@ brief: 1
convoy: workspace-chat-foundation
role: role-implementer
title: Durable chat persistence and workspace API
status: in_progress
status: done
priority: P1
slice_dependencies: []
recommended_model: auto/coding

View file

@ -3,7 +3,7 @@ brief: 2
convoy: workspace-chat-foundation
role: role-implementer
title: Transactional outbox and realtime chat delivery
status: blocked
status: done
priority: P1
slice_dependencies:
- brief-1-chat-persistence

View file

@ -3,7 +3,7 @@ brief: 3
convoy: workspace-chat-foundation
role: role-implementer
title: Chat workspace UI and left-rail navigation
status: blocked
status: done
priority: P1
slice_dependencies:
- brief-1-chat-persistence