Monitoring-service terminology, verdict permanence docs, deployments manifest

[mfw78]

• Rename "watch-tower" to "off-chain monitoring service" across the docs (the polling agent is not upstream's watch-tower)
• Document verdict permanence: INVALID uniformly terminal, NEEDS_INPUT acquisition semantics, the Restriction overlay
• Publish the canonical deployments manifest (chainId → registry address, deploy block, ABI version, topic0 set) consumed by monitoring services

[mfw78]

All three bullets are satisfied. Checked against the tree rather than the commit subjects.

Monitoring-service terminology. #41 renamed the polling agent across docs/, and #53 finished the job in README.md, the tests, and the two glossary parentheticals that were still keeping "watch-tower" alive in the documents meant to retire it. The link to cowprotocol/tenderly-watch-tower went with it. rg -ni 'watch.?tower|tenderly' now returns nothing outside broadcast/StandardJsonInput/*.json, which are verbatim flattened-source verification inputs and not prose.

Verdict permanence. Documented in docs/architecture.md:

• INVALID uniformly terminal: "With restriction expressed as an overlay, the only producer of INVALID is the handler's own OrderNotValid; consumers never need a reason-selector branch for control flow."
• NEEDS_INPUT acquisition semantics: "acquire input or park, never a timed retry", with docs/discovery.md adding that consumers MUST NOT schedule empty-input re-polls and SHOULD probe IOrderModule via ERC-165.
• The Restriction overlay: reported as PollResult.restriction, never overwriting the generator verdict, so a guarded POST stays visible; owner-reversible and observable via SwapGuardSet.

Deployments manifest. deployments/networks.json is the manifest and deployments/README.md specifies it. The schema carries every field this bullet named: chainId keys, composableCow registry address, deployBlock, abiVersion, and the topic0 set. All four events it names exist on the contract (ConditionalOrderCreated, MerkleRootSet, ConditionalOrderRemoved, SwapGuardSet).

networks is empty, but that is the correct content: #46 established this fork has no deployments, and an empty map is what "no chain is serviced" looks like under the documented rules. The bullet asked for the canonical manifest to be published, and it is. Populating entries is a deployment-time action already covered by the manifest's own rule that entries are appended by the deployment pipeline, so nothing is lost by closing this.

Closing as completed.