This voluntary file records reusable ways Autolith adapts itself to this project. It supplements AGENTS.md and never overrides repository policy, user instructions, or capability boundaries. It contains documentation, not executable Lisp.
- Run Lisp checks through the Nix development shell with SBCL
--no-userinitso machine-local Quicklisp and ASDF configuration cannot mask missing inputs. - Visually inspect generated photographs after converting JPEG output to PNG when Autolith’s local image viewer cannot determine valid JPEG dimensions.
- Keep native Rust, Common Lisp core, CLI, and FLTK GUI checks separate enough that failures retain a clear subsystem boundary.
None. No private image mutation or user-local init change is active for Orfeus.
- Problem:
fs.view-imagerepeatedly rejects valid Orfeus JPEG exports with “no valid pixel dimensions” while ImageMagick reads and converts them. - Current behavior: convert generated JPEGs to temporary PNG files before visual inspection. This is a request-local workaround, not tracked Orfeus behavior.
- Evidence: the failure recurred across valid PEN-F and OM-1 render outputs.
- Prior experiment: an exploratory JPEG parser redefinition passed a synthetic assertion but did not repair real attachments. It was discarded; no mutation remains active.
- Scope: Autolith’s JPEG input dimension parser, outside this repository.
- Verification for a future repair: attach the original generated JPEGs directly, verify dimensions and rendering, then run Autolith’s complete image input tests.
- Removal condition: remove this candidate after direct JPEG viewing works in a clean Autolith image.
- Problem: detached child-agent work repeatedly exhausted the Autolith Lisp heap while this repository already had large compiler and image-processing state.
- Current behavior: perform focused work directly and avoid concurrent detached children when the active image is memory-heavy.
- Scope: Autolith child scheduling and result retention, outside this repository.
- Verification for a future repair: run two representative repository reviews concurrently while monitoring heap growth, then confirm their results can be collected without exhausting the active image.
- Removal condition: remove this candidate after bounded child execution remains stable through an equivalent full Orfeus development session.