Backend/Ops Project Green Test Pass — do not touch frontend visual lane

[AtomEons]

Orders

Use this issue as the execution/test lane for Orangebox Delta backend/Ops green proof.

Frontend visual tuning is owned by a separate chat. Do not modify frontend visual source, React components, CSS, mockup state behavior, or design/taste unless a build error requires a non-visual fix and the fix is explicitly minimal.

Repo

AtomEons/orangebox-delta

Current scope

Backend/Ops/API/AtomSmasher/project-green only.

Required commands

Run from repo root on the latest main:

npm install
npm run check
npm run build:web
node ./scripts/v4/frontend-dist-bridge.mjs
npm run build:api
node ./scripts/v4/package-script-doctor.mjs --json
npm run atomsmasher:api-smoke
npm run atomsmasher:doctor
npm run ops:readiness

If a command fails

1. Capture the exact failing command.
2. Capture the full relevant log.
3. Fix only the smallest unambiguous cause.
4. Commit each fix with a clear message.
5. Rerun the failing command.
6. Do not claim green unless the command passes.

Expected green boundary

Backend/Ops green means:

• root syntax checks pass
• frontend workspace can build, but visual perfection is not required here
• frontend build is bridgeable to backend static path via scripts/v4/frontend-dist-bridge.mjs
• API workspace builds
• package script doctor passes or reports concrete missing refs
• AtomSmasher API smoke passes
• AtomSmasher doctor passes or reports concrete runtime blockers
• ops readiness passes or reports concrete local-environment blockers

Change ledger

All fixes must be reflected in:

docs/DELTA_CHANGE_LEDGER_2026-05-28.md

Return format

When done, comment with:

1. Commands run
2. Pass/fail table
3. Files changed
4. Commit SHAs
5. Remaining blockers
6. Whether any frontend visual files were touched

Non-negotiable

No fake green. Receipts and logs decide.

[AtomEons]

Backend/Ops non-visual update — latest required test pass

Frontend visual work is now explicitly owned by a separate chat. This issue remains backend/Ops/API/AtomSmasher/project-green only.

New commits since issue creation

• 8021fe1 — Project Green CI: add dummy DATABASE_URL for Prisma generation.
• 22d2a5b — API: add minimal Vitest target for createId.
• f7ad9ec — Project Green CI: add manual trigger and API test execution.
• d1c65b8 — Ops Script Doctor CI: add manual trigger.
• 1c67d0d — Add non-visual pass addendum doc.
• 7eb8f0f — Add backend bridge from frontend/dist to apps/web/dist for legacy server static path.
• a748a7c — Add non-mutating package script reference doctor.
• f695dd3 — Add Ops Script Doctor CI.
• de15592 — Update change ledger with backend bridge + script doctor.

Run this exact sequence from repo root

npm install
npm run check
npm run build:web
node ./scripts/v4/frontend-dist-bridge.mjs
npm run build:api
npm run test:api
node ./scripts/v4/package-script-doctor.mjs --json
npm run atomsmasher:api-smoke
npm run atomsmasher:doctor
npm run ops:readiness

Boundary

Do not edit frontend/src/**, frontend CSS, state atlas visuals, mockup tuning, or visual taste in this backend/Ops pass. Building the frontend is allowed only as an integration prerequisite.

Report back with

1. Exact commands run
2. Pass/fail per command
3. First failing log if any
4. Files changed
5. Commit SHAs
6. Whether frontend visual files were touched
7. Remaining blockers

No fake green. Logs and receipts decide.

[AtomEons]

Follow-up fix for only red item

Local test report showed all substantive commands passed, with only package-script-doctor red due to a false-positive parse of .example.json from control:run.

I fixed the doctor parser here:

• 26b8615 — scripts/v4/package-script-doctor.mjs: require actual path separators for local refs and prevent .example.json false positives from filenames like MANIFEST.example.json.

Please rerun only:

node ./scripts/v4/package-script-doctor.mjs --json

Expected result:

PACKAGE_SCRIPT_REFS_GREEN
missing_count: 0

If that passes, backend/Ops is green by the provided local test sequence. Frontend visual perfection remains separate and owned by the visual chat.