Design 47 H: H-A-65, the tool runner's call-timeout setting waits for H4; 30 s constant in H1
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
@@ -248,3 +248,9 @@ Where two preparers disagreed, the chosen one is named.
|
||||
existing output changes; a subtask of the contracts-indexer-bridge developer in `mesh-delivery-sdk/seatgen`), and the
|
||||
node-engine definition gains the enum `ManifestReadWord` with that value. P9 (every reader takes it from the generated
|
||||
package), P7.
|
||||
- **H-A-65 (tool runner developer, 02:33)** How the setting `call-timeout` reaches the tool runner: not in H1. The
|
||||
node-engine composes the tool runner's unit as a special case (two environment variables, no config file), so the
|
||||
setting's path is the generic manifest `config` with its file resource, built in H4 when that special case goes
|
||||
(principle 7, no module special-cased in shared code). In H1 the runner's own bound is a constant of 30 seconds and the
|
||||
per-verb `timeout` carries every real need (`merge-pull` 120); the manifest declares no setting it does not read
|
||||
(principle 3). Rules-are-weighed: principle 11 bent for one release, said to the operator.
|
||||
|
||||
Reference in New Issue
Block a user