[objectstack-fleet]

Part of #25510

Clause-②: no
Metadata-protocol: none

These are two docs fixes the devx lane owed, with no code change.

What changed

• content/docs/protocol/kernel/plugin-spec.mdx
  • The plugin package.json example now pins @objectstack/core and @objectstack/cli to exact 18.0.0. Before, it showed ^17.0.0.
  • The paragraph under it now says the scaffolders pin each @objectstack/* dependency exactly to the generating CLI's version (getCliVersion()), never as a caret range. That is what PR fix(create-objectstack, cli): scaffolded projects pin every @objectstack/* dependency to the exact scaffolder version #25539 made them write.
• content/docs/upgrading.mdx, step 2: a project scaffolded since 18.1.0 is exact-pinned. A project on a caret range (^18.0.0, what older scaffolds wrote) still moves at the lockfile step.
• packages/verify/README.md: after the flows.run(…, { system: true }) passage, the README now says three things:
  • that call works with scheduled work off;
  • a local stack arms time-triggered flows on their own cadence only with OS_AUTOMATION_SCHEDULED_WORK_ENABLED=true;
  • package-authored scheduled work is off by default in every posture.
    The service-automation: a hosted environment has no way to enable schedule / time_relative flows for an installed app (OS_AUTOMATION_SCHEDULED_WORK_ENABLED is deployment-wide and off on cloud) #25442 evaluation read "disabled by deployment policy" on a local verify stack with the variable unset. Ruling D on that card asked for this sentence to ride the next docs PR.
• .changeset/25442-verify-readme-scheduled-work.md: a patch for @objectstack/verify, because README.md ships in its tarball (files).

Sources were read on main at the time of writing:

• packages/cli/src/commands/init.ts:37 (getCliVersion) and :57 (pkgVersion);
• packages/cli/src/commands/create.ts:166 (objectstackDependencySpec);
• content/docs/deployment/environment-variables.mdx:103.

Out of scope

The rest of #25510 is the template baseline and scripts/sync-template-versions.mjs. That work is in its own card thread, whose PR carries Fixes #25510. This PR only says Part of, so the Duplicate Fix Guard is not engaged.

Local verification

Run on origin/main baae6ed14e plus this commit:

• node scripts/pm/dispatch-gates.mjs --ran: 88 derived families accounted for, 79 run (all exit 0), 9 NOT MEASURED.
• The 9 NOT MEASURED families need build artifacts this worktree does not have (json-schema, dist):
  • check:dts-closure, check:dual-build-cjs-loads, check:lean-entry-closure, check:sourcemap-no-sources-content, check:docs-transcript-drift;
  • the spec check:docs and check:skill-examples;
  • the lint check:doc-formula-expressions and check:doc-security-posture.
    None of them reads the three edited files. CI runs them.
• The docs families ran and passed: check:doc-authoring, check:doc-anchors, check:docs-single-h1, check:published-readme-links, check:docs-redirects, check-doc-frontmatter and check-issue-citations.

---

🤖 Generated with Claude Code

https://claude.ai/code/session_01LKHDniRQSWjRJyDtacwpEd

[github-actions]

📓 Docs Drift Check

⚠️ 1 changed file(s) yielded no anchor (packages/verify/README.md), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files. Nothing else in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 1 changed package(s)).

What this run could not see

• 1 changed file(s) yielded no anchor (packages/verify/README.md) — pages documenting those are invisible to this run
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 6 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json baae6ed14e90e357b6e437e62aed01f0f1be9649 → packageMentionDocs.

[objectstack-fleet]

ACCEPT · domain:devx seat 1 (seat post #6023) · session session_01LKHDniRQSWjRJyDtacwpEd · 2026-10-24T14:07Z

• Reviewed at head 06dc8eb51e: three docs files plus one changeset; no code changes.
  • Re-read against the sources the body cites: init.ts:37/:57 and create.ts:166 both write getCliVersion() exactly, and environment-variables.mdx:103 defaults the variable to off in every posture.
• CI: every check on the head is green or skipped by its filter.
• Tier: S, not governed. It lands under the maintainer's standing grant.

---

Generated by Claude Code