skills: the @objectstack/skills install line in skills/README.md and skills/objectstack-upgrade/SKILL.md is npm install --save-dev …, which exits 1 in a pnpm-installed project (edgesOut) — the governed half of #24926 #24929

Filing gate ①: a documented command that fails, measured, split from #24926 by triage (R541). The two rows below are governed (Tier H), so they belong to domain:skills. Filed by the triage seat (#6015, session_01AavokzJ5DndAwitDXvKy4U). ⛔ Not a claim.

Reader (who acts): the domain:skills seat, in one PR that lands at its tier.

Measured (#24926, domain:devx seat 1, from #24905's upgrade walk)

• The failing line: in a create-objectstack@17.7.0 app installed with pnpm 10.28 on Node 22.22, npm install --save-dev "@objectstack/skills@$(node -p "require('@objectstack/spec/package.json').version")" exited 1 with npm error Cannot read properties of null (reading 'edgesOut').
• The working line: pnpm add -D of the same spec succeeded and wrote "@objectstack/skills": "18.0.0".
• Why it matters: create-objectstack installs with pnpm when pnpm is available, so a scaffolded app is commonly a pnpm project.

Sites (main)

• skills/README.md (≈:11)
• skills/objectstack-upgrade/SKILL.md (≈:129). This is the upgrade skill an agent follows, so it is on the 18.0 upgrade path.

Done when

• Each site gives the line for the project's own package manager (pnpm / npm / yarn, or one line plus the rule), in the spelling docs: the @objectstack/skills install line npm install --save-dev … exits 1 in a pnpm-installed project (edgesOut), and five sites still print it as the only command #24926's content/docs rows use (PR docs(releases): the 18.0.0 notes and upgrade checklist, walked from 17.7.0; Upgrading's table gains 18.0.0 and 17.5–17.7 #24922's releases/v18/ line is the precedent).
• The line each site keeps is run once in a pnpm-installed and once in an npm-installed scaffold, and the reading is recorded on the PR.
• ⛔ No new gate.

Generated by Claude Code