@luziyang2026/dsh-question-nav 0.4.2 → 0.5.0

package/src/core/align.ts

@@ -0,0 +1,23 @@
+/**
+ * Rail anchor-edge constants shared by the host schema and the browser
+ * settings scope. Pure data: no DSH imports, so the client bundle may inline
+ * this module (a Host import here would leak into the browser half).
+ *
+ * @module dsh-question-nav/align
+ */
+
+/** Supported rail anchor edges. */
+export const ALIGN_OPTIONS = ['left', 'right'] as const
+
+/** Rail anchor edge preference. */
+export type AlignPreference = typeof ALIGN_OPTIONS[number]
+
+/** Default anchor edge when the user-settings document has no override. */
+export const DEFAULT_ALIGN: AlignPreference = 'left'
+
+/** Settings namespace owned by this plugin (spelled here rather than
+ * imported: the client bundle must not depend on a Host package). */
+export const QUESTION_NAV_SETTINGS_NS = 'question-nav'
+
+/** Field carrying the selected anchor edge. */
+export const ALIGN_FIELD = 'align'

package/src/index.ts

@@ -9,19 +9,24 @@
  */
 import type { Context } from '@deepseek-ai/cordis'
 import { questionIndexProjectionDefinition } from './projection.ts'
+import { questionNavSettingsNamespace, QuestionNavSettingsSchema } from './settings.ts'
 
 /** Cordis plugin name. */
 export const name = 'dsh-question-nav'
 
 /**
- * Register the `questionIndex` unit. The registry is an optional capability
- * (absent in headless compositions), so registration rides `ctx.inject`:
- * without it the host half simply contributes nothing and the browser strip
- * falls back to live-window questions.
+ * Register the `questionIndex` unit and the plugin's durable settings
+ * namespace. Both registries are optional capabilities (absent in headless
+ * compositions), so each registration rides `ctx.inject`: without them the
+ * host half simply contributes nothing and the browser strip falls back to
+ * live-window questions and the default rail alignment.
  * @param ctx - plugin context.
  */
 export function apply(ctx: Context): void {
   ctx.inject(['sessionProjections'], (inner) => {
     inner.sessionProjections.register(questionIndexProjectionDefinition)
   })
+  ctx.inject(['settings'], (settingsCtx) => {
+    settingsCtx.settings.register(questionNavSettingsNamespace, QuestionNavSettingsSchema)
+  })
 }

package/src/settings.ts

@@ -0,0 +1,33 @@
+/**
+ * Host-side durable settings for the question-nav plugin, registered into the
+ * DSH user-settings document. Currently one field: which edge of the
+ * conversation column the rail anchors to (`align`). The browser half reads
+ * the same namespace through the settings scope (`ctx.settingsScope.bind`)
+ * and routes the user's choice back through `scope.set`.
+ *
+ * @module dsh-question-nav/settings
+ */
+
+import z from '@deepseek-ai/schemastery'
+import type { SettingsNamespace } from '@deepseek-ai/dsh-settings'
+import {
+  ALIGN_FIELD, ALIGN_OPTIONS, DEFAULT_ALIGN, QUESTION_NAV_SETTINGS_NS,
+  type AlignPreference,
+} from './core/align.ts'
+
+/** Durable settings section shared by the Host schema and the browser scope. */
+export interface QuestionNavSettings {
+  /** Anchor edge of the rail. */
+  align: AlignPreference
+}
+
+/** Durable settings schema; also the wire envelope the browser scope validates against. */
+export const QuestionNavSettingsSchema: z<QuestionNavSettings> = z.object({
+  [ALIGN_FIELD]: z.union([...ALIGN_OPTIONS]).default(DEFAULT_ALIGN),
+})
+
+/** The settings namespace this plugin owns, branded for the Host registry.
+ * `question-nav` matches the registry pattern (`^[a-z][a-z0-9-]*$`), so the
+ * constant needs no runtime validator — keeping this module type-only on the
+ * settings package avoids inlining it (and cosmokit) into the host bundle. */
+export const questionNavSettingsNamespace = QUESTION_NAV_SETTINGS_NS as SettingsNamespace