Skip to content

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

Open
lgahdl wants to merge 2 commits into
feat/m1-mock-venuefrom
docs/108-62-123-sweep
Open

docs: stale-reference sweep — engine rename, Dockerfile, ADR-0007 errata#311
lgahdl wants to merge 2 commits into
feat/m1-mock-venuefrom
docs/108-62-123-sweep

Conversation

@lgahdl

@lgahdl lgahdl commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Closes #123, #108, #62

Three-file docs sweep addressing post-rename and post-M5-ship staleness.

Changes

docs/deployment.md — Replace the "Dockerfile is planned for M5" placeholder and sketch block 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. The M5 milestone shipped; the sketch is misleading to new operators.

docs/qa-signoff.mdnexum-enginenexum-runtime in the warn(unused_crate_dependencies) check row (line 15).

docs/adr/0007-upstream-protocol-logic-to-cow-rs.md — Add errata noting: (1) crates/nexum-enginecrates/nexum-runtime + crates/nexum-cli rename, (2) [patch.crates-io] rev-bump mechanism retired once cowprotocol 0.1.0 published to crates.io. ADRs 0001, 0006, and 0009 already carry this errata; 0007 was the remaining gap.

What's not changed

  • Historical ADRs, migration docs, and operations reports are left as-is (they describe what was true at the time).
  • docs/sdk.md Versioning section was already correct (cowprotocol = "0.1.0", no [patch.crates-io]).
  • docs/01-runtime-environment.md nexum.toml references and docs/02-modules-events-packaging.md diagram were already fixed in the M1 train.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TfSsJPYDQ1GQGbnSVFxATx

…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

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TfSsJPYDQ1GQGbnSVFxATx
@lgahdl lgahdl requested a review from mfw78 as a code owner July 9, 2026 22:25
@jean-neiverth

Copy link
Copy Markdown
Collaborator

Nice cleanup! The new text references ghcr.io/nullislabs/shepherd:<tag>, which matches what CI produces on the canonical repo. But docker-compose.yml (line 26) still hardcodes ghcr.io/bleu/nullis-shepherd:latest, and both .env.example and docs/deployment/docker.md also reference the old bleu/nullis-shepherd name.

Since this section cross-references those files and shows the docker compose up -d quick start, wonder if an operator would end up seeing two different image names depending on which file they're reading. I think PR #220 addresses the same root cause — maybe worth coordinating so they land consistently.

…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").

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TfSsJPYDQ1GQGbnSVFxATx
@lgahdl lgahdl force-pushed the docs/108-62-123-sweep branch from 3653ce8 to 4e69f91 Compare July 10, 2026 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants