<feed xmlns='http://www.w3.org/2005/Atom'>
<title>archsetup/docs/PLAN-dotfiles-separation.org, branch claude/hungry-franklin-09fffc</title>
<subtitle>Builds a full dev workstation from a bare Arch Linux install.
</subtitle>
<id>https://git.cjennings.net/archsetup/atom?h=claude%2Fhungry-franklin-09fffc</id>
<link rel='self' href='https://git.cjennings.net/archsetup/atom?h=claude%2Fhungry-franklin-09fffc'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/archsetup/'/>
<updated>2026-07-09T19:02:20+00:00</updated>
<entry>
<title>docs: remove personal paths and false co-authorship before release</title>
<updated>2026-07-09T19:02:20+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-07-09T19:02:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/archsetup/commit/?id=4f252c5d64b9cbcdcb6ea9ed2accfc7c89452a24'/>
<id>urn:sha1:4f252c5d64b9cbcdcb6ea9ed2accfc7c89452a24</id>
<content type='text'>
The repo carries an open task to publish it, and docs/ leaked things a clone
could neither use nor should see.

Absolute paths under one user's home become the repo root, a home-relative
path, or a named variable, so the snippets stay runnable for anyone. The
testinfra example takes its user from an env var instead of hardcoding one.

References into a private sibling project and into the gitignored tooling
directory are replaced by what they mean; as written they were dead links in
any clone but the author's.

Five documents claimed a co-author who is not a person. An #+AUTHOR line
survives conversion into docx, a wiki page, or a PDF, so it is worth being
exact about: these documents have one author.
</content>
</entry>
<entry>
<title>docs(plan): use SSH push URL and add claude.sh to minimal tree</title>
<updated>2026-05-22T18:40:52+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-22T18:40:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/archsetup/commit/?id=b3b020f92e27de3641ca419724fc4490b896333c'/>
<id>urn:sha1:b3b020f92e27de3641ca419724fc4490b896333c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>docs(plan): fold review decisions into dotfile-separation spec</title>
<updated>2026-05-15T00:13:19+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-15T00:13:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/archsetup/commit/?id=aa88bbcadd7d83b0c10b643e94a8e5dd7bfa50d5'/>
<id>urn:sha1:aa88bbcadd7d83b0c10b643e94a8e5dd7bfa50d5</id>
<content type='text'>
I locked the URL (https://git.cjennings.net/dotfiles.git), the bare
repo path (/var/git/dotfiles.git), and the Phase 1 scope. Added
environment.d/envvars.conf (rofi path stripped) and
systemd/user/emacs.service to the minimal/ tree. Promoted the
DESKTOP_ENV=none VM test from optional to required. Made Phase 2's
clone explicit (sudo -u, not chown-after). Tightened Phase 3's order
so unstow and restow happen without a Hyprland reload between them.
Added a note that the new dotfiles repo can't go on GitHub until the
secrets cleanup ships, plus the post-install update flow in Step 3.3.

Replaced the "Before starting" question block with a Status table
since all five open questions are now resolved.
</content>
</entry>
<entry>
<title>docs: add dotfile-separation spec with phased implementation plan</title>
<updated>2026-05-13T18:30:51+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-13T18:30:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/archsetup/commit/?id=8ea5bd45fb6d613a48d5285e99026925a4dfaae0'/>
<id>urn:sha1:8ea5bd45fb6d613a48d5285e99026925a4dfaae0</id>
<content type='text'>
Covers extracting dotfiles/ into a standalone repo, adding a minimal/ stow target for headless installs, and a three-phase plan with commit boundaries. todo.org tracks the review as a sub-task.
</content>
</entry>
</feed>
