Repository navigation
refactor(deployments): align supported repository layouts - #10
Merged
Merged
Conversation
ci-sourcerer
marked this pull request as ready for review
November 5, 2026 13:32
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.
Align deployment configuration and UI with Stacksmith’s three retained layouts. Remove
flat-files, label folders as Environment directories, and document ambiguity handling and the one-root limit. Pin API and execution builds to the corresponding Stacksmith commit.Validation: 308 frontend tests passed. Backend suite against the changed Stacksmith code: 649 passed, 16 skipped, 3 failures in unchanged
tests/test_stack.pycontainer-launcher expectations. Existing lint failure inscripts/stack.pyremains outside this change. API, worker, frontend, database, and storage containers are healthy;/api/readypasses. API and execution image both use Stacksmith commite34e3d26287165e12a3f6653f74c2194a5634462. Execution-image discovery checks pass, and directory-layout dev/prod targets each completed apply, no-change plan, and destroy using their discovered runfiles.Core change: ci-sourcerer/stacksmith#17
Full authenticated GitHub onboarding/approval and real AWS deployment have not been exercised. No AWS resources were created.