glm-5.2
1baa619ce9
The monolithic open-questions.md (1310 lines, 47 OQs) was large enough to be unmanageable, with high size variance (OQ-42 at 220 lines next to OQ-06 at 8). Decomposed into one file per OQ under docs/architecture/questions/ (NNN-slug.md, mirroring the ADR convention), with open-questions.md retained as the index: theme-grouped tables plus a cross-theme Deferred/Blocked section that surfaces the 6 deferred OQs with their Blocked-on conditions inline (the safe-exit visibility surface). Per-OQ content moved verbatim; all 62 inbound links stay valid (none used anchors). README's curated OQ summary dropped (now redundant with the index tables). Also seeds tasks/architecture/ with this task plus two follow-ups found during the decompose: OQ-09/10 missing structured Blocked-on fields, and the tasks/architecture/ blocker-task half of the Safe Exit protocol being unenforced.
16 lines
854 B
Markdown
16 lines
854 B
Markdown
# OQ-27: from_call Re-Import Trigger
|
|
|
|
- **Origin**: [client-and-adapters.md](crates/call/client-and-adapters.md), ADR-017 Assumption 4
|
|
- **Status**: **resolved** (2026-06-27)
|
|
- **Door type**: Two-way
|
|
- **Priority**: low
|
|
- **Resolution**: The decision is **auto-re-import on connection
|
|
establishment**. The overlay is per-connection (Layer 2, ADR-024), so a
|
|
stale overlay dies with the connection; re-import on reconnect is
|
|
naturally scoped to the new connection. This is the right default for the
|
|
runner pattern (a worker reconnects → the hub re-discovers the worker's
|
|
ops automatically). An explicit `CallConnection::refresh()` method is a
|
|
genuine feature addition — non-breaking, additive — if a deployment
|
|
needs manual control.
|
|
- **Cross-references**: ADR-017, ADR-024, [client-and-adapters.md](crates/call/client-and-adapters.md)
|