<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sl0ppij.git/sl0p/workspace-hints-proposal.md, branch main</title>
<subtitle>a sl0p.foo repository</subtitle>
<id>https://git.sl0p.foo/sl0ppij.git/atom/sl0p/workspace-hints-proposal.md?h=main</id>
<link rel='self' href='https://git.sl0p.foo/sl0ppij.git/atom/sl0p/workspace-hints-proposal.md?h=main'/>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/sl0ppij.git/'/>
<updated>2026-08-12T15:06:29Z</updated>
<entry>
<title>sl0p: document workspace hints for consumers</title>
<updated>2026-08-12T15:06:29Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-08-12T15:06:29Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/sl0ppij.git/commit/?id=82df0861b06529e881209e90a039dd86d1d7db20'/>
<id>urn:sha1:82df0861b06529e881209e90a039dd86d1d7db20</id>
<content type='text'>
</content>
</entry>
<entry>
<title>sl0p: propose per-pane workspace hints</title>
<updated>2026-08-12T14:42:40Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-08-12T14:42:40Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/sl0ppij.git/commit/?id=889180b6b6b7a52144ffb14fc50d9531203677e6'/>
<id>urn:sha1:889180b6b6b7a52144ffb14fc50d9531203677e6</id>
<content type='text'>
A design doc, not an implementation: lets a project ship a layout that also tells
an agent what each pane is for.

The load-bearing decision is the boundary -- zellij carries one opaque string per
pane and never interprets it, pi owns the whole vocabulary. That keeps the fork
change to a single field threaded along the existing status_bar path, and lets the
vocabulary change without rebuilding zellij.

Records two findings that were checked rather than assumed, since both would
otherwise be discovered the expensive way: pane names cannot carry metadata (there
is no stable name field at runtime, and title is clobbered by whatever the program
sets), and the runtime query surface already exists (list-panes --json), so the
work is only to get the field into it.
</content>
</entry>
</feed>
