@gotgenes/pi-permission-system 10.5.0 → 10.5.2

package/src/agent-prep-session.ts

@@ -1,28 +0,0 @@
-import type { ExtensionContext } from "@earendil-works/pi-coding-agent";
-
-import type { GateHandlerSession } from "./gate-handler-session";
-import type {
-  SkillPermissionChecker,
-  SkillPromptEntry,
-} from "./skill-prompt-sanitizer";
-import type { PermissionState } from "./types";
-
-/**
- * The session surface `AgentPrepHandler` invokes during `before_agent_start`:
- * bind context + identify the agent (via {@link GateHandlerSession}), check
- * skill permissions for prompt sanitization (via {@link SkillPermissionChecker}),
- * refresh config, decide tool exposure, manage the active-tools / prompt-state
- * cache keys, and store the resolved skill entries.
- */
-export interface AgentPrepSession
-  extends GateHandlerSession,
-    SkillPermissionChecker {
-  refreshConfig(ctx?: ExtensionContext): void;
-  getToolPermission(toolName: string, agentName?: string): PermissionState;
-  shouldUpdateActiveTools(cacheKey: string): boolean;
-  commitActiveToolsCacheKey(cacheKey: string): void;
-  getPolicyCacheStamp(agentName?: string): string;
-  shouldUpdatePromptState(cacheKey: string): boolean;
-  commitPromptStateCacheKey(cacheKey: string): void;
-  setActiveSkillEntries(entries: SkillPromptEntry[]): void;
-}

package/src/gate-handler-session.ts

@@ -1,13 +0,0 @@
-import type { ExtensionContext } from "@earendil-works/pi-coding-agent";
-
-/**
- * The session surface `PermissionGateHandler` invokes directly: bind the
- * per-event context and identify the agent.
- *
- * This is the two-method context role both entry points share after [#329]
- * extracted `SkillInputGatePipeline` to own the skill-input gate assembly.
- */
-export interface GateHandlerSession {
-  activate(ctx: ExtensionContext): void;
-  resolveAgentName(ctx: ExtensionContext, systemPrompt?: string): string | null;
-}

package/src/session-lifecycle-session.ts

@@ -1,24 +0,0 @@
-import type { ExtensionContext } from "@earendil-works/pi-coding-agent";
-
-import type { SessionLogger } from "./session-logger";
-
-/**
- * The session surface `SessionLifecycleHandler` invokes across
- * `session_start`, `resources_discover`, and `session_shutdown`: refresh and
- * report config, reset / reload / shut down session state, resolve the agent
- * name, surface config issues, read the runtime context, and log.
- *
- * `activate` is intentionally absent — the lifecycle handler never calls it
- * directly (ISP: do not depend on methods you do not use).
- */
-export interface SessionLifecycleSession {
-  refreshConfig(ctx?: ExtensionContext): void;
-  resetForNewSession(ctx: ExtensionContext): void;
-  logResolvedConfigPaths(): void;
-  resolveAgentName(ctx: ExtensionContext, systemPrompt?: string): string | null;
-  getConfigIssues(agentName?: string): string[];
-  reload(): void;
-  getRuntimeContext(): ExtensionContext | null;
-  shutdown(): void;
-  readonly logger: SessionLogger;
-}