Skip to content

docs: dsh 0.1.2 alpha: session-event format and settings API break, new Remote API cookbook - #18

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
docs/sync
Open

docs: dsh 0.1.2 alpha: session-event format and settings API break, new Remote API cookbook#18
github-actions[bot] wants to merge 1 commit into
mainfrom
docs/sync

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

The dsh docs were refreshed to match a development snapshot that has moved
well past the last tagged release: the npm page now tracks a new
0.1.2-alpha.2.5 train (shipped daily 2026-08-30 → 09-02, latest still
0.1.1-rc.2), and 46 mirrored pages were rewritten upstream with interface
changes, not just wording. dsh is an unstable developer preview with no
migration path, so plugin authors on the master/alpha line should expect to
recompile and re-typecheck against these changes.

  • Session event log format hardened. Sequence positions are now branded
    types (SessionSeq, SessionLogOffset, SessionSeqCursor,
    OptionalSessionSeq) threaded through SessionEvent, SurfaceOp, and every
    compaction/* / command/* / session-surface type; event payloads gain an
    ignorable?: true skip marker (an unrecognized required event must now
    refuse reconstruction rather than be dropped); sessions track an
    inheritedEventCount fork-lineage cut; and Session.events is replaced by
    snapshotEvents() / eventAt() / ownEvents() / isOwnSeq(). Downstream
    plugins that merge custom event types or read the log will hit all of this.
  • Settings plugin API changed shape. The standalone
    installSettingsSection(ctx, …) helper and settingsNamespace() brand are
    gone; consumers now ctx.inject(['settings']) and call
    ctx.settings.installSection(owner, ns, schema, entry, hooks) (see the
    rewritten adding-a-settings-card cookbook). Namespace strings are validated
    as lowercase-hyphenated identifiers and remote failures now throw
    RemoteError with slash codes (settings/conflict, settings/rejected)
    instead of TypertRemoteFailure and kebab codes.
  • New cookbook: adding a Remote API (new page) — the five-step recipe for
    adding a ctx.remote.<namespace>.<method>() endpoint: @Remote declaration,
    one RemoteError code table merged into RemoteErrorDetailsMap, manifest
    generation, the typed client call, and Host/Client testing. Worth reading
    before any remote-call work.
  • Remote/gateway config shifts. The Typert gateway error taxonomy moved to
    RemoteError with gateway/* codes carried through unchanged; the
    session-controller adds a coldBlankProbeMaxEvents projection gate; the
    API-gateway WebSocket heartbeat default drops 30000 → 2000 ms.
  • Package map churned (module-graph.md, config-catalog): agent-spine-demo
    and tool-subagent-report are gone, code-runtime-python moved under
    experimental, and several plugins (agent-instructions, agent-loop,
    agent-presets) newly require sessionProjections — session projection
    callbacks and cached/cold snapshots now take an inheritedEventCount
    argument.
  • Also in this run (minor, not dsh): .metadata.json flags two older news
    pages (news1226 DeepSeek-V3, news251201 V3.2) as served-fallback-shell —
    the reverse of the previous clean fetch — so a future full refetch may gut
    them; file content is unchanged in this tree.

@github-actions github-actions Bot changed the title docs: Offline tokenizer zip bumped to v4 in token_usage docs docs: token_usage tokenizer zip bumped from deepseek-v3 to deepseek-v4 Aug 28, 2026
@github-actions github-actions Bot changed the title docs: token_usage tokenizer zip bumped from deepseek-v3 to deepseek-v4 docs: dsh 0.1.2-alpha.2: RemoteError code namespaces, ignorable session events, new Remote API surfaces Aug 30, 2026
@github-actions github-actions Bot changed the title docs: dsh 0.1.2-alpha.2: RemoteError code namespaces, ignorable session events, new Remote API surfaces docs: dsh Remote API reworked: RemoteError code namespace, sessionProjections requirement, 0.1.2-alpha.2 Aug 30, 2026
@github-actions github-actions Bot changed the title docs: dsh Remote API reworked: RemoteError code namespace, sessionProjections requirement, 0.1.2-alpha.2 docs: dsh refresh: RemoteError failure vocabulary, mandatory sessionProjections seam, 0.1.2-alpha.2 Aug 31, 2026
@github-actions github-actions Bot changed the title docs: dsh refresh: RemoteError failure vocabulary, mandatory sessionProjections seam, 0.1.2-alpha.2 docs: dsh 0.1.2-alpha.2: RemoteError taxonomy rename, sessionProjections now a required inject across ~20 plugins, new API surface Aug 31, 2026
@github-actions github-actions Bot changed the title docs: dsh 0.1.2-alpha.2: RemoteError taxonomy rename, sessionProjections now a required inject across ~20 plugins, new API surface docs: dsh 0.1.2-alpha.3: Remote error codes renamespaced, SQLite persistence dropped, new Remote API cookbook Aug 31, 2026
@github-actions github-actions Bot changed the title docs: dsh 0.1.2-alpha.3: Remote error codes renamespaced, SQLite persistence dropped, new Remote API cookbook docs: dsh 0.1.2-alpha: RemoteError code overhaul, ignorable session events, SQLite backend dropped Sep 1, 2026
@github-actions github-actions Bot changed the title docs: dsh 0.1.2-alpha: RemoteError code overhaul, ignorable session events, SQLite backend dropped docs: dsh 0.1.2-alpha: RemoteError wire codes, sessionProjections service requirement, new alpha npm release Sep 1, 2026
@github-actions github-actions Bot changed the title docs: dsh 0.1.2-alpha: RemoteError wire codes, sessionProjections service requirement, new alpha npm release docs: dsh 0.1.2-alpha: Remote API cookbook, namespaced gateway error codes, subagent/session API overhaul Sep 1, 2026
@github-actions github-actions Bot changed the title docs: dsh 0.1.2-alpha: Remote API cookbook, namespaced gateway error codes, subagent/session API overhaul docs: dsh 0.1.2-alpha.4 lands RemoteError taxonomy, session-log format changes, and a sessionProjections core service Sep 1, 2026
@github-actions github-actions Bot changed the title docs: dsh 0.1.2-alpha.4 lands RemoteError taxonomy, session-log format changes, and a sessionProjections core service docs: dsh 0.1.2-alpha line lands: report tool removed, send_message takes agent_id, plugins now require sessionProjections Sep 2, 2026
@github-actions github-actions Bot changed the title docs: dsh 0.1.2-alpha line lands: report tool removed, send_message takes agent_id, plugins now require sessionProjections docs: dsh 0.1.2-alpha line: handle-based session persistence, subagent messaging rewrite, bundle/package renames Sep 2, 2026
…ew Remote API cookbook

The dsh docs were refreshed to match a development snapshot that has moved
well past the last tagged release: the npm page now tracks a new
`0.1.2-alpha.2`→`.5` train (shipped daily 2026-08-30 → 09-02, `latest` still
`0.1.1-rc.2`), and 46 mirrored pages were rewritten upstream with interface
changes, not just wording. dsh is an unstable developer preview with no
migration path, so plugin authors on the master/alpha line should expect to
recompile and re-typecheck against these changes.

- **Session event log format hardened.** Sequence positions are now branded
  types (`SessionSeq`, `SessionLogOffset`, `SessionSeqCursor`,
  `OptionalSessionSeq`) threaded through `SessionEvent`, `SurfaceOp`, and every
  `compaction/*` / `command/*` / session-surface type; event payloads gain an
  `ignorable?: true` skip marker (an unrecognized *required* event must now
  refuse reconstruction rather than be dropped); sessions track an
  `inheritedEventCount` fork-lineage cut; and `Session.events` is replaced by
  `snapshotEvents()` / `eventAt()` / `ownEvents()` / `isOwnSeq()`. Downstream
  plugins that merge custom event types or read the log will hit all of this.
- **Settings plugin API changed shape.** The standalone
  `installSettingsSection(ctx, …)` helper and `settingsNamespace()` brand are
  gone; consumers now `ctx.inject(['settings'])` and call
  `ctx.settings.installSection(owner, ns, schema, entry, hooks)` (see the
  rewritten adding-a-settings-card cookbook). Namespace strings are validated
  as lowercase-hyphenated identifiers and remote failures now throw
  `RemoteError` with slash codes (`settings/conflict`, `settings/rejected`)
  instead of `TypertRemoteFailure` and kebab codes.
- **New cookbook: adding a Remote API** (new page) — the five-step recipe for
  adding a `ctx.remote.<namespace>.<method>()` endpoint: `@Remote` declaration,
  one `RemoteError` code table merged into `RemoteErrorDetailsMap`, manifest
  generation, the typed client call, and Host/Client testing. Worth reading
  before any remote-call work.
- **Remote/gateway config shifts.** The Typert gateway error taxonomy moved to
  `RemoteError` with `gateway/*` codes carried through unchanged; the
  session-controller adds a `coldBlankProbeMaxEvents` projection gate; the
  API-gateway WebSocket heartbeat default drops 30000 → 2000 ms.
- **Package map churned** (`module-graph.md`, config-catalog): `agent-spine-demo`
  and `tool-subagent-report` are gone, `code-runtime-python` moved under
  experimental, and several plugins (`agent-instructions`, `agent-loop`,
  `agent-presets`) newly require `sessionProjections` — session projection
  callbacks and cached/cold snapshots now take an `inheritedEventCount`
  argument.
- Also in this run (minor, not dsh): `.metadata.json` flags two older news
  pages (`news1226` DeepSeek-V3, `news251201` V3.2) as served-fallback-shell —
  the reverse of the previous clean fetch — so a future full refetch may gut
  them; file content is unchanged in this tree.
@github-actions github-actions Bot changed the title docs: dsh 0.1.2-alpha line: handle-based session persistence, subagent messaging rewrite, bundle/package renames docs: dsh 0.1.2 alpha: session-event format and settings API break, new Remote API cookbook Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants