Prepare for a public release: identity out of the code, one-line install

[ralyodio]

Two changes, both prerequisites for making this repository public.

The blog identity is configuration now

The post template hardcoded one person: a byline, a site name, a Mastodon handle, a GitHub profile and an email address, plus two CrawlProof account ids (an analytics site id and an ad slot id).

In a public repository that is worse than untidy. A fresh checkout would publish somebody else's name on every post, and meter that install's pageviews and ad impressions into an account it inherited from the repository rather than chose.

Identity now comes from a config file, read from $BLOG_CONFIG, then <blog dir>/blog.config.json, then ~/.config/cli-tools/blog.json, with the environment able to override any scalar field. The defaults are empty and the empty case is a good one rather than a broken one: no byline, no identity links, and no third-party scripts at all — which is the only fully smolweb-valid output this template has ever been able to produce.

• blog-post config prints which file was picked up and what it resolved to.
• blog-post new says so on stderr when it renders a post with no byline, because a silent anonymous post is the failure worth catching.
• blog.config.example.json is the starting point; blog.config.json is gitignored.

Verified byte for byte: rendering with the maintainer's config reproduces the previous template exactly.

Also drops two colleagues' GitHub handles from gh-prs usage examples, removes a personal dev URL from the feed plugin doc, and ignores the usual credential file shapes.

One-line install, and a cli-tools front door

Installing this meant knowing to clone to a particular path, run pnpm, then run a script deliberately not named link. Fine for the author, poor front door for a public repo.

curl -fsSL https://raw.githubusercontent.com/profullstack/cli-tools/master/install.sh | sh

And a dispatcher, which is mostly there so the set has one name to install by — moshcode decides a tool is present by looking for a binary, so cli-tools on PATH is what makes moshcode install cli-tools and /cli-tools … work:

cli-tools list                 what is here, and what is on PATH
cli-tools update               pull, reinstall, relink
cli-tools link [--force]       symlink into ~/.local/bin
cli-tools aliases --install    merge the pit aliases
cli-tools <command> [args…]    run any of the others

Three things it is careful about:

• The installer adopts a checkout that already owns these command names rather than cloning a second copy whose links are all refused as not-ours, with no explanation of why nothing changed.
• update refuses to move a dirty or diverged tree instead of discarding work.
• aliases --install merges: a name you bound yourself is kept, and the collision is reported rather than silently repointed.

Adds a tools plugin (/tools:install, /tools:list) alongside the existing blog and domain ones.

A correction

These docs had inherited the claim that PATH executables are needed because the pit runs aliases through zsh -c. The README already notes that stopped being true — current moshcode runs $SHELL -ic, which does source rc files. The new code and docs give the weaker, still-sufficient reason: a file works from every caller without anything having been sourced first.

The aliases are thin on purpose and none shares a name with a command, since a shell function beats PATH and would shadow the file. Both invariants are tests now, not comments.

Checks

• 114 tests pass (was 98), typecheck clean.
• Installer verified end to end into a sandbox: clean install links all 8 commands, re-run is idempotent, the adopt-existing-checkout path works, and the alias merge was tested against a copy of a real aliases.json.

🤖 Generated with Claude Code

[github-actions]

ThreatCrush Security Scan

3 finding(s)

MEDIUM: 1 | LOW: 2

Severity	Rule	Location
MEDIUM	redos-nested-quantifier	src/domain-free.ts:56
LOW	insecure-temp-file	test/blog.test.ts:73
LOW	insecure-temp-file	test/blog.test.ts:74

Snippets are redacted; ThreatCrush never prints matched credential material.