Skip to content

comments: the two references to the command-vocabulary gate name its … - #6

Merged
coderoast-dev merged 1 commit into
mainfrom
claude/coderoast-claude-md-malf-p80u1w
Sep 18, 2026
Merged

coderoast-dev merged 1 commit into
mainfrom
claude/coderoast-claude-md-malf-p80u1w

Conversation

@coderoast-dev

Copy link
Copy Markdown
Collaborator

…check module, not the deleted script

src/hooks/useEngineLifecycle.ts and src/types/engine.ts each explain that this client does not re-declare the engine command vocabulary because a gate in the superproject asserts set equality against coderoast-server's command_catalog.hpp. Both named that gate as scripts/command_vocabulary_lint.py, a file that was DELETED in the superproject on 2026-09-17 when the gate became the pharos check module scripts/pharos/checks/command_vocabulary.py (superproject plan row DN-108.P1.2 — every gate becomes a check module, DN-108.D2, and a module is never run by path). Both comments now name the one spelling an agent or a desk types, pharos check --module command_vocabulary.

Vocabulary only: no TypeScript changes, no behaviour changes, and the point both comments make is unchanged — the gate is deliberately NOT in this repository's suite, because only a full workspace checkout holds both sides of the seam, and the vitest arm that tried to reach across the repository boundary threw ENOENT on every run for a month while the pipeline reported green.

Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw

…check module, not the deleted script

`src/hooks/useEngineLifecycle.ts` and `src/types/engine.ts` each explain that this client does
not re-declare the engine command vocabulary because a gate in the superproject asserts set
equality against `coderoast-server`'s `command_catalog.hpp`. Both named that gate as
`scripts/command_vocabulary_lint.py`, a file that was DELETED in the superproject on 2026-09-17
when the gate became the `pharos check` module `scripts/pharos/checks/command_vocabulary.py`
(superproject plan row DN-108.P1.2 — every gate becomes a check module, DN-108.D2, and a module
is never run by path). Both comments now name the one spelling an agent or a desk types,
`pharos check --module command_vocabulary`.

Vocabulary only: no TypeScript changes, no behaviour changes, and the point both comments make
is unchanged — the gate is deliberately NOT in this repository's suite, because only a full
workspace checkout holds both sides of the seam, and the vitest arm that tried to reach across
the repository boundary threw ENOENT on every run for a month while the pipeline reported green.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
@netlify

netlify Bot commented Sep 18, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for elaborate-malasada-e00aa3 ready!

Name Link
🔨 Latest commit bf97573
🔍 Latest deploy log https://app.netlify.com/projects/elaborate-malasada-e00aa3/deploys/6aaccda2a767bb000896002f
😎 Deploy Preview https://deploy-preview-6--elaborate-malasada-e00aa3.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderoast-dev
coderoast-dev merged commit 37490f7 into main Sep 18, 2026
4 of 5 checks passed
@github-actions

Copy link
Copy Markdown

🔬 Sift — structural diff of your CI logs

⚠️ Stale baseline — 3d 14h old, past the 72h bound. No green run has re-seeded it since; this diff compares against that aged snapshot and loses meaning as the streak grows.

✅ No structural change. 509 → 509 log lines, same behaviour.

Deterministic — same inputs, same comment. Runs in your CI; your logs never leave it. · What is this? · Baseline: last green run on main @ f5ae1c2 · 3d 14h old · as of bf97573

@coderoast-dev
coderoast-dev deleted the claude/coderoast-claude-md-malf-p80u1w branch September 19, 2026 08:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants