Skip to content

docs: trim user-facing tutorial, sdk, testing and scripts docs - #602

Merged
mfw78 merged 3 commits into
dev/m1from
docs/598-user-docs
Jul 25, 2026
Merged

docs: trim user-facing tutorial, sdk, testing and scripts docs#602
mfw78 merged 3 commits into
dev/m1from
docs/598-user-docs

Conversation

@mfw78

@mfw78 mfw78 commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

What

Trim the user-facing docs to the house standard (terse, factual, British -ize, no em dashes) as part of the #598 cruft sweep.

Retarget docs/tutorial-first-module.md from the removed stop-loss / cow-api walkthrough to the shipped price-alert example: block subscription, chain read with ABI decode, [config]-driven behaviour, current crate names (nexum-sdk, nexum-sdk-test) and the #[nexum_sdk::module] macro surface. Dropped the aspirational four-hour time-budget framing and the per-section time estimates.

Delete docs/qa-signoff.md, a dated (2026-06-17) pre-review sign-off snapshot.

docs/testing-runtime-harness.md: drop the nonexistent shepherd-sdk-test mock surface (module-logic tests use nexum-sdk-test, venue-facing logic adds videre-test's transport mocks), repoint the sdk.md companions anchor, trim the intro essay.

scripts/README.md: purge em dashes, drop the reference to the deleted docs/operations/e2e-prep.md, and remove the stale stop-loss note.

docs/sdk.md left unchanged: already terse, and its nexum-sdk/videre-sdk split description, the "nothing re-exported between them" claim, keeper::retry_action, and the rustdoc-generation command all verify against the crates.

Why

The tutorial walked a stop-loss module that no longer exists and linked pre-rename crates (shepherd-sdk, shepherd-sdk-test) and the removed cow-api host path, so it could not be followed. The other files carried a deleted mock surface, a dead runbook link, a dated snapshot, and em dashes.

Testing

Markdown-only area: verified nothing links to the deleted docs/qa-signoff.md or docs/operations/e2e-prep.md; every command, crate, module path, and macro in the rewritten tutorial checked against dev/m1 (price-alert source, nexum-cli positional-plus---engine-config surface, #[nexum_sdk::module] expansion, nexum_sdk_test::MockHost). No em dashes remain in the touched files.

AI Assistance

Documentation-only sweep; verification ran was the link and command/crate/path cross-checks against the dev/m1 worktree described above.

Deviations flagged

  • The stop-loss module is absent from modules/ (dev/m1 tip), yet the E2E shell scripts still reference it: scripts/e2e-onchain.sh:19,22,145 and scripts/env-template:24,44. These .sh/template files are outside this area's editable paths (only scripts/README.md is owned here), so the residual references are left for the scripts owner; the twap-monitor and ethflow-watcher markers the scripts primarily exercise do still exist.

Part of #598.

Retarget tutorial-first-module.md from the removed stop-loss/cow-api walkthrough to the shipped price-alert example (block subscription, chain read, ABI decode) with current crate names and the #[nexum_sdk::module] macro surface; drop the aspirational time-budget framing.

Delete qa-signoff.md, a dated pre-review sign-off snapshot.

testing-runtime-harness.md: drop the nonexistent shepherd-sdk-test mock surface (module logic tests use nexum-sdk-test plus videre-test's transport mocks), repoint the sdk.md anchor, trim the intro.

scripts/README.md: purge em dashes, drop the deleted e2e-prep.md reference and the stale stop-loss note.

Part of #598.
@mfw78
mfw78 force-pushed the docs/598-user-docs branch from b27b3ca to 3ae1339 Compare July 25, 2026 03:12
mfw78 added 2 commits July 25, 2026 03:30
Hard-wrapped prose churns diffs: a one-word edit reflows the whole paragraph. Join each paragraph onto a single logical line and let it soft-wrap. Content unchanged (word and heading counts preserved); code fences, tables, lists, blockquotes and headings untouched.
@mfw78
mfw78 merged commit 1ea4db2 into dev/m1 Jul 25, 2026
7 checks passed
@mfw78
mfw78 deleted the docs/598-user-docs branch July 25, 2026 06:11
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.

1 participant