internal/

Package adapterkit holds the helpers every first-party adapter needs but no vendor SDK touches: schema rendering, the terminal-error rule (with the context-overflow mapping and the marker table mw's retry classifier reads), and the FilePart exactly-one guard.

Package dblock is the one-Studio-per-database rule of the weft command (B7-fix): `weft studio` and `weft dev` hold an exclusive lock on <db>.lock, beside a SQLite database file, for as long as they serve it, taken before the port policy runs.

Package discovery is how an app finds the running Studio with no configuration (plan B3): `weft studio` and `weft dev` write a small file, studio.json, naming the Studio they serve, and weft/otel and weft/runtime read it when nothing else names one.

Package doctor is `weft doctor` (plan B5): it asks a running Studio what it is and how it is wired, and prints one line per check.

Package facadegen writes a facade package: one that re-exports another package's whole exported API under a new import path, so github.com/weftgo/weft (the framework) offers the loop that github.com/weftgo/weft/core (the slim module) implements, under the same names.

Package linkreg is the process's open runtime links as an embedded Studio sees them (U20.2, UX-D-01): weft/runtime adds a link when Install opens it and removes it when the link stops, and weft/studio reads the list for /api/meta's runtime_link — whether this process's link talks to this very server in-process, or which Studio it dialled instead.

Package listen is the Studio command's port policy (plan B2): one default port, 7331, stable and reusable, never silently different.

Package provenance carries, on the context a thread session's decision is recorded under, the class its resumed calls' approvals are reported as (weft.tool.approved_by, record contract §3) when a layer above thread decides through the session's own door on someone's behalf — weft/runtime's playground deciding a fork's parked turn reads "runtime", as its ephemeral resumes do, never the Decide door's "user".

Package termsafe makes untrusted text safe to print to an operator's terminal: the CLI's tables (weft runs, weft doctor) print prompts, agent names and error text that came from an app or an OTLP sender, and a control character in them — an escape sequence, a carriage return — would reach the terminal raw.