You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: fix the sweep's own stale claims - cowprotocol override, production.md 3.1
Review catches on the stale-reference sweep itself:
- ADR-0007 errata and sdk.md Versioning both claimed cowprotocol is a
clean 0.1.0 registry dependency "with no git override". The branch's
own Cargo.toml pins 0.2.0 WITH an active [patch.crates-io] override
to nullislabs/cow-rs (pending the hash-only OrderCreationAppData
constructor release). Both now describe that state and point at the
patch-block comment as the source of truth.
- production.md 3.1 still shipped the "interim" hand-rolled Dockerfile
recipe issue #123 flagged; replaced with a pointer to the real root
Dockerfile and docs/deployment/docker.md.
- 02-modules-events-packaging.md: un-garble the parenthetical the
earlier rename made self-contradictory ("was module.toml in earlier
drafts" -> "was nexum.toml").
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TfSsJPYDQ1GQGbnSVFxATx
Copy file name to clipboardExpand all lines: docs/02-modules-events-packaging.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ A module is distributed as a **bundle** - a WASM component plus a manifest that
6
6
7
7
### Manifest (`module.toml`)
8
8
9
-
Every module ships with a manifest. The file is named `module.toml` in 0.2 (was `module.toml` in earlier drafts; per [ADR-0001](adr/0001-engine-toml-separate-from-nexum-toml.md) the operator/module split is now explicit).
9
+
Every module ships with a manifest. The file is named `module.toml` in 0.2 (was `nexum.toml` in earlier drafts; per [ADR-0001](adr/0001-engine-toml-separate-from-nexum-toml.md) the operator/module split is now explicit).
- A follow-on Bleu module - the Rust-side equivalent of `cowprotocol/refunder` (permissionless `invalidateOrder` triggering for expired EthFlow orders) - becomes natural to ship once an ethflow-watcher module lands. Out of scope for M2 but explicitly enabled by the same primitives.
46
46
- TWAP polling logic (decode `ConditionalOrderCreated`, eth_call `getTradeableOrderWithSignature`, decode return, build `OrderCreation`) and EthFlow event decoding stay entirely in guest module code. The `cowprotocol` crate provides only the types and the orderbook client; the strategy is the module's.
47
47
48
-
_Errata: `crates/nexum-engine` was renamed to `crates/nexum-runtime` + `crates/nexum-cli` in the 0.2 refactor. The `[patch.crates-io]`rev-bump mechanism was retired once `cowprotocol 0.1.0` published to crates.io; the workspace now pins it as a normal registry dependency with no git override._
48
+
_Errata: `crates/nexum-engine` was renamed to `crates/nexum-runtime` + `crates/nexum-cli` in the 0.2 refactor. The `cowprotocol` crate now publishes to crates.io (the workspace pins `0.2.0`), so the PR-#5-head consumption model above is historical; a `[patch.crates-io]`git override to `nullislabs/cow-rs` remains active pending a release with the hash-only `OrderCreationAppData` constructor - see the comment above the patch block in the root `Cargo.toml` for the current state._
0 commit comments