Skip to content

docs: stale-reference sweep — engine rename, Dockerfile, ADR-0007 errata#352

Merged
mfw78 merged 2 commits into
dev/m1from
docs/108-62-123-sweep-clean
Jul 15, 2026
Merged

docs: stale-reference sweep — engine rename, Dockerfile, ADR-0007 errata#352
mfw78 merged 2 commits into
dev/m1from
docs/108-62-123-sweep-clean

Conversation

@mfw78

@mfw78 mfw78 commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

What

Docs-only sweep clearing stale references left over from the crate rename and the M5 Docker ship:

  • docs/deployment.md: replaces the "Dockerfile is planned for M5" placeholder and inline sketch with a pointer to the real Dockerfile + docker-compose.yml at the repo root, and to docs/deployment/docker.md for the full container workflow. Notes the image is published to ghcr.io/nullislabs/shepherd:<tag> on every merged commit to main.
  • docs/production.md: replaces the "Dockerfile (interim)" multi-stage sketch and its status note with a pointer to the real root Dockerfile, plus the docker build/root docker-compose.yml build path.
  • docs/qa-signoff.md: nexum-engine -> nexum-runtime in the warn(unused_crate_dependencies) check row.
  • docs/adr/0007-upstream-protocol-logic-to-cow-rs.md: adds errata noting the crates/nexum-engine -> crates/nexum-runtime + crates/nexum-cli rename, and that the workspace now pins cowprotocol = "0.2.0" from crates.io with a temporary [patch.crates-io] git override to nullislabs/cow-rs pending a release with the hash-only OrderCreationAppData constructor.
  • docs/sdk.md: updates the versioning section from cowprotocol = "0.1.0" (no patch) to 0.2.0 with the same temporary patch override described above.
  • docs/02-modules-events-packaging.md: fixes the manifest-naming aside, the pre-rename filename was nexum.toml, not module.toml as the earlier draft claimed.

Historical ADRs, migration docs, and operations reports that describe what was true at the time are left as-is.

Why

Several docs pages still described planned-but-since-shipped work (the Dockerfile) or pre-rename crate/manifest names (nexum-engine, nexum.toml), which misleads new operators and reviewers cross-referencing the ADRs against the current tree.

Testing

Docs-only change, no build required. Verified crate names against the current workspace Cargo.toml and confirmed the linked docs/deployment/docker.md and root Dockerfile/docker-compose.yml exist and match the described workflow.

Closes #123, #108, #62

lgahdl added 2 commits July 15, 2026 10:23
…ata (#123, #108, #62)

- deployment.md: replace the "planned for M5" Dockerfile sketch with a
  pointer to the real Dockerfile + docker.md; update nexum-runtime log
  directive examples
- qa-signoff.md: nexum-engine → nexum-runtime in crate-dependency row
- adr/0007: add errata noting the nexum-engine → nexum-runtime rename
  and the [patch.crates-io] retirement now that cowprotocol 0.1.0 is
  on crates.io
…tion.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").
@mfw78 mfw78 added the base: dev/m1 Open PR targets dev/m1 integration branch — merge AFTER develop PRs; develop merged in last. label Jul 15, 2026
@mfw78 mfw78 merged commit 04413b1 into dev/m1 Jul 15, 2026
5 checks passed
@mfw78 mfw78 deleted the docs/108-62-123-sweep-clean branch July 15, 2026 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

base: dev/m1 Open PR targets dev/m1 integration branch — merge AFTER develop PRs; develop merged in last.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants