chore: sync main into development - #1262
Conversation
* update readme update readme contents, link v2 specs, and add new banner * Update README.md * Update README.md
ITS-1231: Assign PR reviews to foundations team.
Greptile SummaryThis PR syncs three changes from
Confidence Score: 5/5Safe to merge — all changes are documentation, asset, and configuration updates with no logic or protocol changes. The PR touches only the README, CODEOWNERS, an SVG banner, and LFS pointer normalization for diagram PNGs. All new README links were verified to point to existing files. The SVG contains only static vector paths with no scripts or external fetches. No spec logic is altered. No files require special attention. Important Files Changed
|
|
Superseded by #1263, which resolves the asset relocation and README conflicts on an integration branch based on development. |
Summary
Sync the latest changes from
mainintodevelopment, including:This keeps the long-lived
developmentbranch aligned withmain.Merge strategy
Use a regular merge commit to preserve branch ancestry and simplify future
main→developmentsynchronizations.