balladeer 0.0.4 → 1.0.0

package/dist/copy.d.ts

@@ -0,0 +1,148 @@
+/**
+ * The boundary copy, byte for byte. It is the same text in `docs/setup-boundary.md`
+ * and in the control plane's `/agent` instructions, and a packaging test compares
+ * all three, so what the command tells a person Balladeer can see cannot drift
+ * from what the documentation says.
+ *
+ * It describes the product's boundary, not one release's behaviour. What this
+ * release actually performs is stamped separately, outside this constant.
+ */
+export declare const BOUNDARY_COPY = "Balladeer never receives your code. It cannot read your repository: it holds no GitHub token,\ninstalls no GitHub App, and has no access to your files, tests, fixtures, logs, prompts, or\ntranscripts.\n\nWhat it does receive is small and bounded. From you: the text of each promise a named person on your\nteam approves, the numeric ids of your repository and its GitHub owner, and the name of its default\nbranch. From CI: GitHub's signed statement of which repository, workflow, and run is reporting, and\nfor each promise the run checked, the pass or fail outcome, the exact commit it checked, and content\nhashes of the verifier package and its output. Hashes cannot be turned back into your code or your\ntest output.\n\nThe verify job in your CI runs your tests with your checkout and has no Balladeer credential. A\nseparate publish job, with no checkout, sends only those outcomes and hashes.\n\nThis setup creates two credentials, both of which you control. Approving in the browser lets this\nsession act as you to add repositories, connect your coding agent, connect CI, and propose promises;\nit cannot approve, activate, or remove anything. That session lasts a day, each use buys it another\nday, and it is gone seven days after you approved it however much you used it. The coding agent's\nown connection has no expiry: it lets the agent read the promises your team has approved, propose\nnew ones, and propose replacing, retiring, excepting, or reassigning one you already have; every one\nof those waits for a named person to decide it. It can also carry out one of those acts for you, and\nonly this way: you open a Balladeer page in your own browser, read what the act is, sign it off\nthere, and read back the one-time code that page gives you. That code covers that one act on that\none thing, once, and Balladeer records you as the person who took it and the connection as the\nmessenger. Without a code you signed, the connection cannot approve, activate, grant, transfer,\nretire, or delete anything. You can revoke either one at any time in Balladeer, and the setup\nsession also ends on its own.\n\nAdding the workflow puts a check on pull requests into your default branch. That check is advisory\non Balladeer's side; whether it blocks a merge is your own branch protection.\n";
+/**
+ * How a person gets a workspace to approve into, for an agent reading the
+ * setup instructions.
+ *
+ * The pairing page is one page doing two jobs, and only one of them was ever
+ * described: an agent whose person had no workspace read instructions that
+ * assumed there was one to join. The name can be carried to that page so the
+ * person does not retype it, and carrying it is all an agent may do. Creating a
+ * workspace is a person's act, so the copy says the flag pre-fills a form and
+ * says who presses the button, rather than leaving an agent to read a flag name
+ * and conclude it creates something.
+ *
+ * Byte for byte the same text as `AGENT_INSTRUCTIONS_JOIN_OR_CREATE` in the
+ * control plane, and a packaging test compares them: the page an agent fetches
+ * and the terminal it is reading cannot come to describe this differently.
+ */
+export declare const JOIN_OR_CREATE = "The pairing page joins an existing workspace or makes a new one. Somebody whose team already has\na Balladeer workspace signs in and approves the code from the terminal. Somebody who is the first\nperson from their team signs in, names a workspace, and clicks Create, and only then is there\nanything to approve into.\n\nYou can save them the typing, and nothing else. Ask what the workspace should be called, then run\n`balladeer setup --create-workspace \"<name>\"` with the name they gave you. The pairing link this\ncommand prints then carries `?create=<name>`, which pre-fills that name in the create form on the\npairing page. It fills the box and no more than that: the person signs in and clicks Create, and\nuntil they do there is no workspace. An agent never creates one, and Balladeer refuses the attempt\nwhatever it was told in conversation. Never invent the name either. A workspace is named once and\nthe whole team reads it.";
+/**
+ * When a coding agent reads this repository's promises, and when it does not.
+ *
+ * The instruction it replaces said "retrieve by identity, never in bulk" and
+ * then left the choice of read to the agent, which in a repository holding a
+ * thousand promises means a session that opens by paging a catalog it has no
+ * question about. This says which read answers which situation, and names the
+ * one read that must never happen at session start.
+ *
+ * Byte for byte the same text in three carriers: the conventions block written
+ * into the customer's own instructions file, the instructions this server sends
+ * a host on initialize, and the `/agent` page. A packaging test compares them,
+ * because an agent that met one of the three and not the others would read the
+ * catalog on the strength of the carrier that was quiet about it.
+ */
+export declare const RETRIEVAL_SCOPE = "### Reading what is already agreed\n\nRetrieve by promise, and only when this session has a reason to. One repository here can hold a\nthousand agreed promises, and a plan built from whatever survived a truncated catalog read is worse\nthan a plan built from none of it, because nothing tells you which half went missing.\n\nWhen a person gives you a promise id, expand exactly that one with get_promise and stop there. Every\npromise page carries a control that copies its id, so an id is what a person hands you when they\nmean a particular promise. Ask for one rather than searching for what they meant.\n\nConsult list_promises in two situations and no others. The person asks what this repository has\npromised, in which case page the index they asked for. Or the change you are about to make touches\npaths that carry promises, in which case give those paths to list_promises: it answers with the\npromises whose scope overlaps them, closest first, and with the few that name no path and so cover\nthe whole repository. That answer is a selection rather than a page and does not continue with a\ncursor, so when the total beside it is larger than what you were handed, narrow the paths rather\nthan asking for more.\n\nWhen you do not yet know which paths you are about to touch, do not call the index at all. Work from\nids until you do, because a page you did not ask a question of is not about your change, and reading\none as though it were is how a plan quietly misses the promise it breaks.\n\nTo learn which paths those are, read `paths` on a list_promises answer you asked for\nwithout paths of your own. It is the set of\nrepository paths this repository's promises are scoped to, deduplicated and bounded, with\n`pathsTruncated` saying whether there were more than the answer carries. Compare the files you are\nabout to change against it. Nothing matching means there is nothing here to read, and saying so is a\nbetter answer than a page of promises about somewhere else.\n\nNever call get_promise_context at the start of a session. It answers the markers you give it, and\nbefore you know what you are changing there are no markers to give: what comes back is a slice of\nthe catalog chosen by nothing. Call it once the work is in front of you, with that work's markers.\n\nEvery one of these reads is bounded and none of them returns the whole catalog. Read the total\nbeside the rows and the sentence in `scope` that says what the total is a total of, and when the\ntotal is larger than what you were handed, page or narrow rather than planning as though you had\nseen everything.";
+/**
+ * The two things an agent offers in a connected repository without being asked
+ * for them, and starts neither of on its own.
+ *
+ * Both exist because the person cannot see what the agent can. A promise nobody
+ * is checking looks exactly like a promise that is protected until somebody
+ * opens the catalog, and a proposal sitting in a browser tab is a proposal
+ * nobody reads. Neither of these is a licence to act: the first is a sentence
+ * and a question, the second is a rendering of work already done. The capture
+ * style stays what it was, and nothing here proposes a promise nobody asked
+ * for.
+ *
+ * It sits inside `CONVENTIONS_BLOCK` rather than beside it, because the block
+ * is what reaches a session in the customer's own repository. The control
+ * plane's `/agent` page carries the same bytes under its own constant, and a
+ * packaging test compares them.
+ */
+export declare const SESSION_BEHAVIORS = "### Two things to offer without being asked\n\nAt the start of any session in this repository, before you plan anything, ask list_promises for the\npromises nothing is checking yet that belong to the person you are working with: `unverified` true\nand `mine` true, which is one bounded read rather than the catalog. If it returns any, say so in one\nline and offer to build their verifiers now. Name each one by its one-sentence claim rather than by\nan id, so the person can see which behavior is unguarded. Ask the same tool for\n`brokenSinceLastSeen` true as well, and where that returns any, say in one line that those promises\nbroke since they last looked, name each by its claim, and offer to fix them. Then wait for their\nanswer. The offer is the whole of it, and never start building or repairing one because nobody said\nno.\n\nTheirs, and nobody else's. `mine` keeps the promises this person owns or agreed to, and a teammate's\nunguarded promise is that teammate's to hear about: a session that opens by reading out other\npeople's unfinished work reads as an audit of them. `brokenSinceLastSeen` is that person's own by\nconstruction and needs no `mine` beside it. Drop `mine` when this person asks what the rest of the\nteam has promised, and say whose promises you are showing them when you do.\n\nWhen you have proposed promises, show them here as well as there. Put each proposal in the\nconversation in full: its one-sentence claim, who it is for, when it applies and what must then be\ntrue, the numbered cases that must keep working and the ones that must be caught, and every question\nyou left open. Then offer to finish the agreement from here, by asking for a sign-off, giving them\nthe page it returns and taking the one-time code that page shows them, so the browser is needed only\nfor signing. Give them the review link in the same message too, because some people would rather\nread it there and edit it before they agree.";
+/**
+ * What a session may spend on reading, in three sentences.
+ *
+ * The bounded index says what one read may carry. This says how many reads
+ * there should be, which is the half no ceiling can enforce: an agent that
+ * pages the whole index and expands every row has obeyed every limit in the
+ * protocol and has still put the entire catalog in front of a model. So the
+ * budget is written where the agent reads it, beside the rule that makes it
+ * affordable: a row carries what it takes to rule its promise out, and an
+ * expansion is what you spend once a row could not.
+ *
+ * Three carriers say it, byte for byte: the block setup writes into the
+ * customer's own instructions file, the instructions the MCP server sends on
+ * initialize, and the page `/agent` serves. A packaging test holds them
+ * together.
+ */
+export declare const FETCH_BUDGET = "Fetch by id, and only for an id the person gave you or an index row whose paths match the change in\nfront of you. Never enumerate the catalog. Never chain one fetch into the next to see the whole of\nsomething: when the rows do not settle it, narrow the filter rather than expanding another promise.";
+/**
+ * What a coder must know before their editor opens a file inside a promise's
+ * own directory.
+ *
+ * A seal is broken by an ordinary edit, and the person who breaks one rarely
+ * meant to: a rename swept a directory, a formatter reached everything, a
+ * dependency upgrade rewrote an import. The cost lands on somebody else, who
+ * has to qualify the promise again before it protects anything. So this says
+ * three things in the order a coder needs them: those files are sealed, here is
+ * how to see which ones before you edit and before you push, and here is the
+ * single case where editing one is the right move.
+ *
+ * It sits inside `CONVENTIONS_BLOCK` rather than beside it, because the block
+ * is what reaches a session in the customer's own repository. The MCP server's
+ * tool guidance and the control plane's `/agent` page carry the same bytes
+ * under their own constants, and a packaging test compares all three.
+ */
+export declare const SEALED_FILES = "### Files that are sealed, and the one reason to edit one\n\nEvery file under .continuity/promises/ is sealed. The promise that owns that directory records the\nexact bytes of each file in it, so editing one, adding one there, renaming one or deleting one\nbreaks the seal. A promise whose seal is broken stops being checked, and it stays that way until a\nnamed person qualifies it again, which is their afternoon rather than your commit. Nothing in there\nis ordinary source: keep it out of refactors, formatting runs and dependency upgrades.\n\nFind out which directories are sealed before you plan an edit, not after. balladeer status lists\nthem, and list_promises names a promise's sealed directory on its row once a verifier is bound to\nit. Then, before you push, run balladeer check-seals. It prints nothing and exits zero when your\nchange touches no seal, and names the promise, its owner and its page when your change would break\none.\n\nThe one reason to edit a sealed file is to repair a verifier that can no longer run: something it\nimports moved, or the language it is written in changed under it. Never edit one to make a failing\ncheck pass. A check going red is the promise doing its job, and the repair for that belongs in the\nbehavior it protects. A repair is not finished until the promise is sealed again with the runner\nthis repository is pinned to. get_promise_setup carries that exact seal command, and balladeer\ncheck-seals prints it beside any promise it names.";
+/**
+ * Which promises a change touches, measured rather than guessed.
+ *
+ * A promise's scope paths are what somebody typed when they agreed it, and they
+ * age the moment a module moves. The touch map is the measurement instead: the
+ * files each verifier actually executed, recorded on the customer's machine and
+ * sent nowhere. An agent that does not know the command exists goes on matching
+ * markers and never asks for the better answer sitting in the repository.
+ *
+ * The last paragraph is the whole reason the signal is named here. Whether the
+ * map is worth keeping is answerable only if the receipt says which fetches it
+ * caused, and no surface can infer that after the fact.
+ *
+ * Three carriers say it, byte for byte, and a packaging test holds them
+ * together.
+ */
+export declare const TOUCH_MAP_GUIDANCE = "Prefer the measurement over the markers. Where this repository has a touch map, `balladeer affected\n<paths...>` answers which promises ran the files in front of you, out of what each verifier actually\nexecuted the last time `balladeer touch-map` measured it. Both commands run on this machine and\nsend Balladeer nothing, so you may name any path in the change.\n\nAn answer marked stale was measured against a verifier that has changed since, so read it as the\nlast thing anybody measured rather than as fact, and offer to run `balladeer touch-map` again.\nWhere there is no map, where it does not name your paths, or where it reports a promise it could not\nmeasure, fall back to the paths on the index rows. The map narrows which promises are worth\nfetching. It never widens what you may read: the catalog is still never enumerated, and the fetch\nbudget is unchanged.\n\nWhen a retrieval receipt asks why you read a row, the answer for one the map named is `touch`.";
+/**
+ * The conventions block written between markers into this repository's agent
+ * instructions file. Fixed text, compared byte for byte by a test, because a
+ * block that drifts per run would rewrite a customer's committed file on every
+ * setup and the diff would say nothing.
+ */
+export declare const CONVENTIONS_BLOCK = "## Balladeer promises\n\nBefore planning work in this repository, read the promises this team has already approved through\nthe Balladeer MCP server. They are the behaviors a named person has agreed the software keeps, so\nyour plan has to hold them, not just read them.\n\n### Reading what is already agreed\n\nRetrieve by promise, and only when this session has a reason to. One repository here can hold a\nthousand agreed promises, and a plan built from whatever survived a truncated catalog read is worse\nthan a plan built from none of it, because nothing tells you which half went missing.\n\nWhen a person gives you a promise id, expand exactly that one with get_promise and stop there. Every\npromise page carries a control that copies its id, so an id is what a person hands you when they\nmean a particular promise. Ask for one rather than searching for what they meant.\n\nConsult list_promises in two situations and no others. The person asks what this repository has\npromised, in which case page the index they asked for. Or the change you are about to make touches\npaths that carry promises, in which case give those paths to list_promises: it answers with the\npromises whose scope overlaps them, closest first, and with the few that name no path and so cover\nthe whole repository. That answer is a selection rather than a page and does not continue with a\ncursor, so when the total beside it is larger than what you were handed, narrow the paths rather\nthan asking for more.\n\nWhen you do not yet know which paths you are about to touch, do not call the index at all. Work from\nids until you do, because a page you did not ask a question of is not about your change, and reading\none as though it were is how a plan quietly misses the promise it breaks.\n\nTo learn which paths those are, read `paths` on a list_promises answer you asked for\nwithout paths of your own. It is the set of\nrepository paths this repository's promises are scoped to, deduplicated and bounded, with\n`pathsTruncated` saying whether there were more than the answer carries. Compare the files you are\nabout to change against it. Nothing matching means there is nothing here to read, and saying so is a\nbetter answer than a page of promises about somewhere else.\n\nNever call get_promise_context at the start of a session. It answers the markers you give it, and\nbefore you know what you are changing there are no markers to give: what comes back is a slice of\nthe catalog chosen by nothing. Call it once the work is in front of you, with that work's markers.\n\nEvery one of these reads is bounded and none of them returns the whole catalog. Read the total\nbeside the rows and the sentence in `scope` that says what the total is a total of, and when the\ntotal is larger than what you were handed, page or narrow rather than planning as though you had\nseen everything.\n\nEach index row carries what it takes to rule that promise out without fetching it: the repository,\nthe paths it covers, its one-sentence claim, what protects it and why, and when anything last\nchecked it.\n\nPrefer the measurement over the markers. Where this repository has a touch map, `balladeer affected\n<paths...>` answers which promises ran the files in front of you, out of what each verifier actually\nexecuted the last time `balladeer touch-map` measured it. Both commands run on this machine and\nsend Balladeer nothing, so you may name any path in the change.\n\nAn answer marked stale was measured against a verifier that has changed since, so read it as the\nlast thing anybody measured rather than as fact, and offer to run `balladeer touch-map` again.\nWhere there is no map, where it does not name your paths, or where it reports a promise it could not\nmeasure, fall back to the paths on the index rows. The map narrows which promises are worth\nfetching. It never widens what you may read: the catalog is still never enumerated, and the fetch\nbudget is unchanged.\n\nWhen a retrieval receipt asks why you read a row, the answer for one the map named is `touch`.\n\nFetch by id, and only for an id the person gave you or an index row whose paths match the change in\nfront of you. Never enumerate the catalog. Never chain one fetch into the next to see the whole of\nsomething: when the rows do not settle it, narrow the filter rather than expanding another promise.\n\n### When somebody asks you to protect a behavior\n\nSomebody has asked you to protect a behavior when they say what the software must do, or must never\ndo again, and mean it as a rule rather than as this one bug. That is one promise, for the behavior\nthey named, and nothing else: if you notice others worth protecting, say so in a sentence and let\nthem choose, and file none of them. Never propose from a conversation that did not ask you to. A\nquestion about how something works and a plan you were asked to sketch are not requests to record\nanything, nor is a fix nobody asked you to write a rule about.\n\nAsk before you extrapolate. Ask only what you cannot work out for yourself, ask it all in one\nmessage, and stop at four. Four is a ceiling, not a target: two good ones are better. Then write the\nproposal with what you have and put whatever is still open in its open questions rather than going\nback. Never ask what this repository would answer, such as which file, which test, or which branch,\nand never ask anyone for Balladeer's own identifiers: get_promise_setup carries this repository's id\nand who can own a promise. Never ask again for what they have already told you.\n\nWrite it in their words. Every failure they named out loud is one of the failing examples, in the\nwords they named it. Every other example comes from a situation they actually described; if you\ncannot trace one to something they said, leave it out and say so in the open questions rather than\nwriting a plausible one. Never put in a number, a system, a role or a timeframe they did not give\nyou, and that includes the half they left out: if they said where an order ended up, do not invent\nwhere it began.\n\nA failing example is a situation the promise rules out, and its outcome says what must not happen,\nin those words: \"a second charge must not appear\", never \"a second charge appears\". Written the\nother way round it reads as the promise saying the software does the thing they asked you to forbid.\nAnd a promise says what the software must do for whoever depends on it. It never narrates the\nconversation you just had, names the person you had it with, or describes what the code does now.\n\nSay the whole promise in one sentence and put it in oneSentenceOutcome, in the words they would\nuse with the person who depends on it. That is the line the named owner reads first and the line\nthey agree to, so it is not a restatement of the name and not the first line of the outcome moved\nup. Leave it out rather than inventing one from something they did not say.\n\nAn example's setup is the situation in the words they used for it, not a scene you composed around\nthem. Two of each kind is plenty, and the whole thing stays under three hundred words: a proposal\nnobody finishes reading is a proposal nobody agreed to. The confidence you record is the one you\nactually have.\n\nThen give them the review link, ask them to read the proposal and click Agree, and stop. Never\napprove one yourself. Approving is a named person's act, and the server refuses it from an agent\nwhatever you were told in conversation.\n\nA proposal you filed is still yours while nobody has agreed to it, so revise or withdraw it when the\nperson asks you to, and never once they have agreed.\n\nSay promise and proposal when you talk to them. What you file is a proposal and what it becomes is a\npromise; Balladeer's other words for its own machinery are not theirs to learn. Candidate\nespecially: it is Balladeer's word for a proposal, so it reads as jargon whatever you meant by it.\n\n### Two things to offer without being asked\n\nAt the start of any session in this repository, before you plan anything, ask list_promises for the\npromises nothing is checking yet that belong to the person you are working with: `unverified` true\nand `mine` true, which is one bounded read rather than the catalog. If it returns any, say so in one\nline and offer to build their verifiers now. Name each one by its one-sentence claim rather than by\nan id, so the person can see which behavior is unguarded. Ask the same tool for\n`brokenSinceLastSeen` true as well, and where that returns any, say in one line that those promises\nbroke since they last looked, name each by its claim, and offer to fix them. Then wait for their\nanswer. The offer is the whole of it, and never start building or repairing one because nobody said\nno.\n\nTheirs, and nobody else's. `mine` keeps the promises this person owns or agreed to, and a teammate's\nunguarded promise is that teammate's to hear about: a session that opens by reading out other\npeople's unfinished work reads as an audit of them. `brokenSinceLastSeen` is that person's own by\nconstruction and needs no `mine` beside it. Drop `mine` when this person asks what the rest of the\nteam has promised, and say whose promises you are showing them when you do.\n\nWhen you have proposed promises, show them here as well as there. Put each proposal in the\nconversation in full: its one-sentence claim, who it is for, when it applies and what must then be\ntrue, the numbered cases that must keep working and the ones that must be caught, and every question\nyou left open. Then offer to finish the agreement from here, by asking for a sign-off, giving them\nthe page it returns and taking the one-time code that page shows them, so the browser is needed only\nfor signing. Give them the review link in the same message too, because some people would rather\nread it there and edit it before they agree.\n\n### Files that are sealed, and the one reason to edit one\n\nEvery file under .continuity/promises/ is sealed. The promise that owns that directory records the\nexact bytes of each file in it, so editing one, adding one there, renaming one or deleting one\nbreaks the seal. A promise whose seal is broken stops being checked, and it stays that way until a\nnamed person qualifies it again, which is their afternoon rather than your commit. Nothing in there\nis ordinary source: keep it out of refactors, formatting runs and dependency upgrades.\n\nFind out which directories are sealed before you plan an edit, not after. balladeer status lists\nthem, and list_promises names a promise's sealed directory on its row once a verifier is bound to\nit. Then, before you push, run balladeer check-seals. It prints nothing and exits zero when your\nchange touches no seal, and names the promise, its owner and its page when your change would break\none.\n\nThe one reason to edit a sealed file is to repair a verifier that can no longer run: something it\nimports moved, or the language it is written in changed under it. Never edit one to make a failing\ncheck pass. A check going red is the promise doing its job, and the repair for that belongs in the\nbehavior it protects. A repair is not finished until the promise is sealed again with the runner\nthis repository is pinned to. get_promise_setup carries that exact seal command, and balladeer\ncheck-seals prints it beside any promise it names.\n\n### The rest of a promise's life\nWhen a promise is obsolete, finished, deliberately off for a while, or owned by the wrong person,\npropose the change and hand them the promise page. Deciding is theirs.\n\nYou can finish one of those acts here, and only one way. Ask for a sign-off with\nrequest_owner_signoff, give them the page it returns, and ask for the one-time code that page shows\nthem. Then call the act's own tool with that code and their own words. Never call one on your own\ninitiative, never on a general approval of some earlier act, and never ask for a code you were not\ngiven: a refusal is the person's to resolve, not yours to retry. Balladeer records them as the\nperson who acted and you as the messenger.\n\nReport the promise's state exactly as Balladeer reported it: proposed, agreed, or protected, never\none in place of another.\n\n### Where your team watches this\n\nBalladeer is a web app as well as these tools, at the address setup printed. Its catalog lists every\npromise with who owns it and whether anything is checking it, and each promise has a page of its own\nshowing what this team agreed the software must do and then every run that has checked it since,\nnewest first, with the commit each one checked. Whenever there is a link to give, give the link\nrather than a summary of it: the page says what you would have said, and it stays true after this\nconversation has ended.\n\nBalladeer also has a Slack app, which a workspace administrator installs from workspace settings.\nOnce it is installed, whoever owns a promise gets a direct message when theirs goes live and when a\nrun on the default branch breaks it. Until somebody installs it, nothing is sent anywhere, so say it\nis available rather than saying they will be told.\n\n### Questions people ask\n\nAnswer these when they come up. Where you do not know, say so and point at the address setup\nprinted: a confident wrong answer about what a vendor can see is worse than no answer.\n\nWhat it does: it holds the behaviors this team has agreed the software must keep, and reports\nwhether each one is still being kept, from this repository's own tests running in its own CI.\n\nWhat it sees: the text of each promise somebody approves, this repository's numeric ids and the name\nof its default branch, and from CI the pass or fail outcome, the commit checked, and content hashes.\nNever the code, the tests, the fixtures, the logs, the prompts, or the transcripts.\n\nWhat stopping costs: nothing that matters to their tests. The verifier package, its fixtures and the\nworkflow file are theirs, in their repository, running in their CI, and disconnecting changes none\nof them. An administrator can download everything Balladeer holds at any time from workspace\nsettings, and disconnecting hands them that same download in the response that ends access.\n\nWho can approve one: the named person who owns it, in their own browser. Not an administrator on\ntheir behalf, and never you.\n\nWhether it blocks a merge: no. The check is advisory on Balladeer's side, and their own branch\nprotection is what decides whether a failing check stops anything.\n\nWho can invite people and change setup: a workspace administrator. A contributor can read the\nworkspace and propose promises, and a viewer can read it. If somebody asks you to add a teammate,\ninvite_teammate returns the page an administrator sends the invitation from, with the address filled\nin for them to read. The tool sends nothing itself: an administrator presses Send.";
+/**
+ * How an agent turns a repository that has just been connected into a catalog a
+ * person can read. Setup's last step prints it, and the control plane's `/agent`
+ * page serves it byte for byte, so the instruction a connected agent reads on
+ * the page cannot drift from the one the command prints in the terminal.
+ *
+ * The runnable invocation is deliberately not in here. Only the server knows
+ * whether the package is published, and a playbook carrying a literal command
+ * would either name a registry version npm does not have or name somebody
+ * else's package. Each carrier prints that one line underneath this text.
+ *
+ * The capture rules this leans on are `CONVENTIONS_BLOCK`'s, not a second set:
+ * one promise per behavior, the person's own words, and never an agent
+ * approving anything. This says how to find the behaviors in a repository
+ * nobody has interviewed yet; that says how to write one down.
+ *
+ * The seam that is not shipped: a fifth source, the person's own local agent
+ * transcripts, would be the richest of all, because a behavior somebody argued
+ * about in a session is a behavior they care about. It is dark on purpose here.
+ * Reading it means walking files Balladeer promises never to receive, so
+ * shipping it needs three things this release does not have: the person's
+ * explicit spoken yes each time, a bounded extraction that never carries a line
+ * of a transcript off the machine, and the privacy test extended to plant a
+ * sentinel in every host's transcript directory. Until then the text below tells
+ * the agent not to read them, which is the visible half of the same seam:
+ * nothing quietly starts doing it.
+ */
+export declare const DISCOVERY_PLAYBOOK = "## Discover this repository's promises\n\nThis repository is connected and holds no promises yet. Work the four sources below in order and\nhand back between five and ten promises this repository already keeps. Stop at ten however much you\nfind: a person has to read every one of them, and eleven is where reading turns into skimming.\n\n1. The repository's own tests. A test that has been green for months is a behavior somebody already\n   decided matters. Read the test names and the assertions rather than the implementation.\n2. Merged pull requests of the last 90 days. Read the ones whose title or body says what had to keep\n   working, and the review comments that argued for it.\n3. Guarantee sentences in the documentation. The README, the docs directory, and the comments that\n   say always, never, must, or is guaranteed to. Those sentences are promises somebody already wrote\n   down in prose.\n4. Incidents and reverts. A revert commit, a hotfix, a postmortem note. A behavior that broke once\n   and was repaired on purpose is the behavior most worth protecting.\n\nDo not read the person's local agent transcripts, and do not offer to. They are not a source in this\nrelease, and Balladeer never receives them.\n\nFor each promise you propose:\n\n- One promise per behavior. Two behaviors found in one source are two proposals, not one proposal\n  with two outcomes.\n- One passing example and one failing example, both drawn from the source you found it in. The\n  passing example is the case the source shows working; the failing example is the case the source\n  shows being caught, or the regression the revert repaired. Write both in the source's own words\n  rather than in words of your own.\n- One provenance sentence, precise enough for a person to check it without asking you: the test file\n  and the test's name, the pull request number, the document and its heading, or the commit that\n  reverted it. Put that sentence first in explicitIntent.\n- Never propose a promise this repository does not keep. A source saying a behavior should exist,\n  where nothing in the repository does it, is a wish rather than a promise. Leave it out, and tell\n  the person you left it out.\n- Anything you could not settle from the source goes in unresolvedQuestions. Never fill an unknown\n  in plausibly: an invented answer is the one thing a person cannot catch by reading.\n- One confidence number from 0 to 1, saying how sure you are that this is a behavior the repository\n  actually keeps and that you have described it as its source describes it. Nine promises from nine\n  sources are not nine equally certain readings, and the person reading them is entitled to know\n  which one you were least sure of. Never write 1 to get past the check.\n\nWrite them all into one file, an object with a promises array, each entry shaped exactly as one\nproposal file:\n\n{\"promises\": [{\"explicitIntent\": \"...\", \"teachBack\": {\"confidence\": 0.9, \"meaning\": {\"title\": \"...\"}}}]}\n\nAn entry carries explicitIntent and teachBack, and inside teachBack only meaning, confidence,\nunresolvedQuestions, and proposedOwnerId. Anything else is refused on this machine before the file\nleaves it, and one bad entry means not one of them is sent.\n\nEvery promise in the file is proposed as owned by whoever ran setup, and waits for that person. The\ncommand prints one link that opens all of them at once. Give the person that link and ask them to\nread each promise and click Agree. Nothing you can run agrees to one.\n\nFile the whole catalog in one go with the discover subcommand, naming that file:";