docs: recreate the harness without the CLI via the docsite llms.txt - #23
Merged
Conversation
doidor
force-pushed
the
doidor/bootstrap-harness-skill
branch
from
June 23, 2026 10:43
1156484 to
19f28f2
Compare
doidor
force-pushed
the
doidor/bootstrap-harness-skill
branch
from
June 24, 2026 15:02
19f28f2 to
d32e524
Compare
Replace the idea of a dedicated "bootstrap" skill (redundant with the docs) with guidance to point any coding agent at the docsite's machine-readable llms.txt and have it rebuild the harness by hand — the concrete payoff of AgentRig's no-lock-in design. - Getting started: add "Recreate the harness without the CLI (no lock-in)" — what llms.txt gives an agent (the 12 principles as a per-principle artifact inventory, the surface projection map, the install-completeness audit), a pointer to knowledge/templates/ for exact file contents, and a ready-to-use prompt. - Home page: the "No lock-in" card now links to that walkthrough. - README: add a concise "No lock-in — recreate the harness without the CLI" section. - Use the canonical custom domain (https://tudorpopa.com/agentrig) for all docsite links and the markbook siteUrl, so generated canonical / og:url / sitemap and the prose links agree with where the site is actually served. Docs/README/site-config only; no behavior or installed-artifact changes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Bump the docs toolchain (@doidor/markbook + @doidor/markbook-core) to the latest 0.6.0. All changes across 0.3–0.6 are additive with safe defaults (optional `search`/`viewTransitions` config, nested-directive composition, keyboard-nav search) — no breaking config changes; markbook.config.ts is unchanged. 0.6.0 also collapses the homepage canonical to the site root, so the generated docsite canonical is now https://tudorpopa.com/agentrig/. docs:build, npm build, eval --static (33/33 + 6/6) and the test suite (66/66) all pass on the upgrade. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
doidor
force-pushed
the
doidor/bootstrap-harness-skill
branch
from
June 29, 2026 18:54
3d703b3 to
6f8240c
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Documents how to recreate the entire AgentRig harness without the CLI by pointing any coding agent
at the docsite's machine-readable
llms.txt. This is theconcrete payoff of AgentRig's no-lock-in design — the package is never a runtime dependency.
Changes (docs + README + site config)
docs/getting-started.md— new section "Recreate the harness without the CLI (no lock-in)":what
llms.txtgives an agent (the 12 principles as a complete per-principle artifact inventory,the surface projection map, the install-completeness audit), an explicit pointer to
knowledge/templates/for exactcopy-paste file contents, and a ready-to-use prompt.
docs/index.md— the "No lock-in" card now links to that walkthrough.README.md— concise "No lock-in — recreate the harness without the CLI" section.markbook.config.ts—siteUrlset to the canonical custom domainhttps://tudorpopa.com/agentrigso generated
canonical/og:url/ sitemap (and every docsite link in the prose) agree with wherethe site is actually served.
.changeset/recreate-from-llms.md— patch (README ships in the package).No behavior changes, no installed-artifact changes, no
knowledgeVersionbump.Did I verify the docs are actually sufficient to recreate the harness?
Yes — gap analysis:
principles.mdis a full per-principle inventory (12/12, eachnaming its artifact + path);
agent-surfaces.mdis the exact projection map;evals.mddocumentsthe deterministic audit the agent can self-check against.
contents (inlining them verbatim would duplicate and drift from
knowledge/templates/). Fixed bymaking
knowledge/templates/the explicit "exact bytes" source in the new section.llms.txt(architecture + inventory) +
knowledge/templates/(verbatim files) — both in the same publicrepo
llms.txtindexes — together are sufficient.Verification
node dist/cli.js eval --static .— Install Completeness 100% (33/33), Quality Probes 100% (6/6) (back to themainbaseline; the skill's extra check is gone)npm run build— clean ·npm test— 66/66 passnpm run docs:build— clean; the new section's anchor slug(
recreate-the-harness-without-the-cli-no-lock-in) matches the cross-links, the content flows intothe regenerated
llms.txt, and generatedcanonical/og:url/llmsall usetudorpopa.com(zerodoidor.github.ioleft insite/)origin/mainAlso in this PR: bumps the docs toolchain
@doidor/markbook+@doidor/markbook-core0.2.0 → 0.6.0(devDependencies). All changes are additive with safe defaults — no breaking config changes;markbook.config.tsis unchanged. 0.6.0 collapses the homepage canonical to the site root, so the generated docsite canonical ishttps://tudorpopa.com/agentrig/.docs:build+ the full suite pass on the upgrade.