@yadsh/dsh-qa-surface 0.15.2 → 0.15.3

package/lib/types/access/model.d.ts

@@ -64,6 +64,19 @@ export declare function withdrawnSkillNames(config: QaCapabilityConfig): Readonl
  */
 export declare function personalUserSkillNames(config: QaCapabilityConfig, ownSkills: ReadonlySet<string> | undefined): readonly string[];
 export declare function resolveCapabilityPolicy({ config, subroleId, systemTools, systemSkills, available: installed, skillMetadata, revision, }: ResolveCapabilityPolicyInput): QaEffectiveCapabilityPolicy;
+/**
+ * The skills a person may invoke under one policy — the whole of the
+ * user-facing allow-list, and the one place it is read.
+ *
+ * An empty `userSkills` means the role keeps no separate user list, not that it
+ * grants nothing, so the model-facing set stands in for it. A typed gesture is
+ * admitted or refused by this list and the palette is narrowed by it, so both
+ * have to derive it here: a name the palette offers but the line refuses, or
+ * one the palette hides while the line would accept, is one rule read two ways.
+ *
+ * @param policy - the effective capability policy of one session.
+ */
+export declare function userInvocableSkillNames(policy: QaEffectiveCapabilityPolicy): readonly string[];
 export interface ResolveSkillAccessInput {
     readonly config: QaCapabilityConfig;
     /** Every discovered skill with its normalized metadata. */

package/lib/types/access/service.d.ts

@@ -158,6 +158,32 @@ export declare class QaAccessService {
     policyForSessionOwner(owner: {
         readonly id: string;
     } | undefined, sessionId: string, agent: Agent): Promise<QaResolvedSessionPolicy | undefined>;
+    /**
+     * The policy one session record answers with: the snapshot it froze, or the
+     * role as it is configured now when the chat has never frozen one.
+     *
+     * Every read of a session's capabilities goes through here, so a chat that is
+     * running and a chat nobody has woken cannot disagree about what its role
+     * grants.
+     */
+    private policyForRecord;
+    /**
+     * The policy of a chat this process holds no live agent for.
+     *
+     * A cold chat has an owner and a role, and the reads that name its
+     * capabilities must narrow it by the rule above — the same one a live chat is
+     * narrowed by — rather than answer "no role opinion" because the agent that
+     * carries the capability snapshot happens to be asleep. What a cold chat has
+     * no answer for is that snapshot: the catalog the deployment mounts for every
+     * chat stands in for the agent's own, which is why the project layer of this
+     * chat's workspace is missing from it, and why nothing is frozen onto the
+     * session record here — a palette read must not decide what a later turn may
+     * do.
+     *
+     * @returns the resolved policy; the ownership check is the refusal, so a
+     *   foreign browser never reaches it.
+     */
+    policyForColdSession(token: string, sessionId: string): Promise<QaEffectiveCapabilityPolicy>;
     /** The browser's entry point: the token resolves the owning account. */
     policyForSession(token: string, sessionId: string, agent: Agent): Promise<QaResolvedSessionPolicy | undefined>;
     /** Activation history of one session, for review and quality analysis. */

package/lib/types/index.d.ts

@@ -107,10 +107,12 @@ export declare class QaSurface extends TypertRemoteService {
      * check and the deployment's lockdown is the boundary, exactly as it is for
      * every other remote.
      *
-     * The grant mirrors `installQaSkillPolicy` to the letter — an empty
-     * `userSkills` list means the role keeps no separate user list, not that it
-     * grants nothing — so the palette can never offer a skill the typed gesture
-     * would refuse, nor hide one it would accept.
+     * The grant is {@link userInvocableSkillNames} — the one list the typed
+     * gesture is admitted or refused by — for every chat that has a role, woken
+     * or not: the palette a visitor sees before the chat runs is narrowed by that
+     * same rule, so it can neither offer a name the line would refuse nor hide
+     * one it would accept. `undefined` is answered only where the deployment has
+     * no roles to consult at all.
      */
     private slashSessionGrant;
     /**

package/lib/types/slash/catalog.d.ts

@@ -39,6 +39,11 @@ export interface BuildSlashCatalogOptions {
      * The session role's own user-skill grant, when the access system is on.
      * `undefined` means the role system has no opinion, which is its state on a
      * deployment that never enabled roles — not "grant nothing".
+     *
+     * This is the only grant a read may answer with, whatever the chat looks
+     * like: a chat that is running and a chat nobody has woken are narrowed by
+     * the same allow-list and the same role, because the palette that names a
+     * skill this chat may not invoke teaches the visitor a gesture that fails.
      */
     readonly grantedSkills?: readonly string[] | undefined;
     readonly commandSurface: QaSlashCommandSurface;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yadsh/dsh-qa-surface",
-  "version": "0.15.2",
+  "version": "0.15.3",
   "description": "A focused end-user QA surface backed by native DeepSeek Harness sessions",
   "repository": {
     "type": "git",
@@ -135,10 +135,10 @@
   "dependencies": {
     "yaml": "^2.9.0",
     "zod": "^4.4.3",
-    "@yadsh/dsh-audit-core": "^0.1.1",
     "@yadsh/dsh-audit-ui": "^0.1.2",
-    "@yadsh/dsh-plugin-kit": "^0.5.0",
     "@yadsh/dsh-documents": "^0.6.2",
+    "@yadsh/dsh-plugin-kit": "^0.5.0",
+    "@yadsh/dsh-audit-core": "^0.1.1",
     "@yadsh/dsh-plugin-log": "^0.4.1"
   },
   "devDependencies": {