Import standalone Agent API Core from Parsar

[SaladDay]

Purpose

Copy Agent API Core into this standalone repository from MiniMax-AI-Dev/parsar@72ab4d37d49245f15b63d34f5741780e540bcec0. Parsar keeps its product/business code and its existing Core copy unchanged.

Includes the complete API service, pinned protocol, migrations, execution daemon, Docker/E2B providers, existing Harness adapters, native helpers, client, tests and runtime builders. Product Web/server/database/CLI/deployment are excluded. Execution sources and contracts retain their original bytes; only five imported dependency/release-document files are adapted for independent packaging. Root tooling and CI support standalone development.

Validation

• make check passed on Linux with a dedicated PostgreSQL 16 database.
• Standalone API and daemon builds passed.
• Pinned official SDK/raw HTTP suite passed against both the binary and a read-only container.
• Standalone release archive built from committed source.
• Actionlint and import provenance audit passed (1,287 imported files; 1,282 byte-identical).
• Native paid-model/E2B acceptance was not rerun; this copy does not expand protocol coverage.

See provenance/README.md for the boundary and provenance/verification.md for commands, evidence hashes and limits.

Independent review

Blind review of 419ca3c against empty baseline 6973875 found no in-scope blockers. The reviewer independently checked import completeness, file permissions, product dependency boundaries, documentation links, API/daemon builds and protocol/client tests, and verified the recorded Linux evidence hashes. An existing reviewer was reused after the subagent creation limit rejected a fresh reviewer; it received requirements, boundaries and baselines only, without implementation guidance.

Merge-time CI status

The core-check (full make check plus daemon build), agents-api and actionlint workflows passed on 419ca3c. The agents-harness runner failed with System.IO.IOException: No space left on device in the runner diagnostic log; native Harness CI did not complete. The executor native build was still running at merge preparation. These are not reported as passed. No execution code was changed to suppress the failure; the source-copy, independent review and standalone validation evidence above remains the basis for this user-requested merge.