@@ -109,10 +109,12 @@ Still open around it:
109109recall window, so time-range questions run as point recalls,
110110[ #47 ] ( https://github.com/mmeyerlein/meclaw/issues/47 ) the async cell shutdown
111111drain,
112- [ #147 ] ( https://github.com/mmeyerlein/meclaw/issues/147 ) wiring the inline ingress
113- without its reject drain fails silently — a wiring-time check, deliberately held
114- for the architecture pass that makes inline extraction a system-wide property
115- rather than a per-hive feature.
112+ [ #147 ] ( https://github.com/mmeyerlein/meclaw/issues/147 ) is closed in 0.10.2, and
113+ not as the per-hive feature it was held for: a hive declares which of its ports
114+ come in pairs (` params.required_drains ` ), and the mutation that wires the
115+ ingress without the drain is refused. The architecture pass that makes inline
116+ extraction a system-wide property is unaffected — it inherits a rule instead of
117+ having to invent one.
116118
117119## The wave before the launch
118120
@@ -154,14 +156,18 @@ The good first issues from the first public wave — #3 and #4 — shipped with
154156template is a directory, a README and a ` template.json ` , and the fourteen listed
155157in [ ` templates/README.md ` ] ( templates/README.md ) are the worked examples — eleven
156158single-purpose ones plus three composites: ` talky@1.2.0 ` , which carries four of
157- them as sub-units, ` cogny@1.3.0 ` , which carries two, and ` memory-hive@1.2 .0 ` , the
159+ them as sub-units, ` cogny@1.3.0 ` , which carries two, and ` memory-hive@1.3 .0 ` , the
158160agent memory as a hive of ten cells. New ones are welcome.
159161
160162## Shipped
161163
162164One line per release; details in [ CHANGELOG.md] ( CHANGELOG.md ) and the
163165[ GitHub releases] ( https://github.com/mmeyerlein/meclaw/releases ) .
164166
167+ - ** v0.10.2 — a wired port must have its drain.** A hive can declare which of
168+ its ports come in pairs, and a mutation that wires the ingress without the
169+ egress is refused rather than quietly opening a lane that loses messages. The
170+ check asks the router, not the condition's spelling.
165171- ** v0.10.1 — an edge can be replaced again.** ` remove_edges ` now runs before
166172 ` add_edges ` , so dropping a lane and adding its widened replacement in ONE
167173 mutation does what it reads like. The other way round it deleted its own new
0 commit comments