Files
deepseek-harness/packages/session
imccyu ec601ca13d build(vendor): rescope the vendored Cordis packages into @deepseek-ai
Machine-produced by `pnpm run rescope-vendor --apply` plus the regeneration it
prints: `pnpm install` for the lockfile, `pnpm run gen-third-party-notices`,
`verify-translation-pairing --write` for the touched bilingual pairs,
`gen-doc-graphs`, and one typert snapshot whose ids embed character offsets.
`pnpm run rescope-vendor --check` verifies the result.

Renames nine vendored packages (cordis, cosmokit, schemastery and the six
@cordisjs plugins) and every reference that resolves them: manifest names and
dependency keys, module specifiers including declare-module merges, cordis.yml
plugin names, tsconfig paths, every Markdown fence, and `docs/` prose.
Directory names, upstream versions, and dependency ranges are unchanged, so
vendor/README.md still reads as an upstream snapshot; its manifest table gains
an upstream-name column so THIRD_PARTY_NOTICES keeps MIT attribution pointed
at each fork's origin.

The tutorial tier follows the rename end to end: its yaml fences named plugins
the Loader can no longer resolve, its `ts ignore-check` fences disagreed with
the compiled fences beside them, and its prose quoted both. The contracts that
told readers to keep upstream names — the root convention and the vendoring
cookbook's tree comment and manifest invariant — now say to rescope instead.

Two rules read `@deepseek-ai/` as "another workspace plugin": the client bundle
purity gate now names the vendored libraries a browser bundle inlines, and the
files where a bare `cordis` is an agent-preset id keep that product data.
2026-08-10 22:04:13 +08:00
..

session/ — durable session data plane

English | 中文

The durable family around core/session's live in-memory service: the persistence seam with its storage backends and checkpoint policy, the projection seam that serves whole log-derived values, log-backed titles, and outbound session telemetry. All product packages. session-query/ remains a sibling group: the read/tool surface is consumed independently of persistence internals.

Persistence

Durable session persistence, semantic checkpoint policy, and the shipped storage backends.

Package Role ctx key
session-persistence/ Defines the persistence service and shared write coordination ctx.sessionPersistence
session-checkpoint-policy/ Applies semantic durability checkpoints wraps ctx.llm and ctx.tools
session-persistence-jsonl/ Persists sessions in JSONL files registers on ctx.sessionPersistence
session-persistence-sqlite/ Persists sessions in SQLite registers on ctx.sessionPersistence

The session-persistence decision records the persistence design.

Projection

Serves current, log-derived per-session state to client carriers.

Package Role ctx key
session-projection/ Defines and drives session projection units ctx.sessionProjections
session-projection-cache/ Persists and restores projection checkpoints ctx.sessionProjectionCache

Titles

Derives durable session titles from the session log, with an optional model-backed provider.

Package Role ctx key
session-title/ Owns title state, fallback behavior, provider registration, and refresh ctx.sessionTitle
session-title-llm/ Provides shared model-backed title generation
session-title-first-message-llm/ Titles a session from its first eligible human message registers on ctx.sessionTitle
session-title-all-messages-llm/ Titles a session from all eligible human messages registers on ctx.sessionTitle

Deployments may register one model-backed provider; the service retains a deterministic fallback when none is present.

Telemetry

Projects session activity into outbound telemetry and delegates delivery to a configured reporting backend. The telemetry decision records the reporting boundary; the mode decision records immediate, feedback-gated, and disabled delivery.

Package Role
session-telemetry/ Defines capture, redaction, projection, and live or on-demand backend delivery.
session-telemetry-otel/ Delivers telemetry through OpenTelemetry logs in FULL, FEEDBACK_ONLY, or DISABLED mode.

The subsystem references: persistence.md, session-projection.md, session-title.md, and telemetry.md. Only one title provider may register at a time; the demo spine mounts the fallback service and leaves both model providers out of default composition.