Update to APODICTIC Development Editor

{
  "description": "Codex-generated wrapper for APODICTIC's compatibility command surface. Use when the user explicitly asks for `apodictic-pre-writing`, or when they say something like \"I have an idea but no manuscript yet.\", or when they want guide from idea to draftable structure (no manuscript required). This wrapper mirrors the legacy `/pre-writing` behavior.\n",
  "included_files": [],
  "name": "apodictic-pre-writing",
  "skill_md_contents": "---\nname: apodictic-pre-writing\ndescription: >\n  Codex-generated wrapper for APODICTIC's compatibility command surface. Use when the user explicitly asks for `apodictic-pre-writing`, or when they say something like \"I have an idea but no manuscript yet.\", or when they want guide from idea to draftable structure (no manuscript required). This wrapper mirrors the legacy `/pre-writing` 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 Pre Writing\n\nThis generated skill exposes the legacy `/pre-writing` workflow in Codex without duplicating the shared APODICTIC runtime.\n\n## Load Order\n\n1. Read `../../commands/pre-writing.md` as the canonical command behavior.\n2. Read `../pre-writing-pathway/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"
}