@quantiya/codevibe-core 2.0.1 → 2.0.3

package/dist/__tests__/prompt-parser.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/adapter/registry.d.ts

@@ -1,5 +1,6 @@
 import type { AuthorityScope } from '../local-executor/authority';
 import type { AgentKind, ImplementorHandle, ProcessRole } from '../local-executor/types';
+import type { SubstrateHandle } from '../substrate/types';
 import { ReviewerRegistry } from '../reviewer/registry';
 import type { ReviewerSpec } from '../reviewer/provider';
 import type { ReviewerVerdict } from '../reviewer/types';
@@ -7,18 +8,84 @@ import { CapabilityRegistry, type AdapterCapabilities } from './capabilities';
 import { type AcceptedPacketReceipt, type AdapterPacket, type ContinuationPacket, type TaskPacket } from './packets';
 import type { AdapterProgressHooks } from './progress';
 import type { AgentAdapter, ProbeResult, ProbeRole } from './types';
+/**
+ * CP-7 PART F — the structural substrate-engager seam (mirrors
+ * `SubstrateLaunch.engageSubstrate` / the LE's `SubstrateEngager`). OPTIONAL on
+ * the AdapterRegistry: when wired, the single-track (CP-5.b) implementor launch
+ * engages the trusted-execution moat; when absent, the legacy spawn path is
+ * byte-identical (§7 non-regression). Declared structurally so the adapter
+ * module stays decoupled from substrate-launch.
+ */
+export type AdapterSubstrateEngager = (input: {
+    taskId: string;
+    agentKind: AgentKind;
+    workdir: string;
+    role: ProcessRole;
+}) => Promise<{
+    mode: 'substrate';
+    tier: 'docker' | 'sandbox_exec';
+    reducedTrust: boolean;
+    reducedTrustReason?: string;
+    substrateHandle: SubstrateHandle;
+    refreshBrokerToken(): Promise<void>;
+    teardown(): Promise<void>;
+} | {
+    mode: 'reduced_trust';
+    reducedTrust: true;
+    reducedTrustReason: string;
+    teardown(): Promise<void>;
+}>;
+/**
+ * CP-7 PART F (Stage-2 H-2) — the prominent reduced-trust BADGE sink. The
+ * AdapterRegistry has no shell-event channel of its own; the orchestration shell
+ * injects this so a reduced-trust / coarse implementor launch surfaces the SAME
+ * user-visible NOTIFICATION + structured `reducedTrust: true` flag the LE-level
+ * path emits — NOT a bare log. `tier: 'none'` = moat OFF (legacy spawn); a real
+ * tier = coarse (engaged but weakened). When ABSENT, the registry STILL refuses
+ * to run a reduced-trust implementor on only a log — see `launchImplementor`
+ * (it fails closed rather than spawn un-badged).
+ */
+export type ReducedTrustNotifier = (badge: {
+    agentKind: AgentKind;
+    reducedTrustReason: string;
+    tier: 'none' | 'docker' | 'sandbox_exec';
+}) => Promise<void> | void;
 export declare class AdapterRegistry implements AgentAdapter {
     private readonly scope;
     private readonly reviewers;
     private readonly capabilityRegistry;
-    constructor(scope: AuthorityScope, reviewers: ReviewerRegistry, capabilityRegistry: CapabilityRegistry);
+    private readonly substrateEngager?;
+    private readonly notifyReducedTrust?;
+    constructor(scope: AuthorityScope, reviewers: ReviewerRegistry, capabilityRegistry: CapabilityRegistry, substrateEngager?: AdapterSubstrateEngager | undefined, notifyReducedTrust?: ReducedTrustNotifier | undefined);
     capabilities(agent: AgentKind): AdapterCapabilities;
     acceptPacket(packet: AdapterPacket, processRole: ProcessRole): AcceptedPacketReceipt;
     launchImplementor(scope: AuthorityScope, packet: TaskPacket | ContinuationPacket, hooks: AdapterProgressHooks): Promise<ImplementorHandle>;
+    /**
+     * Stage-2 H-2 — surface the PROMINENT reduced-trust badge: a WARN log AND
+     * (when a notifier is wired) the user-visible NOTIFICATION carrying the
+     * structured `reducedTrust: true` flag. The moat being OFF / weakened is
+     * VISIBLE + auditable, never a bare log.
+     *
+     * W2 Stage-2 HIGH — DELIVERY DISCIPLINE per tier:
+     *   - `tier: 'none'` (moat fully OFF — the agent runs unsandboxed with ambient
+     *     creds reachable): the badge MUST be DELIVERED. A `notifyReducedTrust`
+     *     throw PROPAGATES (we do NOT swallow it) so `launchImplementor` fails
+     *     closed and never spawns an un-badged unsandboxed implementor. The WARN
+     *     log alone is NOT sufficient. (The `launchImplementor` call site already
+     *     fails closed when NO notifier is wired; this extends that to "notifier
+     *     present but delivery failed".)
+     *   - `tier: 'sandbox_exec' | 'docker'` (still SANDBOXED): best-effort — a
+     *     notifier throw is logged + swallowed (the agent is contained, so a
+     *     missed coarse badge does not warrant crashing the launch).
+     */
+    private surfaceReducedTrust;
     evaluateReviewer(spec: ReviewerSpec, gateId: string): Promise<ReviewerVerdict>;
     probe(agent: AgentKind, role: ProbeRole): Promise<ProbeResult>;
     refreshCapabilities(agent: AgentKind, role?: ProbeRole): Promise<AdapterCapabilities>;
     private assertAgentAvailable;
     private spawnArgsForProbe;
 }
-export declare function createDefaultAdapterRegistry(scope: AuthorityScope): AdapterRegistry;
+export declare function createDefaultAdapterRegistry(scope: AuthorityScope, opts?: {
+    substrateEngager?: AdapterSubstrateEngager;
+    notifyReducedTrust?: ReducedTrustNotifier;
+}): AdapterRegistry;

package/dist/appsync/__tests__/appsync-client-event-source-filter.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/appsync/__tests__/appsync-client-task-group.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/appsync/__tests__/cleanup-subscription.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/appsync/__tests__/coerce-awsjson-and-review-summary.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/appsync/__tests__/cp1f-quorum-sdk.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/appsync/__tests__/event-throttle.test.d.ts

@@ -0,0 +1 @@
+export {};