tmk241/hemx
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(requirements): migrate to installed redgate format

Browse Source
This commit is contained in:
slhx agent
2026-07-14 01:37:05 +02:00
parent 025d9c1563
commit 23b1d75f7f
7 changed files with 431 additions and 844 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PLAN.md
+1 -1
View File
@@ -77,4 +77,4 @@ encryption, retention, backup, and deployment policy remain host concerns.
- **Requirements:** `v1_release/001-010`, `versioning/*`, `test/*`, `diag/*`, `performance/*`, `security/008`, and all requirements changed by the preceding slices.
- **Proof:** clean-tree formatting, workspace tests, strict all-target Clippy, compile-fail, browser/WASM/offline/multiplayer scenarios, benchmark budgets, approved pinned lockfile audit, requirements proof audit, docs/examples checks, and independent contradiction review all pass with no unresolved P0/P1.
`cargo test -p hemx-core --test effect_batch compatibility_fixture_accepts_only_the_declared_v1_wire_version -- --exact`, `cargo test -p hemx-wasm --test browser flat_patch_persists_offline_then_uploads_with_same_operation_identity -- --exact`, and `cargo test -p hemx-v0-examples -p hemx-client-local-example -p hemx-kanban-example -p hemx-saas-example --lib --bins` prove the first compatibility gate. The first `hemx-xtask test` audit found and fixed three genuine local failures: the app-facing durable-sync primitive now accepts ordinary `IntoEffect`, the canonical example contract recognizes the explicitly isolated legacy fixture, and the canonical gate uses the installed `redgate health` syntax. Workspace/browser tests then pass until requirements governance. The remaining exact blocker is a redgate/parser-format mismatch: the installed CLI interprets the elected lines beginning `0<TAB>001...` as duplicate IDs such as `laws/0`; `cargo-audit` and `cargo-deny` are also unavailable locally. Execution cursor: reconcile or provide the project-approved redgate version/format without mutating the concurrently edited `REQUIREMENTS.md`, rerun `hemx-xtask test`, then run or explicitly disposition the unavailable pinned-lockfile audit tools.
`cargo test -p hemx-core --test effect_batch compatibility_fixture_accepts_only_the_declared_v1_wire_version -- --exact`, `cargo test -p hemx-wasm --test browser flat_patch_persists_offline_then_uploads_with_same_operation_identity -- --exact`, and `cargo test -p hemx-v0-examples -p hemx-client-local-example -p hemx-kanban-example -p hemx-saas-example --lib --bins` prove the first compatibility gate. The release audit fixed three genuine local failures: the app-facing durable-sync primitive now accepts ordinary `IntoEffect`, the canonical example contract recognizes the explicitly isolated legacy fixture, and the requirement corpus is mechanically migrated from duplicated legacy headings/ring prefixes to the installed redgate `## component` plus `ID<TAB>SUMMARY` format without changing its 413 obligations. `cargo run -p hemx-xtask -- test` now passes the complete workspace, browser, techdemo, and citation-reference gate. `cargo audit --version` and `cargo deny --version` both fail with Cargo `no such command`; dependency installation and an approved pinned-lockfile audit therefore remain externally blocked. Execution cursor: run the remaining local performance/docs/examples/contradiction gates, then obtain explicit authority or a supplied environment for `cargo-audit` and `cargo-deny` before claiming release readiness.