<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sl0ppi.git/pi-ext/install.sh, branch main</title>
<subtitle>a sl0p.foo repository</subtitle>
<id>https://git.sl0p.foo/sl0ppi.git/atom/pi-ext/install.sh?h=main</id>
<link rel='self' href='https://git.sl0p.foo/sl0ppi.git/atom/pi-ext/install.sh?h=main'/>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/sl0ppi.git/'/>
<updated>2026-08-12T17:34:35Z</updated>
<entry>
<title>installers: sync scripts/ CLI helpers into ~/bin</title>
<updated>2026-08-12T17:34:35Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-08-12T14:28:53Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/sl0ppi.git/commit/?id=2db5d93ce8269a922eba3674597cbcbc1f2a3cb1'/>
<id>urn:sha1:2db5d93ce8269a922eba3674597cbcbc1f2a3cb1</id>
<content type='text'>
The repo already treated extensions as a deliberate snapshot: copy every
*.ts into ~/.pi/agent/extensions, skip files already identical. Standalone
helpers in scripts/ had no such path, so pir had to be copied by hand and
then drifted from the checkout.

CLI_TOOLS is a "&lt;source in scripts/&gt;:&lt;installed name&gt;" list, so the
installed command name can differ from the filename (pi-resume -&gt; pir).
Same copy-not-symlink policy as the extensions, for the same reason: the
global set should not track in-progress edits. Copies are chmod +x, the
destination is PI_BIN_DIR-overridable like PI_EXT_DIR, a missing source is
reported and skipped rather than aborting the whole install, and the entries
participate in the existing --dry-run output and the "nothing changed"
tally.

Also records why answer-picker.ts is absent from the list: it needed a
helper binary in its socket+separate-pane form (c88fe0d), and does not any
more now that zellij draws and hit-tests the buttons itself and reports
clicks on pi's stdin. That implementation is parked in attic/, which this
script does not glob -- top-level *.ts only -- so nothing there installs.
</content>
</entry>
<entry>
<title>installers: exclude experimental sixel-images.ts from global + dev load</title>
<updated>2026-08-12T17:34:35Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-07-22T23:18:28Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/sl0ppi.git/commit/?id=a7d057326629e0e96332d1b344533024c272c98f'/>
<id>urn:sha1:a7d057326629e0e96332d1b344533024c272c98f</id>
<content type='text'>
Add sixel-images.ts (WIP): renders inline images as sixel via chafa by
forcing image capability on under tmux and patching pi-tui Image.render.
It works end-to-end (sixel draws inside the read box, width-guard bypassed
via an empty Kitty APC marker) but has rough edges (double-render, spacing),
so it is parked for now.

install.sh and dev.sh now carry an EXCLUDE list so this extension is neither
installed globally nor loaded in the isolated dev session. The slop-tool-boxes
read-image injection that paired with it was reverted separately.
</content>
</entry>
<entry>
<title>install.sh: skip files already identical at destination</title>
<updated>2026-08-12T17:34:35Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-07-22T17:42:14Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/sl0ppi.git/commit/?id=037c96fd7230c389fa40f639e5d546e4d06f54ea'/>
<id>urn:sha1:037c96fd7230c389fa40f639e5d546e4d06f54ea</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add install.sh: copy extensions into global pi extensions dir</title>
<updated>2026-08-12T17:34:35Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-07-22T17:41:01Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/sl0ppi.git/commit/?id=252bc1d37abf66c8aea8adfa6cb3826429ed96e4'/>
<id>urn:sha1:252bc1d37abf66c8aea8adfa6cb3826429ed96e4</id>
<content type='text'>
</content>
</entry>
</feed>
