behaviour.sysml still denies shipped RSV (MN-REQ-12.13 honesty)

[chouswei]

Gap

MN-REQ-12.13 shipped in 0.4.4: NeighbourhoodReserve.implemented=true, memnet.neighbourhood_reserve, CLI reserve / extend / release.

behaviour.sysml / verify.sysml still deny it:

• ParentTaskLifecycle doc: neighbourhood reserve remains not shipped
• EvOverlapScopeForbidden / WorkerScopedTurn / MN_VER_12_S13: no neighbourhood reserve coordinates overlapping writers
• AsyncTaskDispatch / WorkerPool: no RSV engine claimed

Same honesty class as #52 (ACL clause). Agents reading the nest will skip reserve that the engine actually gates.

Target

Sync behaviour + verify + any leftover docs so RSV is as-is shipped (optional use, not “not implemented”). Do not re-implement the engine.

Out of scope

New RSV features. WorkerWriteScope (#32). N-server (#47).

[chouswei]

0.4.5 refresh (still open): Engine RSV is shipped (NeighbourhoodReserve.implemented=true). behaviour.sysml still says reserve is not shipped (ParentTaskLifecycle, EvOverlapScopeForbidden / MN-VER-12-S13). Honesty gap unchanged. Not started.

[chouswei]

Engine is shipped (NeighbourhoodReserve.implemented, docs/extras/memnet-neighbourhood-reserve.md, package 0.19.1). CapsPolicy ACL is shipped when session ACL is enabled.

Still this issue: sysml-models/models/behaviour.sysml still teaches the opposite — ParentTaskLifecycle “Neighbourhood reserve remains not shipped” (~L732) and workerApplyingScopedMutate “reserve is not shipped” (~L879). deploy.sysml / requirements.sysml already claim RSV. Sync behaviour (+ any verify cases that still deny RSV) so agents do not skip reserve. Do not re-implement the engine.