[codex] add episteme reasoning workflow

[GTrunSec]

Summary

• Add the Episteme reasoning workflow surfaces for ontology review, Qianji scheduling, and live-model prompt audit artifacts.
• Add structural IDF and source patch scaffolding so private ontology evidence can be reviewed before RDF mutation.
• Extend Qianji activity wiring so episteme ontology reasoning is admitted through the workflow path instead of prompt-only handling.

Impact

This keeps ontology mutation behind review-only evidence and prepares the next slice: materializing source evidence into the Qianji LLM context for real private Episteme reasoning.

Validation

• Pre-commit hook passed during commit, including all-features cargo check/clippy coverage.
• Targeted package tests and clippy checks for xiuxian-wendao-episteme, xiuxian-wendao-studio, and xiuxian-qianji passed before the commit.
• Root worktree was clean before push.

[chatgpt-codex-connector]

💡 Codex Review

xiuxian-artisan-workshop/scripts/runtime/wendao-ai-launch.sh

Line 17 in 4e227f5

PORT="${WENDAO_AI_PORT:-9518}"

Use a distinct default port for wendao-ai

In the default process-compose configuration I checked, nix/modules/process.nix now starts both wendao-frontend and wendao-ai, while the existing frontend launch script already defaults to port 9518. This new default makes the normal runtime start two web dev servers on the same listener, so one service will fail to bind or the wendao-ai healthcheck can probe the frontend instead unless every operator overrides WENDAO_AI_PORT.

---

xiuxian-artisan-workshop/scripts/runtime/check_wendao_frontend_health.py

Line 13 in 4e227f5

is_frontend_healthy = is_runtime_web_healthy

Preserve the frontend health helper signature

For Python callers that import the compatibility helper directly, this alias changes is_frontend_healthy(...) from the previous frontend-specific signature to is_runtime_web_healthy(...), which requires a service_name keyword. Existing tests or external scripts that pass the old arguments now fail with TypeError before performing any healthcheck; wrap the shared helper with service_name="wendao-frontend" instead of aliasing it directly.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".