Show Your Sources
← All memos
Source-backed research memo

Dev Stack Currency — 2026-10-12

devstatus: activedate: 2026-10-12format: frontmatter12 single-source1 contradiction

Stats

13
Claims
6
Sources
6
Unique sources
12
Single-source
1
Contradictions
7
Open questions

Claims (13)

claim.stack.openclaw-releaseconf: high 0.95single sourcestatus: supported

OpenClaw latest stable release = 2026.10.1 (published 2026-10-10); pre-release = 2026.10.5-beta.1 (2026-10-11).

! Single source — not cross-checked. Only 0 distinct sources; the two-source rule is not met.
Sources
No URL sources recorded for this claim.
Local evidence
sources/deposit-dev-stack-loop-2026-10-12.md
openclaw gateway status
claim.stack.openclaw-sdk-retirementsconf: high 0.95single sourcestatus: supported

OpenClaw 2026.10.1 retires plugin/SDK author surfaces: whole-store + transcript-file SDK bridges removed; imports channel-lifecycle, channel-message, channel-reply-pipeline, config-runtime, infra-runtime retired; facades command-auth, discord, telegram-account retired; pre-9.8 authFingerprint bindings dead (no auto-migration). VERIFIED against the archived full release markdown (CHANGELOG/2026.10.1.md:2413-2415) and the version-pinned 2026.10.1 export map.

! Single source — not cross-checked. Only 0 distinct sources; the two-source rule is not met.
Sources
No URL sources recorded for this claim.
Local evidence
sources/deposit-dev-stack-loop-2026-10-12.md
/home/ubuntu/.local/share/pnpm/global/5/.pnpm/openclaw@2026.7.1-2/node_modules/openclaw/docs/plugins/sdk-subpaths.md
claim.stack.sdk-removal-boundaryconf: high 0.95single sourcestatus: supported

Plugin-SDK removal boundary (durable, proven): openclaw/plugin-sdk/channel-reply-pipeline is exported through 2026.9.9 (last-with) and ABSENT from 2026.10.1-beta.1 onward (first-without; incl. 2026.10.1 and 2026.10.5-beta.1). Replacements channel-outbound / channel-inbound are exported at 2026.10.1. The authoritative artifact is the registry export map (tarball package.json), not the prose docs.

! Single source — not cross-checked. Only 0 distinct sources; the two-source rule is not met.
Sources
No URL sources recorded for this claim.
Local evidence
sources/deposit-dev-stack-loop-2026-10-12.md
claim.stack.deepseek-aliasesconf: high 0.85single sourcetier: primarystatus: supported

DeepSeek alias drift: deepseek-flash now serves V4.1-Flash (released 2026-09-10); deepseek-v4-pro serves V4-Pro-0813. Prior V4-Flash / V4-Flash-Vision-Exp retired; legacy IDs still accepted but routed to V4.1-Flash and billed at Flash price.

! Single source — not cross-checked. Only 1 distinct source; the two-source rule is not met.
Sources (1)
tier: primary
https://api-docs.deepseek.com/updates
retrieved 2026-10-12
Local evidence
sources/deposit-dev-stack-loop-2026-10-12.md
claim.stack.deepseek-pricingconf: high 0.85single sourcetier: primarystatus: supported

DeepSeek pricing is peak/off-peak now (eff. 2026-08-16). deepseek-flash: cache-miss input $0.15 off-peak / $0.30 peak; output $0.60 off-peak / $1.20 peak, per 1M tokens. deepseek-v4-pro: input $0.66 / $1.32; output $1.98 / $3.96. Peak = 01:00-04:00 and 06:00-10:00 UTC Mon-Fri.

! Single source — not cross-checked. Only 1 distinct source; the two-source rule is not met.
Sources (1)
tier: primary
https://api-docs.deepseek.com/quick_start/pricing
retrieved 2026-10-12
Local evidence
sources/deposit-dev-stack-loop-2026-10-12.md
claim.stack.github-apiconf: med 0.7single sourcetier: primarystatus: supported

GitHub REST API version 2026-03-10 is the first calendar version with breaking changes (rate removed from GET /rate_limit; permission param removed on team create; submodules typed as 'submodule'; SARIF Content-Type corrected; use_squash_pr_title_as_default removed). GitHub GraphQL 2026-10-01 removals (User.viewerRelevantRepositories, CopilotAgentTask.type) are now live.

! Single source — not cross-checked. Only 1 distinct source; the two-source rule is not met.
Sources (1)
tier: primary
https://docs.github.com/en/rest/about-the-rest-api/breaking-changes
retrieved 2026-10-12
Local evidence
sources/deposit-dev-stack-loop-2026-10-12.md
claim.stack.llamacppconf: med 0.6single sourcetier: primarystatus: supported

llama.cpp (local embeddings dep) moved to semantic versioning: latest v0.6.0 (2026-10-05). v0.4.1 (2026-09-14) was breaking - CLI flags --mmap/--mlock/--direct-io replaced by a single --load-mode.

! Single source — not cross-checked. Only 1 distinct source; the two-source rule is not met.
Sources (1)
tier: primary
https://github.com/ggml-org/llama.cpp/releases
retrieved 2026-10-12
Local evidence
sources/deposit-dev-stack-loop-2026-10-12.md
claim.stack.plugin-sdk-forwardbreakconf: high 0.85single sourcestatus: supported

Forward-break: our enabled plugin lightclawbot imports openclaw/plugin-sdk/channel-reply-pipeline (v1.2.16 static at dist/src/inbound.js:13). On OpenClaw 2026.7.1-2 the subpath still resolves so nothing is broken today, but OpenClaw's installed docs mark it a deprecated compatibility facade scheduled for removal at the next major release -> the import is expected to break on a gateway upgrade.

! Single source — not cross-checked. Only 0 distinct sources; the two-source rule is not met.
Sources
No URL sources recorded for this claim.
Local evidence
/home/ubuntu/.openclaw/npm/projects/lightclawbot/node_modules/lightclawbot/dist/src/inbound.js
sources/deposit-dev-stack-loop-2026-10-12.md
claim.stack.lightclawbot-130conf: high 0.9single sourcestatus: supported

lightclawbot npm latest = 1.3.0 (published 2026-09-22; we run 1.2.16). 1.3.0 STILL imports channel-reply-pipeline (dynamic await import at dist/src/inbound.js:262, unguarded); the only change from 1.2.16 is static->dynamic import. Therefore no released lightclawbot version fixes the forward-break.

! Single source — not cross-checked. Only 0 distinct sources; the two-source rule is not met.
Sources
No URL sources recorded for this claim.
Local evidence
sources/deposit-dev-stack-loop-2026-10-12.md
claim.stack.lightclawbot-vendor-patchconf: high 0.85single sourcestatus: supported

Remediation available (local, not a release): lightclawbot@1.2.16 can run on openclaw >=2026.10.1 via an in-place vendor patch to node_modules/.../dist/src/inbound.js — the single retired static import (line 13) is replaced by a guarded lazy resolver that prefers channel-outbound/createChannelMessageReplyPipeline, falls back to channel-reply-pipeline/createChannelReplyPipeline, and throws a clear error if neither resolves. Patched sha256=10958e2a…f2b1; pristine 1.2.16 sha256=2b1f3c62…c0e17. Verified by RUNNING on scratch openclaw@2026.10.1 (Node 24.16.0) and live 2026.7.1-2. NOT a published fix — npm latest 1.3.0 still ships the unguarded retired import.

! Single source — not cross-checked. Only 0 distinct sources; the two-source rule is not met.
Sources
No URL sources recorded for this claim.
Local evidence
/home/ubuntu/.openclaw/npm/projects/lightclawbot/node_modules/lightclawbot/dist/src/inbound.js
sources/deposit-lightclawbot-patch-2026-10-12.md
claim.stack.node-runtime-gateconf: high 0.9single sourcestatus: supported

Node runtime prerequisite for the 2026.10.x gateway: openclaw@2026.10.1 declares engines.node = '>=24.16.0 <25 || >=26.1.0'. Our host is Node v22.23.2, which fails the gate — so a Node upgrade is a prerequisite for adopting any 2026.10.x gateway, independent of the plugin patch.

! Single source — not cross-checked. Only 0 distinct sources; the two-source rule is not met.
Sources
No URL sources recorded for this claim.
Local evidence
/home/ubuntu/.openclaw/workspace-dev-researcher/research/2026-10-12-openclaw-upgrade-boundary/raw/openclaw-packument.json
claim.stack.deepseek-alias-pinconf: high 0.95single sourcestatus: supported

Our DeepSeek deployment is alias-only and unpinned: config model ids are deepseek/deepseek-flash (15 agents) and deepseek/deepseek-v4-pro (1 agent), with no env/version pin, so the served model version drifts silently. Hardening nit: the DeepSeek API key is a literal string in openclaw.json's models.providers.deepseek.apiKey, not env-referenced.

! Single source — not cross-checked. Only 0 distinct sources; the two-source rule is not met.
Sources
No URL sources recorded for this claim.
Local evidence
/home/ubuntu/.openclaw/openclaw.json

Contradictions & conflicts

Conflicting evidenceDoc conflict — resolved 2026-10-12 (in favour of sdk-subpaths.md:101). The installed docs disagree on channel-reply-pipeline: sdk-subpaths.md:101 marks it deprecated ("use plugin-sdk/channel-outbound"), whereas sdk-migration.md:393 lists it as a normal subpath and the migration example at sdk-migration.md:274 recommends importing it as the "modern focused import" (alongside command-auth, which the retirement set does flag). The tie-breaker is the registry export map (ground truth): the subpat…

Open questions

  1. "Does our live gateway pin OpenClaw below 2026.10.1, and do our plugins use any retired SDK imports/facades? (Local answer: gateway = 2026.7.1-2; lightclawbot uses plugin-sdk/channel-reply-pipeline — deprecated, forward-break on upgrade.)"
  2. "Is our DeepSeek deployment explicitly pinned to a version, or does it track the deepseek-flash alias (now V4.1-Flash)? (Local answer: unpinned / alias-only.)"
  3. Should the DeepSeek API key (and lightclawbot account key) be moved out of openclaw.json literals into env/secret references? (security/privacy decision for repz.)
  4. "Removal boundary RESOLVED 2026-10-12: channel-reply-pipeline exported through 2026.9.9, absent from 2026.10.1-beta.1 on (version-pinned packument). The only remaining check for an actual upgrade: confirm the target build's live exports map before moving."
  5. Will a future lightclawbot release migrate to channel-outbound/channel-inbound? Unknown — the package ships no changelog and has no public repo.
  6. "Doc conflict RESOLVED 2026-10-12: sdk-subpaths.md:101 (deprecated) is correct; sdk-migration.md:393/:274 are upstream doc errors. Tie-breaker = the registry export map (ground truth): channel-reply-pipeline is genuinely gone at 2026.10.1. Preserved as a doc-quality note, not a substantive open question: the migration doc is self-contradictory and its example recommends a removed path — worth reporting upstream."
  7. "For Open Gaps Register GAP 2: does our own unpinned DeepSeek deployment serve as the worked example that justifies designating a version-pin source-of-record?"

Provenance

Parser
parse-memo.mjs
Schema
0.1
Format
frontmatter
Parsed at
2026-10-14T14:34:49.426Z
Input
/home/ubuntu/.openclaw/workspace/projects/show-your-sources/fixtures/dev-stack-currency-2026-10-12.md
Raw evidence
[[sources/deposit-dev-stack-loop-2026-10-12|Deposit — dev external loop (2026-10-12)]]. All external claims carry a retrieved date; re-verify on the next loop.
Rendered by render.mjs · schema v0.1 · built 2026-10-14T14:34:49.413Z