You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
4.`install_to_codex.ps1` copies the current package cleanly, including `package.json` and `package-lock.json`.
18
+
4.`install_to_codex.ps1` copies the current package cleanly.
19
19
5.`meta/excalidraw_report.json` is part of the output contract and the self-audit proves editable scene generation.
20
20
21
21
Recommended:
@@ -54,9 +54,7 @@ Recommended for higher-fidelity diagram rendering:
54
54
55
55
- Mermaid CLI (`@mermaid-js/mermaid-cli`)
56
56
57
-
The repo also ships a local Excalidraw bridge dependency through `package.json`.
58
-
59
-
Even without live LLM access, the proof path still works through `CODE_EXPLAINER_MOCK_LLM=true`. Even if the official Excalidraw bridge is browser-dependent in the local environment, the shipped deterministic fallback scene generator keeps the editable-diagram proof path working and records the downgrade in `meta/excalidraw_report.json`.
57
+
Even without live LLM access, the proof path still works through `CODE_EXPLAINER_MOCK_LLM=true`. The deterministic Excalidraw scene generator is now the default production path, so the repo does not need to ship the official bridge dependency in its default install surface. If a developer wants to experiment with the official bridge anyway, they can install it locally with `npm install --no-save @excalidraw/mermaid-to-excalidraw` and enable `--enable-official-excalidraw-bridge true`.
This copies the current skill package into `~/.codex/skills/code-explainer`. Restart Codex after installation, then run the skill runtime installer inside the installed copy if you need the local Node dependencies there.
91
+
This copies the current skill package into `~/.codex/skills/code-explainer`. Restart Codex after installation.
- The skill exports editable Excalidraw scenes from that Mermaid set.
132
-
-If the official Excalidraw bridge works in the local runtime, it is used directly.
133
-
-If the official bridge is browser-dependent or unavailable, the skill falls back to a deterministic local scene generator for the Mermaid subset it emits and records that downgrade in `meta/excalidraw_report.json`.
128
+
-The deterministic local scene generator is the default production path.
129
+
-The official Excalidraw bridge is opt-in only through `--enable-official-excalidraw-bridge true` and is intended for development experiments, not the default runtime.
- This skill does not mutate the analyzed repository.
130
133
- If the explanation-quality score is below the rubric threshold, treat the output as failed even if files were produced.
131
134
- If Excalidraw export is enabled, treat missing or partial editable scene generation as a real quality issue, not a cosmetic extra.
132
-
- When the official Excalidraw bridge is unavailable or browser-dependent in the local runtime, the skill falls back to a deterministic local scene generator for the Mermaid subset it emits and records that downgrade in `meta/excalidraw_report.json`.
135
+
- The deterministic local Excalidraw exporter is the canonical production path.
136
+
- The official `@excalidraw/mermaid-to-excalidraw` bridge is opt-in only via `--enable-official-excalidraw-bridge true` and should be treated as a development experiment, not a required runtime dependency.
133
137
- Use include/exclude globs to narrow analysis when the repository is very large or noisy.
0 commit comments