Skip to content

main#221

Closed
Shooksie wants to merge 11 commits intodevelopfrom
main
Closed

main#221
Shooksie wants to merge 11 commits intodevelopfrom
main

Conversation

@Shooksie
Copy link
Copy Markdown
Contributor

@Shooksie Shooksie commented Apr 5, 2026

Shooksie and others added 11 commits April 1, 2026 10:34
All agent profiles referenced `tool_profile: sparkcube` but this claude
profile was never defined in global config, causing every workflow to fail
at config validation. Removed all references so agents use default config.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…ck download

Implement production-quality GitHub registry support for pack marketplace with:
- GitHub URL parsing (HTTPS and SSH formats)
- GitHub token authentication via GITHUB_TOKEN environment variable
- GitHub-specific registry sync with optional token authentication
- Intelligent URL format detection for GitHub repositories
- Robust error handling with helpful error messages for private repos
- 10 comprehensive unit tests covering parsing, auth, and edge cases

New public API:
- parse_github_url() - Extract owner/repo from GitHub URLs
- get_github_token() - Retrieve GitHub token from environment
- sync_github_registry() - Sync GitHub registries with auth support
- GitHubUrlType enum - Distinguish between HTTPS and SSH URLs

Features:
- Automatic detection of GitHub URLs in sync_registry()
- Fallback to standard git-based sync for non-GitHub registries
- Lenient URL parsing supports extra path components
- Support for private repositories with GITHUB_TOKEN authentication
- Embedded credentials for HTTPS access

The implementation enables:
1. Adding GitHub repositories as pack registries: ao pack registry add --id myrepo --url https://github.com/owner/repo
2. Syncing registries with optional authentication: ao pack registry sync --id myrepo
3. Searching and installing packs from GitHub-hosted registries
4. Automatic token injection for private repository access

All tests pass (10/10), no existing tests broken, full backward compatibility maintained.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…eep schedule

glm-5/glm-5-turbo models don't exist — all research/review/provider agents
now use claude-haiku-4-5. pr-sweep schedule disabled (conductor dispatches).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Implement ao-memory MCP server integration for workflow phases:
- Add ao.memory MCP server definition to default workflow config
- Bind ao.memory to all standard workflow phases for context loading/saving
- Implement ao mcp memory command for memory context management
- Each phase now has pre-phase context load and post-phase memory save capability

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Rename the top-level sync command to cloud, moving all sync functionality
under the cloud command umbrella. This aligns with the product roadmap to
group cloud-related operations under a single command namespace.

- Rename SyncCommand to CloudCommand with all subcommands (setup, push, pull, status, link)
- Create cloud_types.rs and services/cloud.rs to replace sync_types.rs and sync.rs
- Update CLI routing in root_types.rs and main.rs
- Update services/mod.rs imports
- Update CLI documentation to reflect new command structure
- Remove old sync_types.rs and services/sync.rs files

Usage change: ao sync <cmd> -> ao cloud <cmd>
- Replace poisoned lock expect() with unwrap_or_else() for graceful recovery
- Fix agent_runtime_config tests to use load_or_default and isolated temp dirs
- Add HOME environment isolation to skill_scoping tests with env_lock guards
- Update workflow_config tests to use correct builtin workflow IDs
- Remove pack-specific phase assertions from unit tests

Resolves 14-16 pre-existing test failures from insufficient isolation.
Update standard-workflow and ui-ux-standard workflows to use feature branch
development with automatic PR creation. Implementation now follows:

1. Create feature branch worktree for isolated development
2. Implement changes on feature branch (not main)
3. After all phases succeed, push feature branch
4. Create pull request for review (auto_merge: false)
5. Cleanup worktree after manual merge

This workflow ensures:
- Code review via pull requests before main integration
- Main branch remains protected from direct pushes
- Worktrees are cleaned up automatically
- Feature isolation for safer concurrent task execution

Configuration includes:
- create_pr: true (automatic PR creation)
- auto_merge: false (require explicit merge)
- cleanup_worktree: true (automatic cleanup)
- target_branch: main (merge target)
- strategy: merge (standard git merge)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add ao cloud deploy create and destroy subcommands for managing
deployments on ao-cloud. Implements:

- Create deployment with app_name, region, and machine_size parameters
- Destroy deployment with validation to prevent app name mismatches
- Configuration persistence to .ao/deploy.json
- JSON output support for both commands
- Error handling for deployment lifecycle operations

Fly.io API integration scaffolded for future implementation.
Extend ao cloud deploy with three new subcommands:
- 'ao cloud deploy start' — start a created deployment
- 'ao cloud deploy stop' — stop a running deployment
- 'ao cloud deploy status' — show deployment state

Each subcommand validates the app_name matches configured deployment,
returns JSON output via ao.cli.v1 envelope, and supports human-readable
stderr output. Follows same pattern as existing create/destroy handlers.

Adds 4 parsing tests to cli_types/mod.rs to verify command parsing.
…ec, prototype AO as ACP server for IDE integration. Read the ACP specification, evaluate how AO CLI could expose an ACP interface so IDEs (VS Code, JetBrains, Cursor) can connect to AO as an agent provider. Create a design doc at docs/design/acp integration.md with: (1) ACP spec summary, (2) how AO maps to ACP concepts, (3) implementation plan, (4) competitive advantage. Small scope — research and design doc only, no implementation.): P2: ACP (Agent Client Protocol) evaluation — research the AC
@Shooksie
Copy link
Copy Markdown
Contributor Author

Shooksie commented Apr 5, 2026

Closing — rustfmt fix already landed on main via direct push. PR was incorrectly created against develop (vestigial branch).

@Shooksie Shooksie closed this Apr 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant