Repository navigation
docs: clarify integration workspace workflow - #20
Merged
Merged
Conversation
Keep locked package builds on GOWORK=off while documenting the explicit non-release Core/WASM source checker. Separate package reviews, Core locks, and integration pin selection. Validation: documentation and script consistency review; git diff --check. No source, dependency, or integration pin changes. Co-authored-by: Codex <codex@openai.com>
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.
The guide now distinguishes locked package verification with
GOWORK=offfrom explicit development Core/WASM checks throughtest-core-source.sh. It explains why malt-ts stays outside the native integration workspace and keeps package source pins, the published-Core lock, and Gateway Console's package lock separate.Validation:
git diff --check; checked the rules against the Makefile and the locked-release and source-compatibility scripts. Documentation-only change; npm/WASM suites were not run. Package code, assets, dependency locks, and integration pins are unchanged.