AlembicTest

AlembicTest is the dedicated verification workspace for Alembic real-link testing inside AlembicWorkspace. It stores test scripts, reusable test configuration, reproduction notes, monitoring records, and validation evidence.

This repository is shared by two Codex responsibility windows:

• AlembicTest-IDE: Codex Plugin, Codex host MCP, Codex session / local environment, installed / packaged Plugin runtime smoke, and direct-thread / IDE delivery readback tests.
• AlembicTest: real BiliDili / AlembicWorkspace cold-start, rescan, after-run, AI/provider, Dashboard observation, runtime monitoring, and real project regression tests.

Current AlembicTest real-project verification targets include both AlembicWorkspace and BiliDili. AlembicWorkspace is used for Alembic self-hosting and multi-root ProjectScope integration checks; BiliDili remains the real iOS/Swift business project target. Select the target from the user request or the active control test order. Product fixes belong in the owning Alembic or BiliDili repository, not in this test workspace.

Boundaries

• Do not copy Alembic product implementation into this repository.
• Do not store API keys, cookies, tokens, login state, device IDs, or local private runtime data here.
• Do not treat BiliDili as a disposable fixture or modify its product behavior for test convenience.
• Do not treat AlembicWorkspace as disposable test data; when it is the target, keep workspace control docs, source folders, and ProjectScope bindings within the explicit test order.
• Destructive test operations require explicit user or state-root test-card authorization.
• Do not use AlembicPlugin's Codex MCP reload command as a repair path for the current Codex host MCP session. AlembicTest-IDE may collect fresh MCP probe evidence only when the active test order asks for it; AlembicTest must not run plugin/environment smoke. Live host MCP refresh belongs to AlembicPlugin plus a Codex restart/refresh.
• The default restart flow performs a clean-environment preflight: stop existing Alembic daemons / stale AlembicTest monitors, then clear old Alembic runtime logs. It does not delete databases, candidates, settings, secrets, or project source files.

Layout

AlembicTest/
├── AGENTS.md
├── config/
├── docs/
├── scripts/
└── tmp/

Common Commands

Start with the safe self-check path when closing documentation or script changes. These commands print script help or planned actions only; they do not start Alembic, probe AlembicWorkspace or BiliDili, monitor a cold start, or clean runtime logs.

Run from the workspace root:

npm --prefix AlembicTest run check
npm --prefix AlembicTest run tmp:retention -- --max-age-days 0
node AlembicTest/scripts/restart-alembic.mjs --dry-run

Or from this repository:

npm run check
npm run tmp:retention -- --max-age-days 0
node scripts/restart-alembic.mjs --dry-run

The commands below are authorized test paths. Use restart / monitor commands only when the user request or active state-root test card explicitly asks AlembicTest to restart, monitor, or probe a real project flow. Use Codex MCP probe commands only when the user request or active state-root test card explicitly assigns AlembicTest-IDE to collect Plugin / host environment evidence. Pass --project AlembicWorkspace or --project BiliDili when the target matters; the configured defaultProject is only a CLI fallback for legacy commands.

Run from the workspace root:

npm --prefix AlembicTest run restart
npm --prefix AlembicTest run restart:monitor
npm --prefix AlembicTest run monitor
npm --prefix AlembicTest run monitor:watch
node AlembicTest/scripts/probe-codex-prime.mjs
node AlembicTest/scripts/probe-resident-vector-search.mjs
node AlembicTest/scripts/probe-unified-resident-service.mjs --phase baseline
node AlembicTest/scripts/probe-unified-resident-service.mjs --phase resident

These probe commands launch fresh MCP runtimes for evidence. They do not prove the currently running Codex host MCP session has reloaded Plugin code. Do not pass Plugin reload --stop-mcp / watch --restart-mcp from either test window unless the active state-root test card explicitly authorizes breaking the current host MCP session and restarting Codex afterward.

Or from this repository:

npm run restart
npm run restart:monitor
npm run monitor
npm run monitor:watch
node scripts/probe-codex-prime.mjs
node scripts/probe-resident-vector-search.mjs
node scripts/probe-unified-resident-service.mjs --phase baseline
node scripts/probe-unified-resident-service.mjs --phase resident

scripts/restart-alembic.mjs may need elevated Codex sandbox permissions because Alembic writes local runtime-control state under the user's home directory when registering the active runtime.