Rename the repository to OpenAgentCore

[SaladDay]

The GitHub repository is now MiniMax-AI/OpenAgentCore, and the old URL redirects. This PR renames the in-repository identities that were waiting for the repository rename.

Mapping

Old	New
github.com/MiniMax-AI/parsar-core	github.com/MiniMax-AI/OpenAgentCore
Go module github.com/MiniMax-AI-Dev/parsar (plus the nested microsandbox-provider module)	github.com/MiniMax-AI/OpenAgentCore
services/agents-api/	services/core/
services/core-console/	services/web/
apps/parsar-daemon/, cmd/parsar-daemon/	apps/daemon/, cmd/oac-daemon/
scripts/build-agents-api{,-image,-release}.sh, build-core-console.sh, agents-api-subagents-acceptance.py	scripts/build-core{,-image,-release}.sh, build-web.sh, core-subagents-acceptance.py
npm parsar-core, @agents-core-web/{web,agents-client}, @parsar/claude-sdk-adapter, parsar-mcode-harness	openagentcore, @oac/{web,agents-client}, @oac/claude-sdk-adapter, @oac/mcode-harness
Make targets build-agents-api*, check-agents-api*, docker-build-agents-api	build-core*, check-core*, docker-build-core

GitHub job names are unchanged. Directories are moved with git mv, so history follows.

Unchanged

• example/: everything except the client package name (8 lines, @agents-core-web/agents-client → @oac/agents-client). The Parsar example keeps its naming.
• Links to the separate product Parsar: provenance/ and upstream github.com/MiniMax-AI-Dev/parsar links (pull requests and source records).
• Historical data: packages/agents-client/src/fixtures/parsar-* and landed SQL migrations.
• Other names: contracts/agents-api (the OpenAI Agents API contract), x_agents_core, the agents_api database and role, and X-Core-Console-Actor.

scripts/name-allowlist.json no longer exempts the old repository URL, module path, directories, build scripts or npm names, so check-names rejects them from now on.

Nothing installed or persisted compares the repository URL or a moved path on upgrade or convert. Release candidates built before the GitHub rename recorded the old artifact_base_url; promote-qualified-release.py rejects them, so rebuild them.

Verification

• Full server gate: passed (exit 0) on the rename rebased onto a5f9e47.
  • The Playwright browser cases were skipped: test:web:acceptance and the example's test:e2e (no Chrome on the server). Web and example typecheck, unit tests and builds ran.
  • Earlier gate failures came from the gate environment, not this change: a stale PARSAR_OFFICIAL_SDK_PYTHON export, which the daemon now rejects, and example e2e without Chrome.
• After the final rebase onto 9f972ac (docs-only and text-only changes on main): make check-names check-distribution check-docs check-harness-catalog, config-reference.py --check, pnpm install --frozen-lockfile, pnpm typecheck and go build for both modules.
• Generated outputs: sqlc, OpenAPI and the harness catalog regenerate with no diff.

Review

A fresh Claude subagent did a blind review of the complete diff. It received only the requirements, the exclusions, the checkout and the baseline.

• P0: none.
• P1: pinned apps/docs guide links point to moved paths. Not fixed: apps/docs is deleted by the follow-up PR.
• P2/P3, fixed:
  • the core-doctor allowlist reason;
  • make help alignment;
  • five edge cases in the rename script (package-name-only matching, upstream links, migrations limited to *.sql, symlink arguments, refusing to run when files remain under old directories).

These fixes, and the example import change, were checked with focused tests and the name guard, without another review round.

Other branches

Rebase, then run apply-rename.py [--check] [PATH ...] on the files you changed. It is idempotent and skips the exclusions above. The script lives outside the repository and is shared with the other sessions.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}