Add TBV agent runbook

[web3jenks]

Summary

• add a Trustless Bitcoin Vault agent runbook to the published Testnet docs
• document public browser/computer-use flow, safety boundaries, resume guidance, and evidence expectations
• extract public-facing BabyTester CLI commands and UAT surfaces without publishing private env, secret, or private repo details
• allow TBV LLM_TXT product files in robots.txt

Validation

• git diff --check
• node --check sidebars-default.js

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[greptile-apps]

Greptile Summary

This PR adds a public TBV agent runbook to the testnet docs. The main changes are:

• New browser and computer-use safety guidance for TBV Testnet flows.
• New BabyTester CLI command and UAT surface documentation.
• New navigation entries from the TBV overview and sidebar.
• Additional robots.txt allow rules for TBV llms files.

Confidence Score: 3/5

This is close, but the runbook can guide agents into broken recovery and withdrawal flows.

• Artifact download is treated as optional even though it is required for depositor self-claim recovery.
• Partial repayment is followed by withdrawal without the extra checks needed for remaining debt and collateral health.
• The sidebar and robots changes look contained.

docs/trustless-bitcoin-vault/reference/agent-runbook.mdx needs the lifecycle steps tightened.

Important Files Changed

Filename	Overview
docs/trustless-bitcoin-vault/reference/agent-runbook.mdx	Adds the new agent-facing TBV lifecycle guidance, including the affected artifact and repayment steps.
sidebars-default.js	Adds the new runbook to the explicit TBV Reference sidebar.
static/robots.txt	Allows additional generated llms and TBV llms files.

_{Reviews (1): Last reviewed commit: "Add TBV agent runbook" | Re-trigger Greptile}

[greptile-apps]

Require artifact backup

This makes claimer artifact download optional before activation. The vault-creation docs describe those artifacts and the WOTS keypair as required inputs for depositor self-claim; once the agent activates without saving them, the user can no longer use that fallback if the Vault Provider is later offline or unresponsive. This step should be a required checkpoint, or skipping it should require explicit confirmation that self-claim recovery is being forfeited.

Suggested change

	9. Download recovery artifacts if requested.
	9. Download and back up recovery artifacts before activation, or explicitly confirm that skipping them removes the depositor self-claim fallback.

[greptile-apps]

Branch partial repay

This linear flow proceeds to withdraw after any requested repayment, including a partial repay. A partial repay leaves debt outstanding, so a full withdrawal can revert, while a partial collateral withdrawal requires a separately chosen vault subset and a healthy post-withdrawal health factor. Agents following this sequence can attempt an invalid withdrawal or change collateral exposure when the user only asked to reduce debt.

Suggested change

	12. Repay the intended amount, using max/full only when requested.
	13. Select the relevant vault row if withdraw controls are disabled.
	14. Initiate withdraw and record the final app-side state.
	12. Repay the intended amount, using max/full only when requested.
	13. If repayment was partial, stop and record the updated position unless the user separately confirms a partial collateral withdrawal and target vault subset.
	14. If debt is fully repaid, select the relevant vault row if withdraw controls are disabled.
	15. Initiate withdraw and record the final app-side state.

[github-actions]

🔐 Commit Signature Verification

✅ All 1 commit(s) passed verification

Commit	Author	Signature	Key Type	Key Check
4c0dab9ef41c	Jenks	✅	sk-ssh-ed25519	✅

Summary

• Commits verified: 1
• Signature check: ✅ All passed
• Key type enforcement: ✅ All sk-ssh-ed25519

---

Required key type: sk-ssh-ed25519 (FIDO2 hardware key)

Last verified: 2026-06-03 01:50 UTC