Handbook
Updating the Blueprints submodule
Commands and checks to move blueprints/ to a newer upstream commit — no methodology prose.
What it is
Commands and checks to move blueprints/ to a newer upstream commit — no methodology prose.
When to use it
Use this guide on a schedule, after upstream fixes, or when you need a feature that landed in autowww/blueprints.
Prerequisites
blueprints/is a git submodule at the repository root (not a stray copy without git metadata).- You have permission to commit submodule pointer updates on your default branch.
Choose a topic
| Topic | Page |
|---|---|
| Routine bump — fetch, pull, commit pointer | Routine bump |
Validate and test — CI, check, frozen tree |
Validate and test |
| Recovery — lifecycle, rollback, conflicts | Recovery and rollback |
Quick flow: routine → validate → if anything fails, recovery and Troubleshooting.
Update lifecycle (visual)
What to do next
- Blueprint policy — when you may change files under
blueprints/vs project space. - Troubleshooting and FAQ — common submodule and path issues.