docs: prepare Consensus v0.6 and Studio v0.123 release - #472
Open
MuncleUscles wants to merge 2 commits into
Open
docs: prepare Consensus v0.6 and Studio v0.123 release#472MuncleUscles wants to merge 2 commits into
MuncleUscles wants to merge 2 commits into
Conversation
Document fee-funded transactions, safe appeals, Studio preview networks, tooling RC integration, ECVRF selection, tribunals, developer rewards, keeper operations, and migration guidance. Refresh the JavaScript and Python API surfaces from the exact train heads and add a build-time release invariant check over 363 consensus error selectors and critical behavior anchors.\n\nValidated with the complete 231-route production build, protocol-doc checks, release-doc checks, generated API/LLM exports, and whitespace checks.
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Remove the obsolete ReadyToFinalize status, renumber the terminal phase statuses to the 14-value consensus ontology, document gen_getTransactionLifecycle, and update receipt fields including fee accounting and the absent previousStatus. Strengthen protocol and release checks so the old ordinal model, status timestamp projection, and incomplete vote enum fail before publication.\n\nValidated with the 232-route production build, both documentation checks, generated API and LLM exports, and whitespace checks.
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
1 participant
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.
Delivery context
Depends-On:
Cross-stack release qualification remains owned by genlayerlabs/genlayer-e2e#756. Node v0.6 interface PR #1800 and CLI fee PR #412 are already merged. This docs layer is deliberately downstream of, and outside, the frozen six-PR product landing cut.
Source snapshots used for generated/reference content and integration examples:
2f78febfc06866e59e7f12db848664e95ce99e8e6666892c3ee124e3804e391688c4156a4736fdac2f8122e81862bd5f6cf0daabcfa34b99a1bb060039c54bcc5bc9de3a635bbd5f6a2e3db0310f7ab1054200d3f3d75cProblem and outcome
The next-release documentation was split across old draft PRs and still contained materially stale behavior: pre-ECVRF randomness, first-contract-only developer rewards, obsolete SDK calls and network commands, incomplete appeal charges, an old custom-error set, and the pre-resolution-kernel 15-status lifecycle.
This layer prepares the complete Consensus v0.6 / Studio v0.123 documentation release:
topUpAndSubmitAppeal, including bond + induced-work funding and the exact 2.5× successful bond return;studio-nextdescribed only as an optional browser alias;gen_getTransactionStatus, advancedgen_getTransactionLifecycle, and action-based finalization readiness;previousStatus: null, fee accounting, status names, and the complete execution-vote enum;The imported Node receipt source still showed
LeaderRevealingat its former ordinal 14 even though #1800 removedReadyToFinalize; this layer corrects it to 13 and adds a regression check so a later docs sync cannot silently restore the wrong ordinal.Superseded drafts
This PR consolidates and corrects the useful material from #425, #428, #432, #436, and #439. It replaces the stale integration bundle #441; those PRs should not be merged on top of this layer.
Implementation and validation
npm run build: passing, including 232 static routes, TypeScript validation, generated node API docs, complete docs bundles, and LLM export checks.npm run check:protocol-docs: passing (27 concept pages and all 14 transaction statuses).npm run check:v06-release-docs: passing (363 unique selectors and behavior anchors).git diff --check: passing.0f712376.Full product E2E is not duplicated from this docs-only PR; #756 owns qualification of the exact product snapshot. Publication should wait for the upstream train and matching tooling RC names to become final. The actual Studio deployment, DNS aliases, and package/container releases are intentionally outside this PR.