Repository navigation
feat(architecture): add minimal project bootstrap - #4
Merged
Merged
Conversation
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.
New projects could satisfy the general architecture advice while still accumulating independent behavior in entrypoints and the source root. Require a local placement and dependency contract before substantial implementation, with a verified guard for important boundaries.
Add a conditional project-bootstrap process with frontend, service, and library/CLI archetypes, exposed through prompt bootstrap and the existing connection routes. Keep CORE unchanged, preserve minimal-context routing, and keep connect/update restricted to rule files.
Validation: all seven tooling suites passed on Windows PowerShell 5.1 (975 assertions); hub validation and diff checks passed. An isolated connection fixture passed doctor and reported synchronized status. Integration tests cover explicit workflow selection, rendering, template seeding, and preservation of existing application code. Architectural examples were reviewed as design exercises; agent compliance on newly generated products has not been measured.