sl0ppi.git/config/themes, branch main a sl0p.foo repository https://git.sl0p.foo/sl0ppi.git/atom/config/themes?h=main 2026-08-12T18:47:23Z docs: record the target-dir symlink coupling and refresh stale provenance 2026-08-12T18:47:23Z user user@clank 2026-08-12T18:47:23Z urn:sha1:ec5c8d9381edebdd2a43ce3504783d7983a025bd The disk risk in the roadmap described a situation that no longer exists (12G free, no monorepo build yet). Replaced with the real standing risk: sl0ppij/target is a symlink into the old ~/lol/zellij checkout, so deleting that checkout breaks builds until 'rm sl0ppij/target && make build plugins'. config: snapshot the live environment as source of truth 2026-08-12T17:35:04Z user user@clank 2026-08-12T17:35:04Z urn:sha1:cd2e81d50569271f69d7f3c99aaf8a0295087f33 The most opinionated part of sl0ppi was never in any repo: it lived in ~/.config/zellij as dotfiles, versioned by ~20 hand-made `config.kdl.pre-*` backups. Imported verbatim so the packaging work has something to install. Deliberately not imported: - config.kdl.pre-* / layouts/*.pre-* / themes/*.pre-* backups (that is what git is for now) - plugins/pane-finder.wasm (a build output of sl0ppij/sl0p/zj-pane-finder) - plugins/zjstatus.wasm (a third-party blob no longer referenced by config.kdl -- dropped as dead weight) The snapshot is faithful, so it still hardcodes development-machine paths; config/README.md lists what the rename work has to parameterise.