extract docker tooling to ../sbo-dockerbuild

The test-build tool and image-builder chain grew from a .extras/ helper into a
standalone toolchain, now maintained in its own repo (../sbo-dockerbuild). Remove
them here (scripts, examples, design docs) and repoint CLAUDE.md: test-building
is now done with the installed `test-build` CLI, deps resolved from the SBo tree,
both trees verified per bump. Package-maintenance files stay: nvchecker.toml,
hooks/, assets/.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

1 files changed, 23 insertions, 20 deletions

diff --git a/CLAUDE.md b/CLAUDE.md
index 5bfba11..ffead17 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -11,7 +11,7 @@ on SBo:
 
 1. Track upstream version changes (via nvchecker).
 2. Reflect a new upstream version in the package's `.SlackBuild` / `.info`.
-3. Test-build in a throwaway docker image (see below).
+3. Test-build with the `test-build` tool (see below).
 4. Generate the SBo submission tarball to upload.
 
 New-package development happens in **other** repos, not here:
@@ -48,9 +48,8 @@ Version tracking is handled by a single file:
 ### `.extras/` holds all non-package repo files
 
 Anything that is not a SlackBuild package must live under `.extras/`, never at
-the repo root. Exception: a top-level `docs/` for design docs and specs is fine
-in this repo (the subtree-leak concern that bans it applies to the development
-repos, not here). Existing specs live under `.extras/docs/specs/`.
+the repo root. Currently: `nvchecker.toml` (version tracking), `hooks/` (git
+hooks), `assets/`.
 
 ---
 
@@ -141,25 +140,29 @@ compiled binaries. No stripping needed.
 
 ---
 
-## Test-building in docker
+## Test-building
 
 Because these packages are already published on SBo, the build here is a
-**verification step** on a version bump, not development. It runs in a
-throwaway Slackware container, so it is hermetic and disposable: unlike a real
-`slackrepo build` on the buildsystem VM, **Claude may run it directly**.
+**verification step** on a version bump, not development. It runs in a throwaway
+Slackware container via the **`test-build`** tool, which lives in its own repo,
+`../sbo-dockerbuild` (installed to `~/bin/test-build`). Being hermetic and
+disposable, **Claude may run it directly** (unlike a real `slackrepo build` on
+the buildsystem VM).
 
-Images (Slackware official, pull fresh each time — they are throwaway):
+Workflow for a bump: edit the `.SlackBuild`/`.info`, then verify on **both**
+trees (these are all SBo-published packages, so both are mandatory):
 
-- `-current`: `registry.slackware.nl/slackware/slackware-builder:current`
-- `15.0` (stable): `registry.slackware.nl/slackware/slackware-builder:15.0`
-
-Mount the package dir into a `--rm` container and run its SlackBuild. Anything
-built is discarded with the container; nothing lands in the working tree.
+```bash
+test-build <pkg>            # -current
+test-build --stable <pkg>   # 15.0
+```
 
-No wrapper script exists yet — write the `docker run` invocation inline, or add
-one under `.extras/` if this gets repetitive. The build's only outputs that
-matter are the exit status and lint result; the package tarball it produces is
-throwaway.
+`test-build` resolves the target from the local dir (CWD or a path) and its deps
+from the configured SBo tree, builds in a `--rm` container, and lints with
+`sbopkglint`. Use `--keep` to copy the built `.txz` out (e.g. a binary repack
+like `metasploit-framework-bin` that needs a host install to regenerate
+post-install artifacts). See `../sbo-dockerbuild` for the full tool and its
+image-builder chain.
 
 The one artifact worth keeping from a clean bump is the **SBo submission
 tarball** (`SBo/<pkg>.tar.gz`), produced by the `post-commit` hook — that is
@@ -281,8 +284,8 @@ Claude authors/edits the sources (`.SlackBuild`, `.info`, `README`,
 `slack-desc`, `doinst.sh`, nvchecker stanzas) and runs the non-building checks
 (`sbolint`, `sbodl`, `sbofixinfo`).
 
-**The one exception in this repo** is the throwaway-docker test-build (see
-[Test-building in docker](#test-building-in-docker)): it is hermetic and
+**The one exception in this repo** is the throwaway-docker test-build via the
+`test-build` tool (see [Test-building](#test-building)): it is hermetic and
 disposable, so Claude may run it to verify a bump, including `sbopkglint` on
 the throwaway package it produces.