@integrity-labs/agt-cli 0.28.1003 → 0.28.1005

package/dist/{chunk-BMDLKZHZ.js → chunk-DVSYT4MU.js}

@@ -756,7 +756,7 @@ Route durable work by what it is:
 | A one-shot reminder or single future run | Scheduled task | \`mcp__augmented__schedule_create\` |
 ${workflowRow}| A dashboard or refreshable report surface | Console dashboard | \`dashboards_upsert\` - see \xA7 Dashboards |
 | Facts, preferences, session context | Memory | your memory files - see \xA7 Memory (there, local files ARE the canonical store by design) |
-| Code in a cloned repository | Git | commit and push under \`~/code/\` - see \xA7 Development Workflow |
+| Code in a cloned repository | Git | commit and push from \`../code/\` - see \xA7 Development Workflow |
 
 Boundaries, so this rule never blocks real work:
 
@@ -1623,10 +1623,11 @@ in \`project/\`, commit it, or publish it as an artefact.
 
 ## Development Workflow
 
-Clone repositories under \`~/code/\`, keeping your workspace separate from agent
-config files. For code tasks always use **git worktrees** rather than switching
-branches, so parallel work never disrupts running services, other agents, or the
-main checkout:
+Clone repositories in \`../code/\` (sibling of \`project/\`), **not \`~/code/\`**
+(destroyed on a container rebuild).
+
+Always use **git worktrees** rather than switching branches, so parallel work
+never disrupts services, other agents, or the main checkout:
 
 1. \`git worktree add ../repo-issue-name -b feature/issue-name origin/main\`
 2. Work in the worktree \u2014 the main repo stays on its current branch.
@@ -3153,6 +3154,52 @@ var INTEGRATION_REGISTRY = [
       }]
     }
   },
+  {
+    // ENG-10854 / ADR-0110. The POLICY half of the catalog definition: this
+    // registry is what `isPremiumDefinition` reads, so the premium descriptor
+    // here is what makes the per-org opt-in required at all. The CUSTOMER-FACING
+    // half - the seeded `integration_definitions` row that the Add Integration
+    // picker lists - is deliberately NOT in this change. `/integrations/installs`
+    // reads the DB catalog with a status filter; this registry is not a listing.
+    //
+    // The order matters and is not bookkeeping: `isOrgEntitledToPremium` returns
+    // TRUE for a definition it does not know as premium, because a free
+    // integration has no opt-in concept. So a broker shipped ahead of this entry
+    // would serve an org that had never opted in. The broker additionally fails
+    // closed on `isPremiumDefinition` being false, so the two halves cannot come
+    // apart in that direction either.
+    id: "typed-evaluation",
+    name: "Typed Evaluation",
+    category: "knowledge",
+    description: "Ask closed questions about a piece of text and get calibrated answers back \u2014 yes/no, pick-one, or a position on your own scale \u2014 with a probability for each. It never writes text and cannot answer outside the set of options you give it, which is what makes it safe to point at content you do not trust. Typical uses: is this message a repeat request, which category does this belong to, how urgent does this sound. Answers arrive in about half a second, so an agent can branch on one without spending a model turn.",
+    // No customer credential exists: the call runs on Ninjafy's own gateway key.
+    supported_auth_types: ["none"],
+    capabilities: [
+      {
+        id: "typed-evaluation:evaluate",
+        name: "Evaluate Text",
+        description: "Ask closed questions about text the agent already holds and receive typed answers with probabilities (evaluate_text).",
+        access: "read"
+      }
+    ],
+    beta: true,
+    // ENG-8842's `included`, and the reason is the consent dialog rather than
+    // the price. `pricing` drives the org admin's acknowledgement modal, where
+    // `usage` renders as "manages and bills by usage" and `monthly` as a
+    // subscription. Both would be false statements here: a call costs about
+    // $0.000076 and nothing is metered or billed, so the opt-in exists to record
+    // a decision about a SUB-PROCESSOR, not about money.
+    //
+    // ADR-0110 Decision 11 keeps the door open deliberately: if a genuinely
+    // high-volume capability arrives later - bulk classification of a customer's
+    // own corpus - it is priced at THAT capability's grain and this definition
+    // stays `included`. Ninja Notes is the precedent (ENG-9278): it acquired a
+    // metered capability and did not flip.
+    premium: {
+      pricing: "included",
+      note: "Typed evaluation is included in your plan \u2014 nothing is metered per question. Turning it on is a decision about data, not cost: the text an agent asks about is sent to Typesafe, through our own gateway, to be scored. It is never used to train a model and we store only the answers, never the text."
+    }
+  },
   {
     // Ninja Notes (ADR-0063, ENG-8842). Meeting capture on the user's own Mac,
     // delivered to an agent as a tag-granted note the agent reads and summarises.
@@ -6273,6 +6320,33 @@ var FLAG_REGISTRY = [
     // "these hosts are unreadable". Both outlive this particular version.
     since: "0.28.667"
   },
+  {
+    // ADR-0110 Decision 5 (ENG-10854). Gates PLATFORM-INTERNAL consumers of the
+    // typed evaluation capability - inbound triage, kanban classification,
+    // memory-extraction sensitivity gating, and later the conversation
+    // evaluator. Nobody "installs" those; they are ours, so they are gated
+    // centrally.
+    //
+    // IT DOES NOT GATE THE AGENT TOOL, and that separation is the point. The
+    // agent tool's gate is the customer's own premium opt-in plus a per-agent
+    // install (Decision 4). Pointing this flag at the tool as well would give
+    // it two masters and let a staff flag silently override a decision the
+    // customer made about their own data reaching a sub-processor.
+    //
+    // Ships with no readers: the consumers land in later slices, and the flag
+    // exists now so the first of them has a gate to be born behind rather than
+    // acquiring one afterwards.
+    key: "typed-evaluation",
+    description: "ADR-0110: platform-internal consumers of the typed evaluation model (Jev, via our AI Gateway). OFF (default) = no internal consumer calls it; ON = consumers that have shipped may call, each still subject to the per-org quota, per-agent rate limit and audit row enforced in the broker. Does NOT gate the agent-facing tool, which is governed by the premium opt-in and a per-agent install instead. Customer orgs stay off until the Decision 9 vendor gates close (sub-processor listing with DPA coverage, the legal read on emotion inference, and a recorded disclosure).",
+    flagType: "boolean",
+    // Ships dark. Every consumer degrades to its current behaviour when off,
+    // so the safe value and the no-op value are the same one.
+    defaultValue: false,
+    // Turning it on starts sending customer text to an external sub-processor
+    // on paths the customer did not individually opt into, which is exactly the
+    // class ADR-0022 section 4 reserves the confirmation for.
+    sensitive: true
+  },
   {
     key: "conversation-eval-backend",
     description: "Backend for host-side conversation-success scoring AND memory extraction (ENG-6581), which share one scorer: anthropic-api = Haiku via a direct Anthropic Messages API fetch (no subprocess); claude-p = Haiku via the `claude -p` subprocess (reuses the agent auth, effectively free under Max but a heavy spawn); local = an OpenAI-compatible loopback endpoint (transcript never leaves the host). Auth for the anthropic-api path comes from AGT_CONV_EVAL_ANTHROPIC_API_KEY (falls back to ANTHROPIC_API_KEY); with no key that path fails closed (eval disabled) rather than reverting to claude-p. Enum.",
@@ -8547,7 +8621,11 @@ ${toolsList}
 ## Git Workflow
 
 Use **git worktrees** for all feature work. Do not switch branches on the main checkout.
-Store repositories under \`~/code/\` and create worktrees alongside them for parallel tasks.
+Store repositories in \`../code/\` - the \`code/\` directory beside the agent's \`project/\` working
+directory, inside the agent's own tree - which is what makes it the agent's to keep. Where this
+host runs agents in containers that tree is bind-mounted and survives a rebuild, while \`~/code/\`
+is container-local and is destroyed by one. Create worktrees alongside the checkout for parallel
+tasks.
 `;
 }
 
@@ -15293,4 +15371,4 @@ export {
   peekCurrentSession,
   readDailySessionPin
 };
-//# sourceMappingURL=chunk-BMDLKZHZ.js.map
+//# sourceMappingURL=chunk-DVSYT4MU.js.map