fix(ci): preserve crate docs and declare artifact dependencies

[f0rr0]

Summary

Main's policy test contradicted the Markdown-only release policy, and the WASIX README doctest tried to start an unavailable runtime during source qualification. A query-only Rust package job also attempted to upload bindings and broker packages it had never selected. Parallel WASIX tools browser qualification then exposed missing task dependencies: it opened a seed package before the producer finished.

Expose the existing README as crate documentation across every public Rust library and generated release crate. Keep runtime and build-script examples compile-checked with no_run, hash READMEs in existing source tests, and scope each Rust source upload to its selected producer. Declare the tools consumers' extension and browser resource dependencies so shared producers finish before consumers while independent tests remain parallel. Extend the existing transfer test to verify that order. This preserves the source/artifact separation without adding CI jobs or tooling dependencies.

Release Intent

• The fix(ci): title covers the changed Cargo and package inputs. Runtime behavior, registry identities and versions are unchanged.
• Markdown-only edits retain source/package checks without requesting a product release. Generated crate documentation follows the existing SDK convention.

Verification

• Repository-pinned Moon owner checks: Rust formatting, Clippy, unit tests, doctests and source packages for both SDKs, query, bindings, broker, wire server, build helper and native tools.
• Full workflow gate: pinned actionlint and zizmor, 68 planner tests, nine artifact-transfer tests and scheduling fixtures. Release metadata and graph integration checks passed.
• Native/WASIX, extension, database-resource and shared packaging suites passed. The extracted native carrier/tools fixture builds Rustdoc and checks that README content is visible.
• Rustdoc for all nine public SDK/helper libraries passed with warnings denied. Actual Moon test hashes include the corresponding READMEs.
• Release mutation/fault cases completed. The local aggregate hit a workflow-waiter fixture timeout; the isolated waiter retry and remaining tests passed unchanged.
• The consumer dependency regression fails against the previous task graph and passes against the fixed graph. CI formatting/lint, the full workflow gate, release graph/metadata, and the WASIX tools owner test passed after this fix.
• Replayed the actual planned-job adapter with both SDK and tools browser consumers, Chrome 149, and two CPUs. Query and seed packages were prepared once before both browser tests ran in parallel; source and packed SDK smoke tests and packed tools smoke tests all passed.

The browser replay used runtime artifacts from the failed f2272ad3 CI run 36812091670 as diagnostic inputs, not as qualification of the new commit. That run passed source checks and both Rust package jobs but failed the WASIX TypeScript consumer job on the missing seed dependency. Fresh CI run 36837387629 is qualifying 9bed43253017b5a469eeead6697e49f48195c478. Planning, Rust checks/tests, artifact/resource tests, and WASIX tools source tests have passed; full qualification is still pending. Local synthetic packaging and prior-run runtime artifacts do not replace that gate.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
oliphaunt-docs	Ready	Preview	Oct 1, 2026 8:37am UTC