[codex] Align file runtime and CDE production readiness

[ActiveInAI]

Summary

• Align frontend requested file extensions with the native/lightweight display set requested by the owner, including legacy Office, audio, AVI/MKV, GIF, JPEG, GLB, and STEL.
• Add frontend and backend contract tests that lock the requested CAD/BIM/mesh/Office/media/image/PDF set to real registry routes.
• Keep STEL fail-closed behind a licensed adapter boundary instead of treating it as STEP/IGES or generating fake geometry.
• Bridge module file operations to the backend CDE API and persist module CDE files in the Postgres runtime store.
• Add a repository-level production readiness gate covering module registry drift, retired identity files, generated artifact leakage, production env requirements, file runtime parity, frontend/backend CDE bridge, backend CDE persistence, shell script syntax, and existing Phase 8 readiness smoke.
• Document the production readiness entrypoint and add IFCDB-Agent production environment variables.

Validation

• 04-backend/scripts/smoke-production-readiness-all.sh
• python3 tools/production_readiness_contract.py
• python3 -m unittest tools/test_production_readiness_contract.py
• bun run test
• bun run typecheck
• bun run lint
• bun run build
• cargo fmt --check
• cargo test -p architoken-harness-core file_runtime_registry
• cargo test -p architoken-harness-core
• cargo check -p architoken-harness-core
• cargo build --release -p architoken-harness-core --bin architoken-gateway
• Local runtime smoke: /v1/runtime/capabilities reports no missing requested formats; all 14 /app/modules/{moduleId} routes return 200; /app/digital-twin returns 404.