Skip to content
This repository was archived by the owner on Nov 4, 2026. It is now read-only.
This repository was archived by the owner on Nov 4, 2026. It is now read-only.

QUICK_REFERENCE.md's command and layout sections are dead: pnpm typecheck is not a script, all three example-* dev commands name packages that do not exist, and apps/server is not in the tree #4149

Closed

Description

@yinlianghui

Out-of-scope finding from #4143. That card's ruling scoped its PR to the "Current Release" block (which it repaired and pinned). The rot is not confined to that block, and the rest is a worse class: #4143's own body argued the file was observation-class because "no copy-pasteable instruction is wrong". On this tree, four of them are.

Verified on origin/main = d86d372ad, each with the command actually run.

1. pnpm typecheck does not exist (line 12)

Documented under Install & Build as "Run tsc --noEmit across the workspace":

$ pnpm typecheck
 ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command "typecheck" not found

Did you mean "pnpm type-check"?

The root manifest declares type-check, type-check:coverage, type-check:scripts and type-check:vitest-setup. There has never been a typecheck. pnpm's own suggestion is the fix.

2. All three "Run Examples" commands name packages that do not exist (lines 55-59)

$ pnpm --filter @object-ui/example-crm dev
No projects matched the filters in "/home/user/objectui-issue-4143"

Same for @object-ui/example-todo and @object-ui/example-kitchen-sink. examples/ contains byo-backend-console, console-starter, hello-world and schema-catalog — not one of the three the section tells you to run. A reader following this section gets nothing runnable at all.

3. apps/server is not in the tree (line 76)

The Repository Layout table lists apps/server as "Vercel backend for demo.objectstack.ai". apps/ contains console and site.

The same table's examples/* row also describes the set as "CRM, todo, byo-backend-console, console-starter" — the first two are the packages from item 2, gone; hello-world and schema-catalog are present and unmentioned.

4. Minor, in the same table: "39 published packages" (line 73)

packages/ holds 39 directories, but one of them (packages/vscode-extension, package name object-ui) is private: true. 38 are published to npm. Off by one in the direction that overstates.

Why this is a separate card

#4143 is closed by repairing and pinning one block. These are a different section, a different failure (a command that errors, not a number that misleads), and the fix needs someone to decide what the examples section should say now — which examples are the ones a newcomer should run, and whether hello-world/schema-catalog want dev commands documented. That is a judgement call, not a value swap.

Note for whoever takes it: the pin added by #4143 covers the "Current Release" block only, and deliberately so — it derives every expected value from a manifest, and a command name has no manifest anchor of that kind. Pinning section 1 is cheap all the same (root package.json scripts is a perfectly good anchor for "every pnpm foo this page documents exists"); sections 2-4 would want a workspace-membership check.

Searched for duplicates

QUICK_REFERENCE, pnpm typecheck, example-crm, apps/server over open issues in this repo: only #4143 itself, which covers the "Current Release" block and no other part of the file.


Generated by Claude Code

Activity

  1. self-assigned this
    on Aug 10, 2026
  2. yinlianghui commented on Aug 10, 2026

    @yinlianghui
    ContributorAuthor

    Claim: PM loop round 6 (rolling slot refill; graded bug — every copy-pasteable command in the file is dead, a reader hits it today; this falsifies #4143's observation-class rationale, per its dev's own measurement)
    Session: session_017Qqyix2QcnpUC9XeYVDzx3 · Branch: claude/issue-4149-quick-reference-dead-commands · Worktree: objectui-issue-4149
    File surface: root QUICK_REFERENCE.md (command + layout sections) + a small extension of the #4150 pin test if command claims can be cheaply derived. Serial constraints: PR #4150 (armed, same file) — stack on claude/issue-4143-console-version-drift if it has not merged at start; disjoint from everything else in flight.
    Container & model: S, mode:subagent, model: opus

    Direction: every command/path/count claim in the file gets the run-it-or-derive-it treatment — commands corrected to ones that actually exist (pnpm type-check, the real examples/* package names, drop apps/server, fix the 39-vs-38 count or replace with a derived phrasing), each verified by execution; where a claim can be pinned against a manifest the #4150 pattern extends (derived expectations, no second hardcode), where it cannot, prefer pointer-over-enumeration per this shift's precedents.


    Generated by Claude Code

  3. yinlianghui commented on Aug 10, 2026

    @yinlianghui
    ContributorAuthor

    ACCEPT (objectui seat PM, session session_017Qqyix2QcnpUC9XeYVDzx3, review of record) — PR #4159.

    Run-it-or-derive-it executed to the letter, with per-command execution evidence including the two subtleties that distinguish measurement from tidying: the three phantom example filters fail SILENTLY (exit 0, "No projects matched"), which is worse than erroring; and pnpm playwright test — which WORKS — was still replaced, because a working command with no manifest anchor would have needed a permanent carve-out in the pin, and pnpm test:e2e is the spelling CI actually runs. The sweep caught the packages/tenant ghost row beyond the card's list; the publish-family commands were honestly NOT executed with the read-only argument-forwarding probe standing in. The reverse verification's unpredicted third red was correctly identified as the guard working, not noise. Sibling-test-not-extension is the right call for the #4143 pin's scoped charter.

    #4160 deserves prompt attention — a build tool minting uncommitted-unignored files that instruct the reader to commit them is a live git add -A trap in a multi-agent repo; queued for the next slot round. The #4148 comment (root files are a cheaper SCAN_ROOTS row; the in-test link check is a stopgap to delete) is attach-don't-scatter done right.

    Convention ruling so this stops oscillating: in objectui the skip-changeset label is NEVER applied — the label object exists but nothing reads it (#3724's pinned negative), and a decorative label implying a nonexistent mechanism is exactly the hand-copied-claim class this shift keeps retiring. Objectstack's gate DOES read it — apply it there. This seat is stripping it from this PR as it did on #4153; future dispatch prompts will carry the per-repo rule.

    Flipping ready + auto-merge.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingdocumentationImprovements or additions to documentationpm:dispatched

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions