Unified Agent + reusable Go agent core.
docs: clarify console runtime snapshot flow
+11
-2
+11
-2
docs/configuration.md
+11
-2
docs/configuration.md
···
94
94
- A running `console serve` instance works from its current snapshot.
95
95
- When `config.yaml` changes, a new snapshot is built and swapped in.
96
96
- If rebuilding fails, the old snapshot keeps running.
97
+
- In-flight tasks keep their bound generation. New tasks use the next generation only after the swap.
97
98
98
99
## Console Update Path
99
100
···
120
121
| |
121
122
| success | failure
122
123
v v
123
-
swap local runtime keep old snapshot
124
-
reload managed runtimes log warning
124
+
prepare local generation
125
+
prepare managed runtimes
126
+
|
127
+
v
128
+
apply both sides
129
+
|
130
+
v
131
+
new tasks use new generation keep old snapshot
132
+
old in-flight tasks finish on old generation
125
133
```
126
134
127
135
This separation is intentional:
···
129
137
- the write path is responsible only for durable config
130
138
- the runtime layer is responsible only for consuming snapshots
131
139
- concurrency stays inside each runtime instance, not inside the config writer
140
+
- config writes are atomic replace, so the poller sees either the old file or the new file
132
141
133
142
## Console Startup With Invalid Config
134
143