Update to APODICTIC Development Editor

{
  "description": "Codex-generated wrapper for APODICTIC's compatibility command surface. Use when the user explicitly asks for `apodictic-ready`, or when they say something like \"Is this ready to submit?\", or when they want submission readiness check — full diagnostic + verdict + query/synopsis assessment. This wrapper mirrors the legacy `/ready` behavior.\n",
  "included_files": [],
  "name": "apodictic-ready",
  "skill_md_contents": "---\nname: apodictic-ready\ndescription: >\n  Codex-generated wrapper for APODICTIC's compatibility command surface. Use when the user explicitly asks for `apodictic-ready`, or when they say something like \"Is this ready to submit?\", or when they want submission readiness check — full diagnostic + verdict + query/synopsis assessment. This wrapper mirrors the legacy `/ready` behavior.\nversion: 2.13.3\n---\n\n<!-- Generated by scripts/build-codex.mjs. Do not edit files in codex/ by hand. -->\n\n# APODICTIC Ready\n\nThis generated skill exposes the legacy `/ready` workflow in Codex without duplicating the shared APODICTIC runtime.\n\n## Load Order\n\n1. Read `../../commands/ready.md` as the canonical command behavior.\n2. Read `../core-editor/SKILL.md`.\n3. Load only the references, companion skills, and output rules that those source files call for.\n\n## Execution Notes\n\n- Preserve the command's routing, output, and resume behavior.\n- Skip redundant intake when router output or project state has already prefilled the needed context.\n- Follow the folder architecture in `../core-editor/references/output-structure.md` §Folder Architecture: rolling state at the project root, run artifacts in `runs/YYYY-MM-DD_{model}_{type}/`.\n"
}