Repository navigation
Prepare OpenSymphony 3.0.0 documentation and version metadata - #249
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fbfea68013
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 70a5aa63b0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. Delightful! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
1 participant
Summary
OpenSymphony now has a short entry path for the multi-repository and ACP capabilities added in M12.97 and M12.99. The README points new operators to focused guides; the guides explain repository labels, parent integration, ACP profiles, operator decisions, recovery, rollout, and the 3.0 upgrade path. The architecture diagram includes ACP and central project routing.
Set the root crate, desktop package, Tauri metadata, and lockfiles to 3.0.0. The release guide records the validation boundary for multi-repository rollout and ACP live qualification.
Evidence
cargo fmt --checkcargo clippy --all-targets -- -D warningsTMPDIR=/private/tmp cargo test(full bundled-mode suite; canonical temp path avoids macOS/varsymlink fixture failures)npm run build --workspace=@opensymphony/gateway-schemanpm run type-checknpm run build --workspace=@opensymphony/desktopnpm run package:release --workspace=@opensymphony/desktop -- --dry-run(version 3.0.0 parity)git diff --checkThis PR targets
develop. A follow-up release PR will bring the validated 3.0.0 candidate, including the completed M12.97 and M12.99 work, intomain.