Answer A-319: entry-again also asks the shadow's entries again

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 23:13:12 +01:00
parent 9ebf6e58f0
commit 4d7fc66110
1 changed files with 3 additions and 0 deletions
@@ -568,3 +568,6 @@ the principle that settles it, cited as "design 47 G A-n".
    module's views reader has no FollowSeat);
  - the indexer's tools `indexer_read_*` and `indexer_pending` (the seat serves no such verb): the manifests' invokes
    name the module, the code takes the module from the seat's holder.
+- **A-319** (§698, A-312; principles 1 and 7) The node-engine's `entry-again` asks again every entry cache the
+  node-engine keeps, its own composer's and its shadow's, so an entry once answered not-found in the shadow is taken in
+  on the same act; the shadow re-answers its candidates on that answer. No cache is polled.