菜单
Durable Streams workspace conformance and standards-alignment guidance. Use when wiring or updating upstream conformance suites, adapter/launcher entrypoints, npm package pins, CI hooks, or standards-governance records for this repository.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | durable-streams-conformance-harness |
| description | Durable Streams workspace conformance and standards-alignment guidance. Use when wiring or updating upstream conformance suites, adapter/launcher entrypoints, npm package pins, CI hooks, or standards-governance records for this repository. |
| sources | ["docs/standards.md","package.json","tests/conformance/README.md","scripts/conformance/run-client-suite.sh","scripts/conformance/run-server-suite.sh"] |
| user-invocable | false |
Repo-local guidance for how this workspace aligns with the upstream Durable Streams ecosystem.
This is not protocol truth. It is the local shape for exercising that protocol against the upstream conformance suites.
This workspace treats the upstream protocol and conformance suites as external standards that are tracked explicitly in-repo.
Current governance records live in:
docs/standards.mdCargo.tomlpackage.jsonWhen standards alignment changes, those records should move together.
Current tracked baselines for this repo:
1.0-draftf091f315e4c3ca6769b45135ab8b5f53d70b1751@durable-streams/client-conformance-tests@0.2.3@durable-streams/server-conformance-tests@0.2.3The current server crate in this workspace is a lift-and-shift of published
durable-streams-server 0.1.3.
These values should match:
docs/standards.mdCargo.toml workspace metadatapackage.jsonIf they do not match, treat the standards picture as stale and reconcile it before relying on the harness documentation.
The current workspace pins:
@durable-streams/client-conformance-tests@durable-streams/server-conformance-testsExact versions belong in package.json, not in ad hoc shell commands.
The local harness is split between runners and entrypoints.
These invoke the upstream npm packages:
scripts/conformance/bootstrap.shscripts/conformance/run-client-suite.shscripts/conformance/run-server-suite.shThe upstream client suite expects an adapter executable.
Local path:
tests/conformance/client/run-adapter.shThe workspace-level runner:
durable-streams-client-conformance -- --run <adapter>The upstream server suite runs against a base URL, not a stdin/stdout adapter.
Local paths:
tests/conformance/server/start-server.shscripts/conformance/run-server-suite.shThe workspace-level runner:
start-server.shDURABLE_STREAMS_SERVER_URL as the target base URLrunConformanceTests({ baseUrl }) from the pinned npm packagenpm exec vitest run ...Supported local environment knobs:
DURABLE_STREAMS_SERVER_URLDURABLE_STREAMS_SERVER_LAUNCHERDURABLE_STREAMS_SERVER_SKIP_LAUNCHDURABLE_STREAMS_SERVER_STARTUP_DELAYUse workspace-level conformance plumbing when work spans crates or external process boundaries.
Keep crate-local tests inside the relevant crate when they do not depend on the external suites.
Conformance harness updates should stay thin:
tests/conformanceWhen upstream standards alignment changes:
docs/standards.mdCargo.tomlpackage.jsonThis skill should define:
This skill should not define:
durable-streams-protocolThose should live in the protocol skill or future crate-specific skills.
Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT, code review, naming convention, variable naming, function naming, type naming, 命名规范, 代码风格, 格式化, 最佳实践, 代码审查, 怎么命名
Source-level conventions for the Durable Streams Rust server. Use when changing code under crates/durable-streams-server/src, especially around protocol types, storage contracts, handlers, streaming paths, concurrency, or error handling.
Testing and conformance guidance for the Durable Streams Rust server. Use when adding or changing tests under crates/durable-streams-server/tests, deciding between unit and integration coverage, or wiring the upstream server conformance suite from this workspace.
Durable Streams protocol semantics. Use when implementing client or server behaviour at the HTTP protocol level: stream lifecycle, create/append/close/ delete/head/read semantics, offsets and reserved sentinels, JSON mode, live read modes (`live=long-poll`, `live=sse`), `Stream-Seq`, idempotent producer headers, caching/collapsing headers, TTL/expiry, and `Stream-Closed` EOF signalling.