@linxin666/dsh-client-ui-task-board 0.4.3 → 0.4.5

package/src/tool-surface.ts

@@ -0,0 +1,95 @@
+// Generated by scripts/sync-shared.mjs from shared/host/tool-surface.ts. Do not edit this copy; edit the shared source and run "node scripts/sync-shared.mjs".
+/**
+ * Family-shared tool-surface conventions for the packages that register
+ * model-facing tools.
+ *
+ * One home for the prompt-section placement and the visibility gate this
+ * family previously restated per package.
+ *
+ * Modelled on the official tool packages:
+ * - `@deepseek-ai/dsh-tool-subagent` renders its section through
+ *   `tools.get(name, context.scope) === undefined ? '' : text`, so guidance
+ *   disappears together with a restricted tool.
+ * - 21 of the 22 official tool packages register their tools GLOBALLY and gate
+ *   them with a setting, not per agent. Only the Agent Teams tool package —
+ *   whose tools belong to one membership — installs into each `agent.ctx`.
+ *   This family follows the majority: registration stays global so the
+ *   registry's per-scope `restrict()` mask (which filters inherited global
+ *   tools and REJECTS scope-local names) can still withhold these tools.
+ *
+ * Structural types only: this copy lands in packages that do not all depend on
+ * the same SDK service packages.
+ */
+
+/**
+ * Prompt-section order for each package's tool guidance.
+ *
+ * These sit in the family band between the deployment persona and the SDK's
+ * `PLAN_POLICY` (500). Values are owned here rather than written per package so
+ * the host plugins whose guidance shares one prompt cannot drift into an
+ * accidental tie.
+ */
+export const PLUGIN_TOOL_SECTION_ORDERS = {
+  ssh: 150,
+  'task-board': 200,
+} as const
+
+/** One plugin id keyed by {@link PLUGIN_TOOL_SECTION_ORDERS}. */
+export type PluginToolSectionId = keyof typeof PLUGIN_TOOL_SECTION_ORDERS
+
+/**
+ * Order of an external provider extension's own guidance section, right after
+ * the band of the plugin it extends.
+ *
+ * An extension names itself, not the plugin it plugs into, so its order stays
+ * out of {@link PLUGIN_TOOL_SECTION_ORDERS}: every package's copy of this module
+ * then carries no provider id. The slot still has one owner and cannot collide
+ * with a host plugin's band.
+ */
+export const EXTENSION_TOOL_SECTION_ORDER = 210
+
+/**
+ * The scoped tool lookup a section provider needs: the registry read for one
+ * assembly's scope. Matches `ctx.tools.get(name, scope)`.
+ */
+export interface ScopedToolLookup {
+  get(name: string, scope?: unknown): unknown
+}
+
+/** One assembly context carrying the scope the section is rendered for. */
+export interface SectionScopeContext {
+  scope?: unknown
+}
+
+/**
+ * Build a section provider that renders \`text\` only while at least one of
+ * \`toolNames\` is visible to the rendering scope.
+ *
+ * The native convention: a tool that a restriction, a preset, or a missing
+ * registry removed must not leave guidance behind telling the model to call it.
+ * An unreadable registry renders the text unchanged — guidance that outlives a
+ * momentary read failure is recoverable; guidance for a tool that is gone is
+ * not.
+ * @param tools - the scoped tool registry, when the deployment serves one.
+ * @param toolNames - registered names the guidance describes.
+ * @param text - the guidance rendered while they are reachable.
+ * @returns the section text provider.
+ */
+export function visibleToolText(
+  tools: ScopedToolLookup | undefined,
+  toolNames: readonly string[],
+  text: string,
+): (context: SectionScopeContext) => string {
+  if (tools === undefined) return () => text
+  return (context: SectionScopeContext) => {
+    for (const name of toolNames) {
+      try {
+        if (tools.get(name, context.scope) !== undefined) return text
+      } catch {
+        // A refused lookup is not proof the tool is gone; keep the guidance.
+        return text
+      }
+    }
+    return ''
+  }
+}

package/lib/types/host/run-guarded.d.ts

@@ -1,39 +0,0 @@
-/**
- * Async-boundary guard shared by the plugin family's Host halves: every
- * fire-and-forget promise chain and callback the host runtime does not own
- * (route handlers, timers, event listeners, spawned work) funnels through
- * these helpers. The dsh host installs a process-level fail-loud guard that
- * turns ANY unhandled promise rejection into a whole-process exit — one
- * plugin's stray rejection would otherwise take every plugin down. These
- * helpers exist so that failure mode is structurally impossible in family
- * code: the rejection becomes a logged error at the plugin boundary instead.
- *
- * Complements the aggregate's shell isolation (packages/dsh-web-all): the
- * shell contains import/activation failures at boot; runGuarded contains
- * run-time failures after activation.
- * @module dsh-web-shared/host/run-guarded
- */
-/**
- * Run one async operation, logging (never propagating) a rejection. Use for
- * promises whose lifecycle the caller does not await: spawned work, retry
- * loops, background flushes. Returns the original promise so callers can
- * still chain when they want to.
- * @param promise - the work to shield; any thenable.
- * @param label - log prefix naming the work site.
- * @param log - error sink; defaults to console.error.
- * @returns the input promise (rejection already consumed).
- */
-export declare function runGuarded<T>(promise: PromiseLike<T>, label: string, log?: (error: unknown) => void): PromiseLike<T>;
-/**
- * Wrap one callback so every invocation is individually guarded: a rejection
- * inside one call is logged and swallowed instead of escaping into whatever
- * infrastructure invoked the callback (HTTP server, EventEmitter, interval).
- * Sync throws are caught identically; a returned promise is replaced by
- * `undefined` after guarding (callers that need the original rejection should
- * await inside their own try/catch instead).
- * @param label - log prefix naming the callback site.
- * @param handler - the work to guard.
- * @param log - error sink; defaults to console.error.
- * @returns a wrapped callback with the same parameter list.
- */
-export declare function guardedHandler<A extends unknown[]>(label: string, handler: (...args: A) => unknown, log?: (error: unknown) => void): (...args: A) => unknown;

package/src/host/run-guarded.ts

@@ -1,76 +0,0 @@
-// Generated by scripts/sync-shared.mjs from shared/host/run-guarded.ts. Do not edit this copy; edit the shared source and run "node scripts/sync-shared.mjs".
-/**
- * Async-boundary guard shared by the plugin family's Host halves: every
- * fire-and-forget promise chain and callback the host runtime does not own
- * (route handlers, timers, event listeners, spawned work) funnels through
- * these helpers. The dsh host installs a process-level fail-loud guard that
- * turns ANY unhandled promise rejection into a whole-process exit — one
- * plugin's stray rejection would otherwise take every plugin down. These
- * helpers exist so that failure mode is structurally impossible in family
- * code: the rejection becomes a logged error at the plugin boundary instead.
- *
- * Complements the aggregate's shell isolation (packages/dsh-web-all): the
- * shell contains import/activation failures at boot; runGuarded contains
- * run-time failures after activation.
- * @module dsh-web-shared/host/run-guarded
- */
-
-/** Format one failure line for logging. */
-function formatFailure(label: string, error: unknown): Error {
-  return new Error(`[${label}] unhandled async failure: ${error instanceof Error ? error.stack ?? error.message : String(error)}`)
-}
-
-/**
- * Run one async operation, logging (never propagating) a rejection. Use for
- * promises whose lifecycle the caller does not await: spawned work, retry
- * loops, background flushes. Returns the original promise so callers can
- * still chain when they want to.
- * @param promise - the work to shield; any thenable.
- * @param label - log prefix naming the work site.
- * @param log - error sink; defaults to console.error.
- * @returns the input promise (rejection already consumed).
- */
-export function runGuarded<T>(promise: PromiseLike<T>, label: string, log: (error: unknown) => void = console.error): PromiseLike<T> {
-  void Promise.resolve(promise).catch(error => {
-    log(formatFailure(label, error))
-  })
-  return promise
-}
-
-/**
- * Wrap one callback so every invocation is individually guarded: a rejection
- * inside one call is logged and swallowed instead of escaping into whatever
- * infrastructure invoked the callback (HTTP server, EventEmitter, interval).
- * Sync throws are caught identically; a returned promise is replaced by
- * `undefined` after guarding (callers that need the original rejection should
- * await inside their own try/catch instead).
- * @param label - log prefix naming the callback site.
- * @param handler - the work to guard.
- * @param log - error sink; defaults to console.error.
- * @returns a wrapped callback with the same parameter list.
- */
-export function guardedHandler<A extends unknown[]>(
-  label: string,
-  handler: (...args: A) => unknown,
-  log: (error: unknown) => void = console.error,
-): (...args: A) => unknown {
-  return (...args: A) => {
-    try {
-      const result = handler(...args)
-      if (isPromiseLike(result)) {
-        void Promise.resolve(result).catch(error => {
-          log(formatFailure(label, error))
-        })
-        return undefined
-      }
-      return result
-    } catch (error) {
-      log(formatFailure(label, error))
-      return undefined
-    }
-  }
-}
-
-function isPromiseLike(value: unknown): value is PromiseLike<unknown> {
-  return typeof value === 'object' && value !== null && typeof (value as PromiseLike<unknown>).then === 'function'
-}