@litfamily/litcodex 1.0.30 → 1.0.31
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README-Ko-KR.md +11 -11
- package/README.md +11 -11
- package/dist/install/generated-skill-payload-hashes.d.ts +188 -82
- package/dist/install/generated-skill-payload-hashes.js +188 -82
- package/dist/install/skill-catalog.d.ts +1 -1
- package/dist/install/skill-catalog.js +12 -1
- package/dist/install/skill-resource-hashes.d.ts +1 -1
- package/dist/install/skill-resource-hashes.js +1 -1
- package/marketplace/plugins/litcodex/.codex-plugin/plugin.json +1 -1
- package/marketplace/plugins/litcodex/components/auto-update/package.json +1 -1
- package/marketplace/plugins/litcodex/components/comment-checker/package.json +1 -1
- package/marketplace/plugins/litcodex/components/git-bash/package.json +1 -1
- package/marketplace/plugins/litcodex/components/lit-loop/directive.md +10 -4
- package/marketplace/plugins/litcodex/components/lit-loop/directives/lit-adhd.md +191 -0
- package/marketplace/plugins/litcodex/components/lit-loop/directives/lit-handoff.md +2 -0
- package/marketplace/plugins/litcodex/components/lit-loop/directives/lit-hijack.md +219 -0
- package/marketplace/plugins/litcodex/components/lit-loop/directives/lit-recap.md +2 -0
- package/marketplace/plugins/litcodex/components/lit-loop/directives/lit-schematic.md +199 -0
- package/marketplace/plugins/litcodex/components/lit-loop/directives/litwork.md +2 -1
- package/marketplace/plugins/litcodex/components/lit-loop/dist/adhd-suggest.d.ts +10 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/adhd-suggest.js +67 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/card-html.d.ts +1 -1
- package/marketplace/plugins/litcodex/components/lit-loop/dist/card-html.js +128 -8
- package/marketplace/plugins/litcodex/components/lit-loop/dist/card-looks.d.ts +19 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/card-looks.js +58 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/card-status.d.ts +27 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/card-status.js +94 -7
- package/marketplace/plugins/litcodex/components/lit-loop/dist/cli.js +13 -3
- package/marketplace/plugins/litcodex/components/lit-loop/dist/codex-hook.d.ts +2 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/codex-hook.js +8 -9
- package/marketplace/plugins/litcodex/components/lit-loop/dist/control-chars.d.ts +5 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/control-chars.js +23 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/hook-cli.d.ts +8 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/hook-cli.js +118 -11
- package/marketplace/plugins/litcodex/components/lit-loop/dist/hud.d.ts +1 -1
- package/marketplace/plugins/litcodex/components/lit-loop/dist/hud.js +29 -13
- package/marketplace/plugins/litcodex/components/lit-loop/dist/lane-events.d.ts +13 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/lane-events.js +85 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/lane-state.d.ts +55 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/lane-state.js +227 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/live-step.d.ts +5 -1
- package/marketplace/plugins/litcodex/components/lit-loop/dist/live-step.js +17 -1
- package/marketplace/plugins/litcodex/components/lit-loop/dist/markers.d.ts +6 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/markers.js +6 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/modes.d.ts +1 -1
- package/marketplace/plugins/litcodex/components/lit-loop/dist/modes.js +25 -1
- package/marketplace/plugins/litcodex/components/lit-loop/dist/motion-gate.d.ts +79 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/motion-gate.js +310 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/motion-route.js +5 -1
- package/marketplace/plugins/litcodex/components/lit-loop/dist/plan-persistence.js +10 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/redaction.js +18 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/reentry.d.ts +15 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/reentry.js +46 -9
- package/marketplace/plugins/litcodex/components/lit-loop/dist/rewind-cli.d.ts +10 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/rewind-cli.js +88 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/rewind-go.d.ts +20 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/rewind-go.js +84 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/rewind-look.d.ts +6 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/rewind-look.js +41 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/rewind-redact.d.ts +3 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/rewind-redact.js +40 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/rewind-rollout.d.ts +48 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/rewind-rollout.js +292 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/rewind.d.ts +162 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/rewind.js +773 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/route-heads.js +44 -2
- package/marketplace/plugins/litcodex/components/lit-loop/dist/run-panel.js +1 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/schematic-route.d.ts +6 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/schematic-route.js +35 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/screen-card.d.ts +3 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/screen-card.js +15 -5
- package/marketplace/plugins/litcodex/components/lit-loop/dist/skill-mention-scope.js +6 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/stack-hook.d.ts +8 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/stack-hook.js +57 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/statusline.js +8 -3
- package/marketplace/plugins/litcodex/components/lit-loop/dist/threads.d.ts +50 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/threads.js +178 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/trigger.d.ts +1 -1
- package/marketplace/plugins/litcodex/components/lit-loop/dist/trigger.js +29 -5
- package/marketplace/plugins/litcodex/components/lit-loop/dist/workflow-map.d.ts +10 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/workflow-map.js +11 -1
- package/marketplace/plugins/litcodex/components/lit-loop/dist/workflow-stack.d.ts +132 -0
- package/marketplace/plugins/litcodex/components/lit-loop/dist/workflow-stack.js +488 -0
- package/marketplace/plugins/litcodex/components/lit-loop/package.json +1 -1
- package/marketplace/plugins/litcodex/components/lsp/package.json +1 -1
- package/marketplace/plugins/litcodex/components/rules/package.json +1 -1
- package/marketplace/plugins/litcodex/components/start-work-continuation/dist/codex-hook.d.ts +6 -0
- package/marketplace/plugins/litcodex/components/start-work-continuation/dist/codex-hook.js +65 -0
- package/marketplace/plugins/litcodex/components/start-work-continuation/package.json +1 -1
- package/marketplace/plugins/litcodex/components/telemetry/package.json +1 -1
- package/marketplace/plugins/litcodex/components/wikify-knowledge/package.json +1 -1
- package/marketplace/plugins/litcodex/hooks/hooks.json +24 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/SKILL.md +6 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/kit/components.css +414 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/kit/fonts.json +22 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/kit/layouts/landing.html +164 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/kit/layouts/settings.html +114 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/kit/layouts/workspace.html +115 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/kit/styles/computational-brutalism.json +227 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/kit/styles/field-notes.json +205 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/kit/styles/graphite.json +200 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/kit/styles/meadow.json +199 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/kit/styles/neo-brutalism.json +222 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/kit/ui.js +228 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/references/brand-and-imagery.md +1 -1
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/references/complete-contract.md +1 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/references/craft-floor.md +2 -2
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/references/default-editorial-pixel.json +15 -8
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/references/design-choice.md +19 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/references/house-styles.md +235 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/references/motion-guide.md +2 -2
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/references/probe-and-review.md +6 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/references/production-interview.md +2 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/references/slop-register.md +4 -4
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/scripts/design-lock.mjs +400 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/scripts/lock-probe.mjs +196 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/scripts/page-probe.mjs +22 -4
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/scripts/pixel-art.mjs +60 -0
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/scripts/probe.mjs +59 -13
- package/marketplace/plugins/litcodex/skills/frontend-ui-ux/scripts/rule-data.mjs +38 -4
- package/marketplace/plugins/litcodex/skills/lit-adhd/SKILL.md +181 -0
- package/marketplace/plugins/litcodex/skills/lit-adhd/agents/openai.yaml +6 -0
- package/marketplace/plugins/litcodex/skills/lit-adhd/references/card-examples.md +147 -0
- package/marketplace/plugins/litcodex/skills/lit-adhd/references/status-taxonomy.md +37 -0
- package/marketplace/plugins/litcodex/skills/lit-diagram-drawer/SKILL.md +18 -7
- package/marketplace/plugins/litcodex/skills/lit-diagram-drawer/references/style-guide.md +20 -11
- package/marketplace/plugins/litcodex/skills/lit-diagram-drawer/references/type-architecture.md +3 -3
- package/marketplace/plugins/litcodex/skills/lit-diagram-drawer/references/type-dependency.md +1 -1
- package/marketplace/plugins/litcodex/skills/lit-diagram-drawer/references/type-swimlane.md +1 -1
- package/marketplace/plugins/litcodex/skills/lit-diagram-drawer/references/type-tree-block-decomposition.md +1 -1
- package/marketplace/plugins/litcodex/skills/lit-diagram-drawer/references/type-tree.md +3 -3
- package/marketplace/plugins/litcodex/skills/lit-diagram-drawer/references/type-wardley.md +1 -1
- package/marketplace/plugins/litcodex/skills/lit-diagram-drawer/references/verifier-guide.md +1 -0
- package/marketplace/plugins/litcodex/skills/lit-diagram-drawer/scripts/diagram-craft-rules.mjs +1 -2
- package/marketplace/plugins/litcodex/skills/lit-diagram-drawer/scripts/visual-quality.mjs +1 -2
- package/marketplace/plugins/litcodex/skills/lit-docx/SKILL.md +12 -3
- package/marketplace/plugins/litcodex/skills/lit-docx/references/direction-step.md +6 -3
- package/marketplace/plugins/litcodex/skills/lit-hijack/SKILL.md +449 -0
- package/marketplace/plugins/litcodex/skills/lit-hijack/agents/openai.yaml +6 -0
- package/marketplace/plugins/litcodex/skills/lit-hijack/references/capture-and-provenance.md +100 -0
- package/marketplace/plugins/litcodex/skills/lit-hijack/references/clean-room-build.md +111 -0
- package/marketplace/plugins/litcodex/skills/lit-hijack/references/distil-and-licence.md +102 -0
- package/marketplace/plugins/litcodex/skills/lit-hijack/references/gap-and-port-design.md +125 -0
- package/marketplace/plugins/litcodex/skills/lit-hijack/references/parity-and-report.md +108 -0
- package/marketplace/plugins/litcodex/skills/lit-hijack/scripts/hijack.mjs +1050 -0
- package/marketplace/plugins/litcodex/skills/lit-loop/SKILL.md +13 -4
- package/marketplace/plugins/litcodex/skills/lit-plan/SKILL.md +6 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/NOTICE +1 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/SKILL.md +35 -8
- package/marketplace/plugins/litcodex/skills/lit-pptx/fonts/jetbrains-mono/JetBrainsMono-Bold.ttf +0 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/fonts/jetbrains-mono/JetBrainsMono-Regular.ttf +0 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/fonts/jetbrains-mono/OFL.txt +93 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/fonts/jetbrains-mono/SOURCE.md +21 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/anti-slop-checklist.md +5 -2
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/authoring-guide.md +3 -4
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/density-and-fill.md +20 -6
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/direction-step.md +26 -8
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/examples/14-engineering-review-computational-brutalism-ko.md +173 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/examples/15-launch-pitch-neo-brutalism-ko.md +154 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/examples/16-design-lecture-bauhaus-ko.md +139 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/examples/17-community-programme-riso-ko.md +158 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/examples/18-public-data-briefing-newsroom-ko.md +179 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/layout-families.md +42 -27
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/title-treatments.md +31 -27
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/tonalities/bauhaus.md +136 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/tonalities/chalk.md +1 -1
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/tonalities/computational-brutalism.md +145 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/tonalities/neo-brutalism.md +155 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/tonalities/newsroom.md +141 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/tonalities/riso.md +133 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/tonalities/signal.md +1 -1
- package/marketplace/plugins/litcodex/skills/lit-pptx/references/tonalities/studio.md +1 -1
- package/marketplace/plugins/litcodex/skills/lit-pptx/scripts/compile-deck.js +1 -1
- package/marketplace/plugins/litcodex/skills/lit-pptx/scripts/craft_extras.py +136 -94
- package/marketplace/plugins/litcodex/skills/lit-pptx/scripts/embed_fonts.py +13 -1
- package/marketplace/plugins/litcodex/skills/lit-pptx/scripts/lib/grid-resolver.js +101 -110
- package/marketplace/plugins/litcodex/skills/lit-pptx/scripts/lib/layout-resolver.js +9 -15
- package/marketplace/plugins/litcodex/skills/lit-pptx/scripts/lib/render-pack.js +386 -579
- package/marketplace/plugins/litcodex/skills/lit-pptx/scripts/lib/slide-grid.js +104 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/scripts/lib/template-registry.js +57 -6
- package/marketplace/plugins/litcodex/skills/lit-pptx/scripts/office-run.mjs +2 -1
- package/marketplace/plugins/litcodex/skills/lit-pptx/scripts/qa_deck.py +7 -13
- package/marketplace/plugins/litcodex/skills/lit-pptx/scripts/render_pages.py +124 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/atlas/pack.yaml +1 -1
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/bauhaus/pack.yaml +98 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/chalk/pack.yaml +1 -1
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/computational-brutalism/pack.yaml +100 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/gazette/pack.yaml +1 -1
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/ledger/pack.yaml +1 -1
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/neo-brutalism/pack.yaml +107 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/newsroom/pack.yaml +99 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/night/pack.yaml +1 -1
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/paper/pack.yaml +1 -1
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/riso/pack.yaml +99 -0
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/signal/pack.yaml +2 -2
- package/marketplace/plugins/litcodex/skills/lit-pptx/templates/tonalities/studio/pack.yaml +1 -1
- package/marketplace/plugins/litcodex/skills/lit-recap/SKILL.md +2 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/SKILL.md +198 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/agents/openai.yaml +6 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/examples/iso-heat-exchanger/build.mjs +38 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/examples/iso-heat-exchanger/scene.mjs +133 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/examples/journal-adsorption-rig/build.mjs +87 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/examples/pid-dosing-skid/build.mjs +85 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/references/cutaway-outputs.md +70 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/references/isometric-craft.md +101 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/references/journal-figures.md +72 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/references/kit-api.md +134 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/references/pfd-and-layout.md +53 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/references/pid-drafting.md +103 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/references/pid-symbols.md +163 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/references/verification.md +100 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/doctor.mjs +57 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/figure.mjs +81 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/fonts.mjs +28 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/geom.mjs +113 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/interactive.mjs +292 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/isa.mjs +115 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/iso.mjs +719 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/legend-sheet.mjs +162 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/pid.mjs +937 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/png.mjs +132 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/qa-core.mjs +658 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/route.mjs +218 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/sheet.mjs +890 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/svg.mjs +82 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/lib/theme.mjs +115 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/motion.mjs +129 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/qa.mjs +92 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/render.mjs +233 -0
- package/marketplace/plugins/litcodex/skills/lit-schematic/scripts/scaffold.mjs +60 -0
- package/marketplace/plugins/litcodex/skills/lit-scientific-visualization/SKILL.md +34 -8
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/SKILL.md +18 -14
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/THIRD_PARTY_NOTICES +12 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/assets.mjs +388 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/blender/runner.py +221 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/blender.mjs +132 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/board.mjs +142 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/constants.mjs +6 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/cover-assets.mjs +7 -4
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/cover-capture.mjs +8 -7
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/cover-init.js +14 -2
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/cover-treatment.mjs +38 -3
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/cover.mjs +19 -4
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/driver.mjs +8 -8
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/gallery.mjs +147 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/house.mjs +45 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/image.mjs +89 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/look.mjs +58 -25
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/runtime.mjs +59 -14
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/safe-read.mjs +32 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/scaffold.mjs +208 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/score.mjs +668 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/sound.mjs +174 -31
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/stage-gate.mjs +45 -3
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/stage-kit.js +99 -1
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/stage-qa.js +8 -1
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/stage-qa.mjs +180 -11
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/stage-render.mjs +42 -12
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/stage-worker.mjs +7 -4
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/stage.mjs +96 -10
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/styles.mjs +233 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/treatment.mjs +291 -14
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/vendor/three/LICENSE +21 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/vendor/three/addons/environments/RoomEnvironment.js +144 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/vendor/three/addons/geometries/RoundedBoxGeometry.js +155 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/engine/vendor/three/three.module.js +54571 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/recipes/hero-3d/expected.json +33 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/recipes/hero-3d/index.html +139 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/references/cover.md +44 -7
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/references/depth.md +156 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/references/design-choice.md +22 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/references/quality-gate.md +29 -7
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/references/runtime.md +1 -1
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/references/sound.md +87 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/references/stage.md +19 -7
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/references/studio.md +246 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/references/style-bibles.md +2 -2
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/references/treatment.md +41 -21
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/scripts/render.mjs +51 -4
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/styles/paper.json +185 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/styles/swiss-signal.json +188 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/styles/terminalcore.json +182 -0
- package/marketplace/plugins/litcodex/skills/lit-typographic-motion/styles/tidal.json +187 -0
- package/marketplace/plugins/litcodex/skills/litresearch/SKILL.md +7 -0
- package/marketplace/plugins/litcodex/skills/litwork/SKILL.md +2 -1
- package/marketplace/plugins/litcodex/skills/readme-studio/SKILL.md +10 -0
- package/marketplace/plugins/litcodex/skills/review-work/SKILL.md +7 -1
- package/marketplace/plugins/litcodex/skills/start-work/SKILL.md +10 -0
- package/node_modules/@litcodex/lit-loop/directive.md +10 -4
- package/node_modules/@litcodex/lit-loop/directives/lit-adhd.md +191 -0
- package/node_modules/@litcodex/lit-loop/directives/lit-handoff.md +2 -0
- package/node_modules/@litcodex/lit-loop/directives/lit-hijack.md +219 -0
- package/node_modules/@litcodex/lit-loop/directives/lit-recap.md +2 -0
- package/node_modules/@litcodex/lit-loop/directives/lit-schematic.md +199 -0
- package/node_modules/@litcodex/lit-loop/directives/litwork.md +2 -1
- package/node_modules/@litcodex/lit-loop/dist/adhd-suggest.d.ts +10 -0
- package/node_modules/@litcodex/lit-loop/dist/adhd-suggest.js +67 -0
- package/node_modules/@litcodex/lit-loop/dist/card-html.d.ts +1 -1
- package/node_modules/@litcodex/lit-loop/dist/card-html.js +128 -8
- package/node_modules/@litcodex/lit-loop/dist/card-looks.d.ts +19 -0
- package/node_modules/@litcodex/lit-loop/dist/card-looks.js +58 -0
- package/node_modules/@litcodex/lit-loop/dist/card-status.d.ts +27 -0
- package/node_modules/@litcodex/lit-loop/dist/card-status.js +94 -7
- package/node_modules/@litcodex/lit-loop/dist/cli.js +13 -3
- package/node_modules/@litcodex/lit-loop/dist/codex-hook.d.ts +2 -0
- package/node_modules/@litcodex/lit-loop/dist/codex-hook.js +8 -9
- package/node_modules/@litcodex/lit-loop/dist/control-chars.d.ts +5 -0
- package/node_modules/@litcodex/lit-loop/dist/control-chars.js +23 -0
- package/node_modules/@litcodex/lit-loop/dist/hook-cli.d.ts +8 -0
- package/node_modules/@litcodex/lit-loop/dist/hook-cli.js +118 -11
- package/node_modules/@litcodex/lit-loop/dist/hud.d.ts +1 -1
- package/node_modules/@litcodex/lit-loop/dist/hud.js +29 -13
- package/node_modules/@litcodex/lit-loop/dist/lane-events.d.ts +13 -0
- package/node_modules/@litcodex/lit-loop/dist/lane-events.js +85 -0
- package/node_modules/@litcodex/lit-loop/dist/lane-state.d.ts +55 -0
- package/node_modules/@litcodex/lit-loop/dist/lane-state.js +227 -0
- package/node_modules/@litcodex/lit-loop/dist/live-step.d.ts +5 -1
- package/node_modules/@litcodex/lit-loop/dist/live-step.js +17 -1
- package/node_modules/@litcodex/lit-loop/dist/markers.d.ts +6 -0
- package/node_modules/@litcodex/lit-loop/dist/markers.js +6 -0
- package/node_modules/@litcodex/lit-loop/dist/modes.d.ts +1 -1
- package/node_modules/@litcodex/lit-loop/dist/modes.js +25 -1
- package/node_modules/@litcodex/lit-loop/dist/motion-gate.d.ts +79 -0
- package/node_modules/@litcodex/lit-loop/dist/motion-gate.js +310 -0
- package/node_modules/@litcodex/lit-loop/dist/motion-route.js +5 -1
- package/node_modules/@litcodex/lit-loop/dist/plan-persistence.js +10 -0
- package/node_modules/@litcodex/lit-loop/dist/redaction.js +18 -0
- package/node_modules/@litcodex/lit-loop/dist/reentry.d.ts +15 -0
- package/node_modules/@litcodex/lit-loop/dist/reentry.js +46 -9
- package/node_modules/@litcodex/lit-loop/dist/rewind-cli.d.ts +10 -0
- package/node_modules/@litcodex/lit-loop/dist/rewind-cli.js +88 -0
- package/node_modules/@litcodex/lit-loop/dist/rewind-go.d.ts +20 -0
- package/node_modules/@litcodex/lit-loop/dist/rewind-go.js +84 -0
- package/node_modules/@litcodex/lit-loop/dist/rewind-look.d.ts +6 -0
- package/node_modules/@litcodex/lit-loop/dist/rewind-look.js +41 -0
- package/node_modules/@litcodex/lit-loop/dist/rewind-redact.d.ts +3 -0
- package/node_modules/@litcodex/lit-loop/dist/rewind-redact.js +40 -0
- package/node_modules/@litcodex/lit-loop/dist/rewind-rollout.d.ts +48 -0
- package/node_modules/@litcodex/lit-loop/dist/rewind-rollout.js +292 -0
- package/node_modules/@litcodex/lit-loop/dist/rewind.d.ts +162 -0
- package/node_modules/@litcodex/lit-loop/dist/rewind.js +773 -0
- package/node_modules/@litcodex/lit-loop/dist/route-heads.js +44 -2
- package/node_modules/@litcodex/lit-loop/dist/run-panel.js +1 -0
- package/node_modules/@litcodex/lit-loop/dist/schematic-route.d.ts +6 -0
- package/node_modules/@litcodex/lit-loop/dist/schematic-route.js +35 -0
- package/node_modules/@litcodex/lit-loop/dist/screen-card.d.ts +3 -0
- package/node_modules/@litcodex/lit-loop/dist/screen-card.js +15 -5
- package/node_modules/@litcodex/lit-loop/dist/skill-mention-scope.js +6 -0
- package/node_modules/@litcodex/lit-loop/dist/stack-hook.d.ts +8 -0
- package/node_modules/@litcodex/lit-loop/dist/stack-hook.js +57 -0
- package/node_modules/@litcodex/lit-loop/dist/statusline.js +8 -3
- package/node_modules/@litcodex/lit-loop/dist/threads.d.ts +50 -0
- package/node_modules/@litcodex/lit-loop/dist/threads.js +178 -0
- package/node_modules/@litcodex/lit-loop/dist/trigger.d.ts +1 -1
- package/node_modules/@litcodex/lit-loop/dist/trigger.js +29 -5
- package/node_modules/@litcodex/lit-loop/dist/workflow-map.d.ts +10 -0
- package/node_modules/@litcodex/lit-loop/dist/workflow-map.js +11 -1
- package/node_modules/@litcodex/lit-loop/dist/workflow-stack.d.ts +132 -0
- package/node_modules/@litcodex/lit-loop/dist/workflow-stack.js +488 -0
- package/node_modules/@litcodex/lit-loop/package.json +1 -1
- package/node_modules/@litcodex/lit-loop/skills/lit-adhd/SKILL.md +181 -0
- package/node_modules/@litcodex/lit-loop/skills/lit-hijack/SKILL.md +449 -0
- package/node_modules/@litcodex/lit-loop/skills/lit-loop/SKILL.md +13 -4
- package/node_modules/@litcodex/lit-loop/skills/lit-plan/SKILL.md +6 -0
- package/node_modules/@litcodex/lit-loop/skills/lit-recap/SKILL.md +2 -0
- package/node_modules/@litcodex/lit-loop/skills/lit-schematic/SKILL.md +198 -0
- package/node_modules/@litcodex/lit-loop/skills/lit-scientific-visualization/SKILL.md +34 -8
- package/node_modules/@litcodex/lit-loop/skills/litresearch/SKILL.md +7 -0
- package/node_modules/@litcodex/lit-loop/skills/litwork/SKILL.md +2 -1
- package/node_modules/@litcodex/lit-loop/skills/review-work/SKILL.md +7 -1
- package/node_modules/@litcodex/lit-loop/skills/start-work/SKILL.md +10 -0
- package/package.json +2 -2
- package/readme-assets/badge-version.svg +1 -1
- package/readme-assets/skills/lit-adhd.webp +0 -0
- package/readme-assets/skills/lit-hijack.webp +0 -0
- package/readme-assets/skills/lit-schematic.webp +0 -0
|
@@ -0,0 +1,111 @@
|
|
|
1
|
+
# Clean-room build
|
|
2
|
+
|
|
3
|
+
The build separates two roles. The spec writer reads the sources and writes `SPEC.md`. The implementer reads `SPEC.md` and the target, and builds. The spec is the only artifact that crosses from one role to the other. This mirrors the classic two-team method for compatible reimplementation, where one team studied the original and wrote a functional specification and a second team, with no exposure, built from that specification alone.
|
|
4
|
+
|
|
5
|
+
## Why the split matters
|
|
6
|
+
|
|
7
|
+
A writer who has just read a source reproduces its phrasing, its examples and its order without noticing. A writer who never saw it cannot. The split does two things: it keeps expression out of the target, and it forces the spec to be complete, because anything left out of the spec cannot reach the implementer by memory.
|
|
8
|
+
|
|
9
|
+
Be honest about its limits. The model that implements may have met the source during training, the person running the port has read it, and a skill-shaped source often states its mechanism in one obvious way. The result is therefore described as *independently re-expressed*, with an exposure note in the report, rather than as untouched by the source.
|
|
10
|
+
|
|
11
|
+
## Roles in a Codex session
|
|
12
|
+
|
|
13
|
+
| Role | Who | Sees | Writes |
|
|
14
|
+
| --- | --- | --- | --- |
|
|
15
|
+
| Spec writer | the root session that ran capture, distil and gap | sources, ledger, target | `SPEC.md`, the ledger |
|
|
16
|
+
| Planner | `lit-plan` | `SPEC.md`, the target | the plan file under `.litcodex/plans/` |
|
|
17
|
+
| Implementer | a child agent from `multi_agent_v1.spawn_agent` with `fork_context: false` | the brief (spec + target root), the target | target files |
|
|
18
|
+
| Executor discipline | `start-work` | the approved plan, the rows | row evidence |
|
|
19
|
+
| Gatekeeper | `hijack.mjs check` | everything | pass or fail |
|
|
20
|
+
|
|
21
|
+
## Step 1: plan with lit-plan
|
|
22
|
+
|
|
23
|
+
Load `lit-plan` and give it `SPEC.md` as the brief. Each plan row is a column-zero `- [ ] N. <title>` row in its grammar and names the SPEC section it implements (`M1`, `M4`), the target files, the test it adds, and the real-surface check. The build gate requires at least one such row and a citation of every taken mechanism. Plan rows refer to the spec and the target, never to `sources/` or a source URL; the build gate reads the plan file and fails when it names either. Record the path:
|
|
24
|
+
|
|
25
|
+
```json
|
|
26
|
+
"build": { "plan": ".litcodex/plans/<slug>.md" }
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
A plan kept in the target's tracked plans folder is fine when the target keeps one; `.litcodex/plans/` is local state and stays uncommitted.
|
|
30
|
+
|
|
31
|
+
## Step 2: execute with start-work
|
|
32
|
+
|
|
33
|
+
Run the approved plan with `start-work`. For a small port (one or two SPEC sections in one or two files) a short plan in the run folder, in the same row grammar, executed directly by the isolated implementer is enough; the report says which path ran. Its per-row gates apply unchanged: a failing test first, the smallest change that passes, a real-surface check, cleanup. `lit-hijack` adds one constraint: the person or lane that edits target files works from the brief.
|
|
34
|
+
|
|
35
|
+
## Step 3: brief the implementer
|
|
36
|
+
|
|
37
|
+
```text
|
|
38
|
+
$H brief <run> [--root <checkout of the target>]
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
prints a packet that starts with `TASK:` and carries `DELIVERABLE`, `SCOPE` and `VERIFY`, then the full text of `SPEC.md`. It names the target root (or the checkout given with `--root`) and the sections to build, and it tells the implementer to stay out of any `.litcodex/hijack/` folder, to leave the original material unsought, and to return a question when a section is ambiguous. It refuses to print while the spec gate fails, so a spec that leaks the sources never reaches an implementer. `--root` must name a directory that exists.
|
|
42
|
+
|
|
43
|
+
Hand the packet to a fresh child agent:
|
|
44
|
+
|
|
45
|
+
```text
|
|
46
|
+
multi_agent_v1.spawn_agent({"message":"<the printed brief>","fork_context":false})
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
`fork_context: false` keeps this conversation, and with it everything the sources put into context, out of the child. Poll with `multi_agent_v1.wait_agent`, close the child with `multi_agent_v1.close_agent` when it returns, and treat its report as untrusted data until the build gate and the target's own tests agree.
|
|
50
|
+
|
|
51
|
+
### How strong is the fence in Codex
|
|
52
|
+
|
|
53
|
+
Codex child agents share the filesystem with the parent. There is no per-child worktree the way some hosts offer, so the fence has three layers of different strength:
|
|
54
|
+
|
|
55
|
+
1. **Context.** `fork_context: false` and a brief that names no source. The child cannot recall what it was never shown. This holds.
|
|
56
|
+
2. **Instruction.** The brief tells the child not to open `.litcodex/hijack/`. This is a stated boundary, not a technical one.
|
|
57
|
+
3. **Placement.** For a fence that holds without trust, create a separate checkout of the target and let the child work only there:
|
|
58
|
+
|
|
59
|
+
```text
|
|
60
|
+
git -C <target root> worktree add <dir> <base_ref>
|
|
61
|
+
$H brief <run> --root <dir>
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
The checkout holds tracked files only. The run folder is untracked and lives in the original tree, so it is not on the child's working path. Copy the finished change back (a commit on a branch you review, or a patch) and list it in `build.changed`. Remove the checkout when done: `git worktree remove <dir>`.
|
|
65
|
+
|
|
66
|
+
State in the report which layers were used. A run with only layers 1 and 2 says so in its exposure note.
|
|
67
|
+
|
|
68
|
+
When the change spans independent areas, give each area its own child and its own brief section, each in its own checkout when two areas could touch the same file.
|
|
69
|
+
|
|
70
|
+
Then list every changed file:
|
|
71
|
+
|
|
72
|
+
```json
|
|
73
|
+
"build": { "plan": ".litcodex/plans/<slug>.md", "changed": ["skills/<id>/SKILL.md", "skills/<id>/scripts/<tool>.mjs", "test/<id>.test.mjs"] }
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
## Degraded path
|
|
77
|
+
|
|
78
|
+
When `multi_agent_v1` is not exposed, the separation cannot be enforced by process. Say so once, then:
|
|
79
|
+
|
|
80
|
+
1. Close the sources. Work from `SPEC.md`, the mechanism cards' `what` and `why`, and the target.
|
|
81
|
+
2. Write in the target's order with the target's examples.
|
|
82
|
+
3. Rely on the overlap gate as the remaining fence, and record `build.separation: "single-context"` in the ledger so the report's exposure note is accurate.
|
|
83
|
+
|
|
84
|
+
Missing `multi_agent_v1` is not a reason to stop. It only changes the label on the result.
|
|
85
|
+
|
|
86
|
+
## The overlap gate
|
|
87
|
+
|
|
88
|
+
`hijack.mjs overlap` and the spec and build phases of `check` compare text against every capture of the run, including every text file of a captured repo.
|
|
89
|
+
|
|
90
|
+
- Text is normalised (Unicode compatibility form, lower case) and split into words of letters and digits, so punctuation, Markdown and line breaks do not hide a copy. Hangul and other scripts work the same way.
|
|
91
|
+
- Every run of `min_words` consecutive words (12 by default, kept in `ledger.min_words`) that also appears in a capture is reported with the file, the line, the length and the source id.
|
|
92
|
+
- Three or more identical headings between a target file and a source produce a warning: matching structure is copying too, even with new sentences.
|
|
93
|
+
|
|
94
|
+
How to respond to a hit:
|
|
95
|
+
|
|
96
|
+
| Hit | Response |
|
|
97
|
+
| --- | --- |
|
|
98
|
+
| A sentence or paragraph from the source | Rewrite from the mechanism card, in the target's order and with the target's example |
|
|
99
|
+
| A long shared run inside code | Re-implement from the spec; renaming variables over copied logic changes nothing |
|
|
100
|
+
| A standard phrase both texts need (a licence name, an API name, a protocol field) | Shorten the run below the threshold, or name it once and refer to it. Record the case in the report |
|
|
101
|
+
| Headings that match | Restructure around the target's flow |
|
|
102
|
+
|
|
103
|
+
Lowering `min_words` makes the gate stricter; raising it to silence a hit defeats it. Keep the default unless the report explains why.
|
|
104
|
+
|
|
105
|
+
## What the gate cannot see
|
|
106
|
+
|
|
107
|
+
A paraphrase that follows the source sentence by sentence with synonyms passes a word-run check. So does copied logic with renamed identifiers. Two habits close most of that gap: write from the mechanism cards with the sources closed, and let the implementer be someone who never opened them. For a high-stakes port, add a verifier child that reads the source, the spec and the diff side by side and reports structural echoes the script cannot detect.
|
|
108
|
+
|
|
109
|
+
## Attribution in the build
|
|
110
|
+
|
|
111
|
+
When any taken mechanism rests on an `ideas-credit` source, the build adds the target's attribution notice. Follow the target's existing pattern first: a target that already keeps a methodology or provenance record gets a new entry there. Otherwise an `ATTRIBUTION.md` beside `SKILL.md` names, per source: the work, the author, the URL, the licence, what idea was adapted, and a sentence that no text or code was reused. Record its path in `ledger.attribution.path`; the report gate checks it names every `ideas-credit` source that fed a taken mechanism. The notice is the one file the overlap gate skips, because it must carry titles and URLs.
|
|
@@ -0,0 +1,102 @@
|
|
|
1
|
+
# Distil and licence
|
|
2
|
+
|
|
3
|
+
Distilling turns sources into mechanism cards: what a technique does, why it works, and how sure anyone can be. The licence gate then decides, per source, what the port may take. Both steps are about separating the transferable method from the author's expression of it.
|
|
4
|
+
|
|
5
|
+
## Mechanism, evidence, opinion
|
|
6
|
+
|
|
7
|
+
A source usually mixes three things. Keep them apart on every card.
|
|
8
|
+
|
|
9
|
+
| Part | What it looks like | Where it goes |
|
|
10
|
+
| --- | --- | --- |
|
|
11
|
+
| Mechanism | A step, rule, structure, check or default that produces an effect | `what` and `why` |
|
|
12
|
+
| Evidence | A measurement, a before/after, a reproducible example, a failure story with a cause | `evidence` and `evidence_note` |
|
|
13
|
+
| Opinion | Taste, prediction, preference, a confident claim without support | a card marked `opinion`, or nowhere |
|
|
14
|
+
|
|
15
|
+
Evidence classes:
|
|
16
|
+
|
|
17
|
+
- `evidenced`: someone measured it, showed comparable outputs, or the mechanism can be reproduced from the description and you reproduced it.
|
|
18
|
+
- `anecdotal`: a practitioner reports it worked for them, with enough detail to understand why, and without a measurement.
|
|
19
|
+
- `opinion`: a stance or a style choice. Still worth porting when it fits the target, and the report says it was taken on taste.
|
|
20
|
+
|
|
21
|
+
A post that is mostly opinion can still carry one solid mechanism. A post full of numbers can carry none you can use. Judge each card on its own.
|
|
22
|
+
|
|
23
|
+
## Writing a card
|
|
24
|
+
|
|
25
|
+
```json
|
|
26
|
+
{
|
|
27
|
+
"id": "M1",
|
|
28
|
+
"title": "Production brief before any render",
|
|
29
|
+
"sources": ["S1", "S3"],
|
|
30
|
+
"locator": "S1 section 1; S3 pages 4-6",
|
|
31
|
+
"what": "A short production note fixes the takeaway, the allowed references, the real assets and the rejection condition before the first frame is drawn.",
|
|
32
|
+
"why": "Any decision left open gets filled by the model's default, and those defaults are why unrelated outputs look alike.",
|
|
33
|
+
"evidence": "anecdotal",
|
|
34
|
+
"evidence_note": "Two practitioners report it; neither measured it."
|
|
35
|
+
}
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
Write `what` as behaviour someone could observe in the target after the port, and `why` as the failure the mechanism prevents. If the only way you can phrase a card is the author's sentence, you have the sentence and not yet the mechanism; reread the source, close it, and explain it as you would to a colleague.
|
|
39
|
+
|
|
40
|
+
Merge cards that describe one technique from several sources, and name every source on the merged card. Keep a card that only one source has. Split a card that bundles two techniques with different evidence.
|
|
41
|
+
|
|
42
|
+
The gate for this phase (`hijack.mjs check <run> --phase distil`) refuses an empty card set, a card without `title`, `locator`, `what` or `why`, an evidence class outside the three above, a card with no source, and a card that names a source the ledger does not hold.
|
|
43
|
+
|
|
44
|
+
## What is worth porting
|
|
45
|
+
|
|
46
|
+
Four questions decide whether a card can earn a place in the target:
|
|
47
|
+
|
|
48
|
+
1. **Is it new?** Run the target's typical task once without help and see whether the base model already does this. A mechanism the model follows unaided is no gain.
|
|
49
|
+
2. **Is it a mechanism or a mood?** "Make it feel premium" is a mood. "Limit the palette to three tokens declared before the build" is a mechanism.
|
|
50
|
+
3. **Can the target hold it?** Some techniques need surfaces the target lacks (a renderer, a hook event, a runtime). Note the missing surface rather than faking it.
|
|
51
|
+
4. **Can its effect be seen?** If no output would differ after the port, the parity step cannot prove it. Find the marker before you take it.
|
|
52
|
+
|
|
53
|
+
## Good theft, as a checklist
|
|
54
|
+
|
|
55
|
+
The old artist's distinction between good and bad theft maps cleanly onto this skill:
|
|
56
|
+
|
|
57
|
+
| Good | Bad | In a hijack run |
|
|
58
|
+
| --- | --- | --- |
|
|
59
|
+
| Honour the source | Degrade it | Credit in the report; represent the source's claims fairly |
|
|
60
|
+
| Study it | Skim it | Read every captured source in full before writing cards |
|
|
61
|
+
| Steal from many | Steal from one | Merge techniques across sources; compare them |
|
|
62
|
+
| Credit | Plagiarise | Provenance rows, and a shipped credit line where the licence asks |
|
|
63
|
+
| Transform | Imitate | Re-express in the target's idiom, structure and examples |
|
|
64
|
+
| Remix | Rip off | Combine with what the target already does well |
|
|
65
|
+
|
|
66
|
+
## The licence table
|
|
67
|
+
|
|
68
|
+
Ideas, procedures, methods and facts are outside copyright in most legal systems; the expression of them is protected. That split is why every decision below permits mechanisms and none permits wording. `hijack.mjs licence` applies this table from the captured licence evidence:
|
|
69
|
+
|
|
70
|
+
| Licence evidence | Class | Decision | Reason |
|
|
71
|
+
| --- | --- | --- | --- |
|
|
72
|
+
| MIT, ISC, BSD-2/3-Clause, Apache-2.0, Zlib, BSL-1.0 | permissive | `ideas-credit` | Reuse is allowed; the port takes mechanisms only and ships a credit line |
|
|
73
|
+
| 0BSD, Unlicense, CC0-1.0 | permissive | `ideas-credit` | No conditions; credit is a courtesy the target still pays |
|
|
74
|
+
| CC BY | attribution | `ideas-credit` | The licence asks for credit when material is shared; credit the ideas too |
|
|
75
|
+
| GPL, LGPL, AGPL, MPL, EPL, CC BY-SA | copyleft | `ideas-only` | Copying would pull the target under the source's terms; keep the implementer away from the source |
|
|
76
|
+
| CC BY-NC, CC BY-ND | restricted | `ideas-only` | Commercial use or shared adaptations are barred; mechanisms only |
|
|
77
|
+
| None found (`NOASSERTION`) | unlicensed | `ideas-only` | Default copyright: all rights reserved; posts, blogs, PDFs and most gists land here |
|
|
78
|
+
| Anything else | unrecognised | `ideas-only` | Treated as all rights reserved until a person says otherwise |
|
|
79
|
+
| Text that states reuse terms | restricted-terms | `needs-review` | "do not copy", "no part of this", "source-available", "proprietary", "confidential" |
|
|
80
|
+
|
|
81
|
+
Reuse terms are read only on lines that talk about rights (a copyright line, a licence heading, a notice). A source that merely discusses copying in its subject matter, such as a design article with a "do not copy the layout" bullet, does not trip `needs-review` by that alone.
|
|
82
|
+
|
|
83
|
+
`needs-review` blocks the licence phase until a person decides:
|
|
84
|
+
|
|
85
|
+
```text
|
|
86
|
+
$H licence <run> --set S4=ideas-only --reason "copyright page restricts reproduction; we take the method only"
|
|
87
|
+
$H licence <run> --set S5=no-go --reason "material was shared privately"
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
A user decision is kept on later `licence` runs. Record the reason in plain words.
|
|
91
|
+
|
|
92
|
+
`no-go` applies whatever the licence says when the capture crossed a login or paywall, when the material is leaked, private or confidential, or when terms forbid the use you intend. A mechanism that rests only on no-go sources stays out; one that also has an allowed source may be taken on that source alone, and its card says so.
|
|
93
|
+
|
|
94
|
+
## Credit lines
|
|
95
|
+
|
|
96
|
+
For `ideas-credit` sources the target ships a short notice, in the style the target already uses (an `ATTRIBUTION.md` beside a skill is common). Each entry names the work, the author, the URL, the licence, and one sentence on what idea was adapted and that no text or code was reused. For `ideas-only` sources the report carries the credit, and the target carries it too when the user wants it; ask once.
|
|
97
|
+
|
|
98
|
+
Credit is ethics and courtesy. It leaves the legal position of a copy unchanged, which is why the build never copies in the first place.
|
|
99
|
+
|
|
100
|
+
## Jurisdiction and limits
|
|
101
|
+
|
|
102
|
+
Quotation rules, moral rights and the line between idea and expression differ between countries, and close paraphrase or copied structure can still infringe where words differ. This procedure lowers risk; it does not certify anything. When a source matters commercially and its terms are unclear, tell the user once and let them decide. Patents and trademarks sit outside this gate: re-expressing a method leaves a patent on it untouched, and a source's product names are not yours to reuse.
|
|
@@ -0,0 +1,125 @@
|
|
|
1
|
+
# Gap analysis and port design
|
|
2
|
+
|
|
3
|
+
The gap analysis decides which mechanisms the target needs; the port design decides what each one becomes inside the target. Both are written against the target as it was at the base revision.
|
|
4
|
+
|
|
5
|
+
## Read the target first
|
|
6
|
+
|
|
7
|
+
Before judging any gap, read:
|
|
8
|
+
|
|
9
|
+
- the target's `AGENTS.md` and README, for its rules and its voice;
|
|
10
|
+
- every file of the skill or module being changed: the entrypoint, every reference, every script, every asset that carries behaviour;
|
|
11
|
+
- every test that names the target, and the guards that pin its files (payload pins, corpus floors, route tests);
|
|
12
|
+
- for a plugin, how a neighbouring skill of similar weight is enrolled, so you know which surfaces a complete port must touch.
|
|
13
|
+
|
|
14
|
+
For a new target (`hijack.mjs init --new`), read the neighbouring skills of the product it will join instead, and treat every mechanism as `lacks` with `gap.searched` naming what you compared against.
|
|
15
|
+
|
|
16
|
+
## Gap fields
|
|
17
|
+
|
|
18
|
+
```json
|
|
19
|
+
"gap": {
|
|
20
|
+
"status": "weak",
|
|
21
|
+
"refs": ["skills/motion/SKILL.md:120-134", "skills/motion/scripts/render.mjs:88"],
|
|
22
|
+
"note": "The skill asks for a treatment in prose; the render script starts without one."
|
|
23
|
+
}
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
- `status` is `has`, `weak` or `lacks`.
|
|
27
|
+
- `refs` are `path:line` or `path:start-end`, relative to the target root. The gate resolves each one at the base revision (`git show <base>:<path>`) and fails when the file or the line is missing, so a gap claim always points at text that existed when you judged it. A file the port adds later does not resolve, because it was not there at the base revision. For a target outside git the gate reads the working tree, which is why Phase 0 takes a snapshot first.
|
|
28
|
+
- A `lacks` claim with empty refs needs `searched`: the terms and places you searched ("grep for brief|treatment in skills/motion/ and its tests; no gate before render").
|
|
29
|
+
- `note` is one sentence a reviewer can check against the refs.
|
|
30
|
+
|
|
31
|
+
How to judge the status:
|
|
32
|
+
|
|
33
|
+
| Status | The target… |
|
|
34
|
+
| --- | --- |
|
|
35
|
+
| `has` | does it, and something enforces it: a script, a hook, a test, a gate |
|
|
36
|
+
| `weak` | does part of it, does it only sometimes, or states it in prose with nothing enforcing it |
|
|
37
|
+
| `lacks` | neither does nor states it |
|
|
38
|
+
|
|
39
|
+
Prose that tells the model to do something, with no mechanism behind it, is usually `weak`. Contract prose alone tends to leave behaviour unchanged, while mechanical checks move it. A gap that a gate would close is often the most valuable port.
|
|
40
|
+
|
|
41
|
+
## Port decisions
|
|
42
|
+
|
|
43
|
+
```json
|
|
44
|
+
"port": { "decision": "adapt", "reason": "Strengthen the existing treatment step with a render gate." }
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
- `take`: the target lacks it and should gain it.
|
|
48
|
+
- `adapt`: the target has part of it; strengthen or complete it.
|
|
49
|
+
- `leave`: keep it out, with the reason. Good reasons: the target already has it; the base model already does it unaided; the licence gate forbids it; it conflicts with the target's design; its evidence is too thin for its cost; the target lacks a surface it needs.
|
|
50
|
+
|
|
51
|
+
The gate rejects `take` on a `has` gap (use `adapt` or `leave`) and any taken mechanism whose only sources are `no-go`.
|
|
52
|
+
|
|
53
|
+
## Re-expressing in the target's idiom
|
|
54
|
+
|
|
55
|
+
A port lands well when a reader of the target cannot tell which parts came from elsewhere, because everything is in the target's own terms. For each taken mechanism decide:
|
|
56
|
+
|
|
57
|
+
| Question | Answer from the target, not the source |
|
|
58
|
+
| --- | --- |
|
|
59
|
+
| What is it called? | The target's naming pattern and vocabulary |
|
|
60
|
+
| Where does it live? | The file the target would naturally put it in |
|
|
61
|
+
| What enforces it? | The target's own script, hook, gate or test style |
|
|
62
|
+
| How is it invoked? | The target's routes, commands, flags or events |
|
|
63
|
+
| How is it tested? | The target's test framework and fixtures |
|
|
64
|
+
| How does it ship? | The target's manifest, payload pins and package rules |
|
|
65
|
+
| How do users learn of it? | The target's help, listing, README and docs |
|
|
66
|
+
|
|
67
|
+
Map the source's idea onto the target's surfaces; never carry the source's surfaces across. When a source describes a folder layout or a file format, design the target's own, shaped by the target's existing conventions.
|
|
68
|
+
|
|
69
|
+
## Enrollment surfaces for a Codex plugin target
|
|
70
|
+
|
|
71
|
+
A capability in a Codex plugin is reachable only through the surfaces the host and the plugin read. When the target is a plugin skill, list every surface the port touches:
|
|
72
|
+
|
|
73
|
+
- the skill entrypoint (`skills/<id>/SKILL.md`), its `agents/openai.yaml` (display name, short description, default prompt and whether Codex may pick it implicitly), and its references, scripts and assets;
|
|
74
|
+
- the installer's skill catalog, the payload hashes and the resource hashes the plugin keeps, plus its pack manifest;
|
|
75
|
+
- the prompt hook's trigger tokens, route heads and route directive, when the capability has a natural-language route, and the per-mode continue note a repeated prompt gets;
|
|
76
|
+
- components, agents and settings defaults, when the capability uses them;
|
|
77
|
+
- user-facing listings: README skill tables, the skills guide and usage guide in each shipped language, the package READMEs, the changelog;
|
|
78
|
+
- the package's ignore files and pack guard, so the installed copy carries the new files and local state stays out;
|
|
79
|
+
- tests that fail when any of the above loses the capability (an orphan test).
|
|
80
|
+
|
|
81
|
+
For other systems, find the equivalent list first: the registry, the router, the config, the installer, the docs and the tests. A port that skips one of them is a ghost: the file exists and nothing reaches it.
|
|
82
|
+
|
|
83
|
+
Each product in a family is its own target. A port into one product never copies files into a sibling harness port and never adds a dependency between them; when the user wants the same capability elsewhere, each sibling gets its own run and its own re-expression.
|
|
84
|
+
|
|
85
|
+
## SPEC.md template
|
|
86
|
+
|
|
87
|
+
```markdown
|
|
88
|
+
# <target>: <one-line purpose of this port>
|
|
89
|
+
|
|
90
|
+
Target root: <path> · base revision: <rev>
|
|
91
|
+
Taken: M1, M4 · left: M2, M3, M5 (see the run report)
|
|
92
|
+
|
|
93
|
+
## M1 <title in the target's words>
|
|
94
|
+
|
|
95
|
+
Behaviour: <what the target will do afterwards, observable>
|
|
96
|
+
Lives in: <files and surfaces in the target>
|
|
97
|
+
Enforced by: <script, hook, gate or test>
|
|
98
|
+
Acceptance:
|
|
99
|
+
- <check 1, runnable>
|
|
100
|
+
- <check 2, runnable>
|
|
101
|
+
Parity: <criterion> · marker: <text the new behaviour leaves in its output>
|
|
102
|
+
Enrollment: <catalog, route, docs, pins, tests this section touches>
|
|
103
|
+
Out of scope: <what this section leaves alone>
|
|
104
|
+
|
|
105
|
+
## M4 <title>
|
|
106
|
+
…
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
Write the spec from the mechanism cards and the target, with the sources closed. Use the target's examples and the target's order. The spec gate rejects a section-less mechanism, a path into `sources/`, a source URL, and any run of 12 or more words shared with a capture; it warns when three or more headings match a source's headings, because copied structure is still copying.
|
|
110
|
+
|
|
111
|
+
## Fields the parity step needs from the spec
|
|
112
|
+
|
|
113
|
+
Fill these while writing the spec, so the proof is designed before the build:
|
|
114
|
+
|
|
115
|
+
```json
|
|
116
|
+
"parity": {
|
|
117
|
+
"criterion": "A brief from the skill names the takeaway and the rejection condition.",
|
|
118
|
+
"red": "Old skill: brief has neither field.",
|
|
119
|
+
"green": "New skill: brief has both fields in every run.",
|
|
120
|
+
"surface": "codex exec in a throwaway workspace, old and new skill installed the same way",
|
|
121
|
+
"artifact": "parity/contact-sheet.png"
|
|
122
|
+
}
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
and on the ledger, `parity.markers`: short strings the new behaviour leaves in its output and the old behaviour does not. Pick markers that only the mechanism produces (a field name, a gate's refusal line, a file the new step writes), so a marker in a baseline output means contamination.
|
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
# Parity proof and report
|
|
2
|
+
|
|
3
|
+
A port is proven by two observations: the capability fires on the surface a user touches, and the new target behaves differently from the old one on the same prompt. Green tests and new files are necessary and never sufficient. Ports have passed every gate while being unreachable, and A/B runs have measured nothing because the baseline could read the treatment; this step exists to catch both.
|
|
4
|
+
|
|
5
|
+
## 1. Reachability
|
|
6
|
+
|
|
7
|
+
Drive the real entry point, read what comes back, then break the wiring and watch the probe fail.
|
|
8
|
+
|
|
9
|
+
| Target surface | Probe | Break it by |
|
|
10
|
+
| --- | --- | --- |
|
|
11
|
+
| Prompt-hook route | Pipe a `UserPromptSubmit` JSON payload into the hook and assert the skill is named in the returned context | Removing the route entry |
|
|
12
|
+
| Typed skill | `codex exec` with the typed `$litcodex:<id>` mention, reading the model input | Renaming the skill in the catalog |
|
|
13
|
+
| Skill discovery | A `codex exec` prompt that should surface the skill, with the request log showing its path | Changing the description or the implicit-invocation policy |
|
|
14
|
+
| Script or gate | Run the installed copy's script on a fixture that should fail and one that should pass | Reverting the gate |
|
|
15
|
+
| Package payload | Pack the package and list the files (read the JSON listing, not the human text) | Removing the file from the package manifest |
|
|
16
|
+
|
|
17
|
+
A probe that cannot fail proves nothing; record the broken run beside the passing one, and name the test that went red.
|
|
18
|
+
|
|
19
|
+
## 2. An isolated baseline
|
|
20
|
+
|
|
21
|
+
The baseline is the target at the base revision, in a place where the new work cannot be read:
|
|
22
|
+
|
|
23
|
+
```text
|
|
24
|
+
git -C <target root> worktree add <lane folder>/parity-base <base_ref>
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
or the snapshot copied in Phase 0. Check the isolation before running anything: the baseline folder has none of the new files, `git log` inside it stops at the base revision, and the run folder, the spec and the diff are outside any path the baseline session can reach. When the target lives in a repo the baseline session could explore, run the baseline from a copy outside that repo.
|
|
28
|
+
|
|
29
|
+
## 3. Running both arms
|
|
30
|
+
|
|
31
|
+
Choose prompts the spec never used as examples: a held-out prompt shows the behaviour generalises, while a prompt copied from the spec only shows the spec was followed.
|
|
32
|
+
|
|
33
|
+
For a Codex skill or plugin target, run each arm as a real `codex exec` in its own throwaway workspace with its own scratch `CODEX_HOME`:
|
|
34
|
+
|
|
35
|
+
```text
|
|
36
|
+
CODEX_HOME=<scratch>/baseline-home codex exec --skip-git-repo-check -C <scratch>/baseline-ws "<held-out prompt>" < /dev/null
|
|
37
|
+
CODEX_HOME=<scratch>/treatment-home codex exec --skip-git-repo-check -C <scratch>/treatment-ws "<held-out prompt>" < /dev/null
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
- Each scratch home gets only that arm's copy of the target, installed the same way (for a plugin: `codex plugin marketplace add <copy>` then `codex plugin add <name>@<marketplace>`; for a project skill: a copy under the workspace's own skills folder).
|
|
41
|
+
- The installed copy of the same plugin in the real home stays out of the picture because the real home is never used. Never copy `auth.json` or any credential into a scratch home; when the arm needs a model, sign in inside the scratch home yourself or use a local test provider, and say which.
|
|
42
|
+
- A plugin hook stays untrusted in a non-interactive run. For the throwaway arms only, `--dangerously-bypass-hook-trust` is acceptable because the hook source is the arm's own copy in a scratch home.
|
|
43
|
+
- Keep the runs cheap: a small prompt, one model. Run each arm at least twice when its output varies. One sample can mislead.
|
|
44
|
+
- After the runs, read the real `~/.codex/config.toml` (read only) and confirm no scratch path leaked into it.
|
|
45
|
+
|
|
46
|
+
For a code target, run the target's tests and its real command on both revisions, and save the outputs.
|
|
47
|
+
|
|
48
|
+
Save every output under `parity/` (`baseline-1.md`, `treatment-1.md`, …) and list them:
|
|
49
|
+
|
|
50
|
+
```json
|
|
51
|
+
"parity": {
|
|
52
|
+
"baseline_outputs": ["parity/baseline-1.md", "parity/baseline-2.md"],
|
|
53
|
+
"treatment_outputs": ["parity/treatment-1.md", "parity/treatment-2.md"],
|
|
54
|
+
"markers": ["Rejection condition"]
|
|
55
|
+
}
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
The parity gate then requires every marker in every treatment output and in no baseline output. A marker missing from a treatment output means the port changed behaviour unreliably. A marker in a baseline output means the baseline saw the new work, or the target already had the behaviour and the gap was imaginary. Either way the proof is void until fixed. Before trusting a tie or a surprising win, grep the baseline transcript for the treatment's distinctive identifiers (file names, section names, the skill's own terms); any hit voids the comparison.
|
|
59
|
+
|
|
60
|
+
## 4. Visual outputs
|
|
61
|
+
|
|
62
|
+
When the target makes images, films, slides, documents or pages, the user judges them by eye. Render the baseline and treatment outputs side by side on one contact sheet (rows for arms, columns for runs), save it under `parity/`, and show it. Machine checks such as overlap or layout scores are geometry checks; call them that. Headless browsers used for renders take `--use-mock-keychain --password-store=basic` so no keychain dialog interrupts the user.
|
|
63
|
+
|
|
64
|
+
The sample output is evidence that the port works. Polishing that one sample is a different task; offer it only when the user asks.
|
|
65
|
+
|
|
66
|
+
## 5. The report
|
|
67
|
+
|
|
68
|
+
`REPORT.md` lives in the run folder. The gate requires the three headings, every mechanism id, every source's URL or path, and a credit notice for every `ideas-credit` source that fed a taken mechanism.
|
|
69
|
+
|
|
70
|
+
```markdown
|
|
71
|
+
# Port report: <title>
|
|
72
|
+
|
|
73
|
+
Target: <root> at <base revision> → <new revision or working tree>
|
|
74
|
+
Run: .litcodex/hijack/<slug>/ · gate: check --phase report PASS
|
|
75
|
+
|
|
76
|
+
## Taken
|
|
77
|
+
- M1 <title>: <where it lives now> · parity: marker in 2/2 treatment runs, 0/2 baseline runs
|
|
78
|
+
- M4 <title>: …
|
|
79
|
+
|
|
80
|
+
## Left
|
|
81
|
+
- M2 <title>: the target already enforces it (<path:line>)
|
|
82
|
+
- M3 <title>: opinion with no gain over the base model in a probe run
|
|
83
|
+
- M5 <title>: rests only on S5, which is no-go
|
|
84
|
+
|
|
85
|
+
## Provenance
|
|
86
|
+
| Id | Source | Author | Published | Retrieved | Licence | Decision |
|
|
87
|
+
| --- | --- | --- | --- | --- | --- | --- |
|
|
88
|
+
| S1 | https://… | … | … | … | NOASSERTION | ideas-only |
|
|
89
|
+
|
|
90
|
+
## Exposure
|
|
91
|
+
The spec writer read every source. The implementer worked from SPEC.md as a child agent with
|
|
92
|
+
fork_context false, in a separate checkout (or: in the same context, degraded path). The model may
|
|
93
|
+
have met these sources before. No run of 12 or more words is shared with any capture; headings were
|
|
94
|
+
checked for structural echoes.
|
|
95
|
+
|
|
96
|
+
## Credit
|
|
97
|
+
<attribution notice path, or "credit lives in this report">
|
|
98
|
+
|
|
99
|
+
## Review by
|
|
100
|
+
<date, and what would make this port stale: a model change, a target redesign, a new source>
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
## 6. Closing the run
|
|
104
|
+
|
|
105
|
+
1. `hijack.mjs check <run> --phase report` passes.
|
|
106
|
+
2. The reply to the user says what was taken and left, the parity result in a sentence, the contact sheet when there is one, and the report path.
|
|
107
|
+
3. Offer `review-work` for a review of the diff; its provenance lane reads the run folder.
|
|
108
|
+
4. The run folder stays local and out of commits. Commits, pushes and releases wait for the user.
|