[hq] refresh real-value pilot status#141
Merged
Merged
Conversation
e0661ba to
3b1730d
Compare
This was referenced May 14, 2026
Owner
Author
|
HQ post-merge reconciliation after PR #141 merged to main as f384236. Verified in isolated checkout E:\FlowMemory\flowmemory-main-post141 on detached origin/main: npm ci, npm ci --prefix apps/dashboard, npm ci --prefix crypto, npm run flowchain:product-e2e, npm run flowchain:l1-e2e, npm run flowchain:real-value-pilot:e2e -- -AllowIncomplete, node infra/scripts/check-unsafe-claims.mjs, and git diff --check passed. Strict npm run flowchain:real-value-pilot:e2e still fails closed with the expected six missing proof commands (#133-#138). npm run contracts:hardening:slither still exits 1 on the known BaseBridgeLockbox.releaseNative Slither findings tracked by #140. |
This was referenced May 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
main.Why
The previous HQ docs were accurate before PR #132 merged, but now
maincontains the HQ gate scripts and the release/static-analysis blockers are closed. The current no-go state is narrower: the strict pilot gate still fails until the six dedicated subsystem proof commands land onmain.Checks run
git diff --checknode infra/scripts/check-unsafe-claims.mjsnpm run flowchain:real-value-pilot:e2e -- -AllowIncompletenpm run flowchain:l1-e2e, strictnpm run flowchain:real-value-pilot:e2efailing as intended, andnpm run flowchain:product-e2eCurrent blockers
npm run flowchain:real-value-pilot:contractsnpm run flowchain:real-value-pilot:bridgenpm run flowchain:real-value-pilot:runtimenpm run flowchain:real-value-pilot:walletnpm run flowchain:real-value-pilot:control-dashboardnpm run flowchain:real-value-pilot:opsThe owner pilot remains no-go until those commands exist and strict
npm run flowchain:real-value-pilot:e2epasses onmainalongsidenpm run flowchain:l1-e2e.HQ Required Review Metadata (2026-05-14)
Allowed folders touched:
docs/FLOWCHAIN_REAL_VALUE_PILOT.mddocs/agent-runs/real-value-pilot-hq/infra/scripts/contracts-static-analysis.ps1infra/scripts/contracts-static-analysis.shinfra/scripts/flowchain-real-value-pilot-e2e.ps1package.jsonForbidden folders not touched:
crates/services/crypto/contracts/apps/dashboard/hardware/.github/Exact checks recorded in this PR body:
git diff --checknode infra/scripts/check-unsafe-claims.mjsnpm run flowchain:real-value-pilot:e2e -- -AllowIncompletenpm run flowchain:l1-e2e, strictnpm run flowchain:real-value-pilot:e2efailing as intended, andnpm run flowchain:product-e2eReadiness blockers:
DIRTYat HQ review time; do not merge until rebased/reconciled with currentmainand checks are coherent.