@intentic/sandbox-contract 1.307.0 → 1.308.0

package/src/contracts/capabilities.contract.ts

@@ -1,4 +1,4 @@
-import { oc } from "@orpc/contract";
+import { procedure } from "../protocol/route-meta.js";
 import { streamOf } from "../protocol/routes.js";
 import { IntenticLineSchema } from "../events/system-events.js";
 import {
@@ -18,10 +18,13 @@ import { MarketplaceRequestSchema, MarketplaceSchema } from "../schemas/marketpl
 import { RemoteRefsRequestSchema, RemoteRefsSchema } from "../schemas/git/remote-refs.js";
 import { OkSchema } from "../schemas/shared.js";
 
+// Connected services name accounts and what this sandbox reaches: the operating tier's, reads included, and no token's.
+const capabilityRoute = procedure.meta({ floor: "maintainer", control: "never" });
+
 // The sandbox's unified capability manifest, spanning `list`/`add`/`remove`/`status`/`marketplace`. A VAULTED marker
 // with nothing stored behind it is refused rather than silently written.
 export const capabilitiesContract = {
-    list: oc
+    list: capabilityRoute
         .route({
             method: "GET",
             path: "/capabilities",
@@ -30,7 +33,7 @@ export const capabilitiesContract = {
                 "Each connection with its live state, the settings that are safe to show, and the names of the credentials it holds. The values of those credentials are never in the answer, on any route but one.",
         })
         .output(CapabilitiesListSchema),
-    add: oc
+    add: capabilityRoute
         .route({
             method: "POST",
             path: "/capabilities",
@@ -41,7 +44,7 @@ export const capabilitiesContract = {
         .input(CapabilitySchema)
         .output(streamOf(IntenticLineSchema)),
     // A credential the caller is keeping arrives as VAULTED here too, so an edit can be tested without retyping a key.
-    probe: oc
+    probe: capabilityRoute
         .route({
             method: "POST",
             path: "/capabilities/probe",
@@ -49,9 +52,11 @@ export const capabilitiesContract = {
             description:
                 "Dials the service the way this connection would and hands back what it said, before anything is written. The answer is the service's own confirmation or its exact refusal, so a wrong token or an unreachable host is found on the form rather than on a card afterwards.",
         })
+        // Sends a stored key to a caller-supplied host: withheld from the panel token every panel process holds.
+        .meta({ panel: false })
         .input(CapabilitySchema)
         .output(CapabilityProbeSchema),
-    remove: oc
+    remove: capabilityRoute
         .route({
             method: "DELETE",
             path: "/capabilities/{id}",
@@ -61,7 +66,7 @@ export const capabilitiesContract = {
         })
         .input(CapabilityIdParamSchema)
         .output(OkSchema),
-    rename: oc
+    rename: capabilityRoute
         .route({
             method: "POST",
             path: "/capabilities/{id}/rename",
@@ -72,7 +77,7 @@ export const capabilitiesContract = {
         .input(CapabilityRenameSchema)
         .output(OkSchema),
     // Called by the /secrets page's edit action.
-    setSecret: oc
+    setSecret: capabilityRoute
         .route({
             method: "POST",
             path: "/capabilities/{id}/secret",
@@ -81,7 +86,7 @@ export const capabilitiesContract = {
         })
         .input(CapabilitySecretInputSchema)
         .output(OkSchema),
-    status: oc
+    status: capabilityRoute
         .route({
             method: "GET",
             path: "/capabilities/{id}/status",
@@ -91,7 +96,7 @@ export const capabilitiesContract = {
         .input(CapabilityIdParamSchema)
         .output(CapabilityStatusSchema),
     // Gated by `permissions.daemon` in the manifest (ext-deployments reads its Komodo key pair this way).
-    connection: oc
+    connection: capabilityRoute
         .route({
             method: "GET",
             path: "/capabilities/{id}/connection",
@@ -99,9 +104,11 @@ export const capabilitiesContract = {
             description:
                 "The one call that hands back stored secrets, so an extension's own backend can dial the service behind a connection. Never answered for a signed-in person: only a machine credential reaches it, and an extension's only if its manifest asked for this route out loud at install time.",
         })
+        // Answers with the secrets included: withheld from the panel token every panel process holds.
+        .meta({ panel: false })
         .input(CapabilityIdParamSchema)
         .output(CapabilityConnectionSchema),
-    marketplace: oc
+    marketplace: capabilityRoute
         .route({
             method: "POST",
             path: "/capabilities/marketplace",
@@ -111,7 +118,7 @@ export const capabilitiesContract = {
         .input(MarketplaceRequestSchema)
         .output(MarketplaceSchema),
     // What the install form pins to, so nobody has to read a commit sha off a web page and paste it.
-    refs: oc
+    refs: capabilityRoute
         .route({
             method: "POST",
             path: "/capabilities/refs",
@@ -121,7 +128,7 @@ export const capabilitiesContract = {
         })
         .input(RemoteRefsRequestSchema)
         .output(RemoteRefsSchema),
-    dismiss: oc
+    dismiss: capabilityRoute
         .route({
             method: "DELETE",
             path: "/capabilities/recommendations/{entry}",
@@ -132,7 +139,7 @@ export const capabilitiesContract = {
         .input(CapabilityEntryParamSchema)
         .output(OkSchema),
     // Runs the capability's declared `loginCommand` in the terminal session the panel attaches to.
-    login: oc
+    login: capabilityRoute
         .route({
             method: "POST",
             path: "/capabilities/{id}/login",
@@ -143,7 +150,7 @@ export const capabilitiesContract = {
         .input(CapabilityIdParamSchema)
         .output(CapabilityLoginSchema),
     // The seed comes from the config field the card marks `totp`.
-    otp: oc
+    otp: capabilityRoute
         .route({
             method: "GET",
             path: "/capabilities/{id}/otp",
@@ -151,6 +158,8 @@ export const capabilitiesContract = {
             description:
                 "Generates a single two-factor code from a stored seed. The one credential-adjacent read an agent is allowed, and it is safe because a code expires in seconds and never reveals the seed, so an agent can answer a prompt without ever holding the factor.",
         })
+        // The `otp` CLI mints a code on the agent token; it never reads the seed behind it.
+        .meta({ agent: true })
         .input(CapabilityIdParamSchema)
         .output(CapabilityOtpSchema),
 };

package/src/contracts/chores.contract.ts

@@ -1,4 +1,4 @@
-import { oc } from "@orpc/contract";
+import { procedure } from "../protocol/route-meta.js";
 import { ChoreLedgerWriteSchema, ChoreProbeRequestSchema, ChoresReportSchema } from "../schemas/maintenance.js";
 import { OkSchema } from "../schemas/shared.js";
 
@@ -6,7 +6,7 @@ import { OkSchema } from "../schemas/shared.js";
 // agent (`POST /agent`), reusing its worktree, status, cost and transcript rather than duplicating a launcher here.
 export const choresContract = {
     // Polled by both the rail badge and the panel.
-    list: oc
+    list: procedure
         .route({
             method: "GET",
             path: "/chores",
@@ -15,7 +15,7 @@ export const choresContract = {
                 "Every repo's standing evidence in one read: what the last measurement found and how old it is, the cheap signals that are always current, and what has already been decided about each.",
         })
         .output(ChoresReportSchema),
-    probe: oc
+    probe: procedure
         .route({
             method: "POST",
             path: "/chores/probe",
@@ -26,7 +26,7 @@ export const choresContract = {
         .input(ChoreProbeRequestSchema)
         .output(OkSchema),
     // Also how a snooze is recorded, upserted the same way as a verdict.
-    record: oc
+    record: procedure
         .route({
             method: "POST",
             path: "/chores/ledger",

package/src/contracts/ci.contract.ts

@@ -1,4 +1,4 @@
-import { oc } from "@orpc/contract";
+import { procedure } from "../protocol/route-meta.js";
 import {
     CiFixParamSchema,
     CiFixResponseSchema,
@@ -14,7 +14,7 @@ import { OkSchema } from "../schemas/shared.js";
 // (/ci/webhook/:host) is a plain Hono route, vendors can't do Google ID tokens, so it lives outside this
 // contract, like /automations/{id}/fire.
 export const ciContract = {
-    runs: oc
+    runs: procedure
         .route({
             method: "GET",
             path: "/ci/runs",
@@ -23,7 +23,7 @@ export const ciContract = {
                 "What the forges are reporting for every workspace repo that has a remote, served from a cache and filled in on demand. Repos whose notifications are not wired up say so.",
         })
         .output(CiRunsResponseSchema),
-    rerun: oc
+    rerun: procedure
         .route({
             method: "POST",
             path: "/ci/runs/rerun",
@@ -32,7 +32,7 @@ export const ciContract = {
         })
         .input(CiRunParamSchema)
         .output(OkSchema),
-    cancel: oc
+    cancel: procedure
         .route({
             method: "POST",
             path: "/ci/runs/cancel",
@@ -41,7 +41,7 @@ export const ciContract = {
         })
         .input(CiRunParamSchema)
         .output(OkSchema),
-    jobs: oc
+    jobs: procedure
         .route({
             method: "POST",
             path: "/ci/runs/jobs",
@@ -50,7 +50,7 @@ export const ciContract = {
         })
         .input(CiRunParamSchema)
         .output(CiJobsResponseSchema),
-    fix: oc
+    fix: procedure
         .route({
             method: "POST",
             path: "/ci/fix",

package/src/contracts/diff.contract.ts

@@ -1,10 +1,10 @@
-import { oc } from "@orpc/contract";
+import { procedure } from "../protocol/route-meta.js";
 import { DerivedDiffSchema, DiffSourceQuerySchema } from "../schemas/diff.js";
 
 // What a diff's two sides are besides text: the byte route (/diff/raw) is plain Hono since it streams a body; the
 // derived-text route is here, answering both sides in one call so they render together.
 export const diffContract = {
-    derived: oc
+    derived: procedure
         .route({
             method: "GET",
             path: "/diff/derived",

package/src/contracts/endpoints.contract.ts

@@ -1,4 +1,4 @@
-import { oc } from "@orpc/contract";
+import { procedure } from "../protocol/route-meta.js";
 import { z } from "zod";
 import { CapabilityIdParamSchema } from "../schemas/capabilities.js";
 import { ModelsSchema } from "../schemas/providers/provider-oauth.js";
@@ -87,7 +87,7 @@ export const LocalModelFitSchema = z.object({
 export type LocalModelFitResponse = z.infer<typeof LocalModelFitSchema>;
 
 export const endpointsContract = {
-    models: oc
+    models: procedure
         .route({
             method: "GET",
             path: "/endpoints/{id}/models",
@@ -97,7 +97,7 @@ export const endpointsContract = {
         })
         .input(CapabilityIdParamSchema)
         .output(ModelsSchema),
-    trial: oc
+    trial: procedure
         .route({
             method: "GET",
             path: "/endpoints/trial/status",
@@ -108,7 +108,7 @@ export const endpointsContract = {
         .output(TrialStatusSchema),
     // Sized against this machine rather than a table in the browser, because the numbers that matter (a cgroup cap, a
     // GPU that may not be passed through, weights already on disk) are only knowable in here.
-    localModelFit: oc
+    localModelFit: procedure
         .route({
             method: "GET",
             path: "/endpoints/local-model/fit",
@@ -119,7 +119,7 @@ export const endpointsContract = {
         .output(LocalModelFitSchema),
     // Start or stop fetching the instant model's weights before anyone has asked for them, so the first local turn does
     // not begin with a download. Idempotent: starting twice joins the transfer already running.
-    localModelPrefetch: oc
+    localModelPrefetch: procedure
         .route({
             method: "POST",
             path: "/endpoints/local-model/prefetch",

package/src/contracts/exit.contract.ts

@@ -1,15 +1,18 @@
-import { oc } from "@orpc/contract";
+import { procedure } from "../protocol/route-meta.js";
 import { streamOf } from "../protocol/routes.js";
 import { IntenticLineSchema } from "../events/system-events.js";
 import { ExitCountriesSchema, ExitIdParamSchema, ExitListSchema, ExitObservationSchema, ExitUseInputSchema } from "../schemas/exit.js";
 import { OkSchema } from "../schemas/shared.js";
 
+// The agent's `exit` CLI operates these on the agent token; a control token never reaches them.
+const exitRoute = procedure.meta({ agent: true, control: "never" });
+
 // An exit is added as an `exit` capability; started, moved and rotated here, since switching country is a
 // runtime operation done both by the operator and by the agent's `exit` command on PATH. Each exit publishes an opt-in
 // SOCKS proxy; the sandbox's default route, model endpoint and reachability tunnel never move.
 export const exitContract = {
     // Drives the capability card, the account picker and `geo list` (the CLI is `geo`; `exit` is a shell builtin).
-    list: oc
+    list: exitRoute
         .route({
             method: "GET",
             path: "/exit",
@@ -19,7 +22,7 @@ export const exitContract = {
         })
         .output(ExitListSchema),
     // "Provider" is Tor's directory, VPN Gate's CSV, or pasted confs; this is what auto-fills the country picker.
-    countries: oc
+    countries: exitRoute
         .route({
             method: "GET",
             path: "/exit/{id}/countries",
@@ -29,7 +32,7 @@ export const exitContract = {
         })
         .input(ExitIdParamSchema)
         .output(ExitCountriesSchema),
-    start: oc
+    start: exitRoute
         .route({
             method: "POST",
             path: "/exit/{id}/start",
@@ -39,7 +42,7 @@ export const exitContract = {
         })
         .input(ExitIdParamSchema)
         .output(streamOf(IntenticLineSchema)),
-    use: oc
+    use: exitRoute
         .route({
             method: "POST",
             path: "/exit/{id}/use",
@@ -50,7 +53,7 @@ export const exitContract = {
         .input(ExitUseInputSchema)
         .output(streamOf(IntenticLineSchema)),
     // Cheap on tor (a control-port signal); a re-dial to another server for everything else.
-    rotate: oc
+    rotate: exitRoute
         .route({
             method: "POST",
             path: "/exit/{id}/rotate",
@@ -60,7 +63,7 @@ export const exitContract = {
         })
         .input(ExitIdParamSchema)
         .output(streamOf(IntenticLineSchema)),
-    check: oc
+    check: exitRoute
         .route({
             method: "POST",
             path: "/exit/{id}/check",
@@ -70,7 +73,7 @@ export const exitContract = {
         })
         .input(ExitIdParamSchema)
         .output(ExitObservationSchema),
-    stop: oc
+    stop: exitRoute
         .route({
             method: "POST",
             path: "/exit/{id}/stop",

package/src/contracts/extensions.contract.ts

@@ -1,4 +1,4 @@
-import { oc } from "@orpc/contract";
+import { procedure } from "../protocol/route-meta.js";
 import { CapabilityIdParamSchema } from "../schemas/capabilities.js";
 import {
     ExtensionEnabledInputSchema,
@@ -24,7 +24,7 @@ import { OkSchema } from "../schemas/shared.js";
 // Installed extensions resolved to their approved manifests. The bundle itself is a plain Hono route, `GET
 // /extensions/{id}/bundle`, not part of this oRPC contract: raw ESM bytes aren't a JSON payload.
 export const extensionsContract = {
-    list: oc
+    list: procedure
         .route({
             method: "GET",
             path: "/extensions",
@@ -34,7 +34,7 @@ export const extensionsContract = {
         })
         .output(ExtensionsListSchema),
     // Writes into `.intentic/config/workspace-extensions/<name>/`.
-    create: oc
+    create: procedure
         .route({
             method: "POST",
             path: "/extensions/workspace",
@@ -46,7 +46,7 @@ export const extensionsContract = {
         .output(WorkspaceExtensionCreatedSchema),
     // Read the plan first, then send the removal: the plan is the only place the owner is told what else goes, and the
     // connections it names are not derivable from the manifest alone.
-    removalPlan: oc
+    removalPlan: procedure
         .route({
             method: "GET",
             path: "/extensions/{id}/removal",
@@ -56,7 +56,7 @@ export const extensionsContract = {
         })
         .input(CapabilityIdParamSchema)
         .output(ExtensionRemovalPlanSchema),
-    remove: oc
+    remove: procedure
         .route({
             method: "POST",
             path: "/extensions/{id}/remove",
@@ -66,7 +66,7 @@ export const extensionsContract = {
         })
         .input(CapabilityIdParamSchema)
         .output(ExtensionRemovedSchema),
-    settings: oc
+    settings: procedure
         .route({
             method: "GET",
             path: "/extensions/{id}/settings",
@@ -75,7 +75,7 @@ export const extensionsContract = {
         })
         .input(CapabilityIdParamSchema)
         .output(ExtensionSettingsSchema),
-    setSettings: oc
+    setSettings: procedure
         .route({
             method: "POST",
             path: "/extensions/{id}/settings",
@@ -86,7 +86,7 @@ export const extensionsContract = {
         .input(ExtensionSettingsInputSchema)
         .output(OkSchema),
     // The Extensions tab states which of these apply to a given extension.
-    setEnabled: oc
+    setEnabled: procedure
         .route({
             method: "POST",
             path: "/extensions/{id}/enabled",
@@ -97,7 +97,7 @@ export const extensionsContract = {
         .input(ExtensionEnabledInputSchema)
         .output(OkSchema),
     // The permission gate that produces these counts runs in the browser (apiImpl.ts).
-    recordUsage: oc
+    recordUsage: procedure
         .route({
             method: "POST",
             path: "/extensions/usage",
@@ -107,7 +107,7 @@ export const extensionsContract = {
         })
         .input(ExtensionUsageBatchSchema)
         .output(OkSchema),
-    readiness: oc
+    readiness: procedure
         .route({
             method: "GET",
             path: "/extensions/{id}/readiness",
@@ -119,7 +119,7 @@ export const extensionsContract = {
         .output(ExtensionReadinessSchema),
     // The extensions list itself carries what the periodic registry check found (update/advisory/health per row); these
     // routes are the verbs around it.
-    checkUpdates: oc
+    checkUpdates: procedure
         .route({
             method: "POST",
             path: "/extensions/updates/check",
@@ -128,7 +128,7 @@ export const extensionsContract = {
                 "Compares every installed extension against its source and reports what is newer, what carries an advisory and what looks unhealthy. This also happens on a schedule; call it to check on demand.",
         })
         .output(ExtensionUpdatesCheckedSchema),
-    updatePreview: oc
+    updatePreview: procedure
         .route({
             method: "POST",
             path: "/extensions/{id}/update/preview",
@@ -138,7 +138,7 @@ export const extensionsContract = {
         })
         .input(ExtensionUpdateActionSchema)
         .output(ExtensionUpdatePreviewSchema),
-    applyUpdate: oc
+    applyUpdate: procedure
         .route({
             method: "POST",
             path: "/extensions/{id}/update",
@@ -148,7 +148,7 @@ export const extensionsContract = {
         })
         .input(ExtensionUpdateActionSchema)
         .output(ExtensionUpdateAppliedSchema),
-    revert: oc
+    revert: procedure
         .route({
             method: "POST",
             path: "/extensions/{id}/revert",
@@ -157,7 +157,7 @@ export const extensionsContract = {
         })
         .input(CapabilityIdParamSchema)
         .output(ExtensionUpdateAppliedSchema),
-    setUpdatePolicy: oc
+    setUpdatePolicy: procedure
         .route({
             method: "POST",
             path: "/extensions/{id}/update-policy",
@@ -168,7 +168,7 @@ export const extensionsContract = {
         .input(ExtensionUpdatePolicyInputSchema)
         .output(OkSchema),
     // Declared via `contributes.processes`; the terminals list shows each one's log as `svc-ext-<id>-<name>`.
-    processStatus: oc
+    processStatus: procedure
         .route({
             method: "GET",
             path: "/extensions/{id}/processes/{name}",
@@ -177,7 +177,7 @@ export const extensionsContract = {
         })
         .input(ExtensionProcessParamSchema)
         .output(ExtensionProcessStatusSchema),
-    processStart: oc
+    processStart: procedure
         .route({
             method: "POST",
             path: "/extensions/{id}/processes/{name}/start",
@@ -186,7 +186,7 @@ export const extensionsContract = {
         })
         .input(ExtensionProcessParamSchema)
         .output(OkSchema),
-    processStop: oc
+    processStop: procedure
         .route({
             method: "POST",
             path: "/extensions/{id}/processes/{name}/stop",