[codex] Update project Specrew assets to 0.38.0

[VenyaBrodetskiy]

Summary

Updates this project checkout to the generated Specrew 0.38.0 project state:

• records the project Specrew extension registration as 0.38.0
• updates .specrew/config.yml platform pins to Spec Kit 0.9.4 and Squad 0.10.0
• adds generated specrew-code-rules skill surfaces for Agents, Claude, Cursor, and GitHub
• refreshes generated coordinator/refocus/host binding surfaces

Validation

• pwsh -NoProfile -ExecutionPolicy Bypass -File .\scripts\specrew.ps1 --version
• pwsh -NoProfile -ExecutionPolicy Bypass -File .\tests\integration\publish-module-harness.tests.ps1
• pwsh -NoProfile -ExecutionPolicy Bypass -File .\tests\integration\version-info-states.tests.ps1
• git diff --cached --check

Note: specrew update --info --skip-update-check was attempted but this execution shell does not have npm on PATH, so the Squad latest-version probe could not complete.

[Copilot]

Pull request overview

This PR updates the repository’s Specrew-managed project state to Specrew 0.38.0, including updated platform pins, refreshed coordinator/governance surfaces, and newly generated specrew-code-rules skill surfaces across supported hosts.

Changes:

• Bumps project pins/registration to Specrew 0.38.0 (Spec Kit 0.9.4, Squad 0.10.0).
• Adds generated specrew-code-rules skill surfaces for GitHub, Claude, Cursor, and Agents.
• Refreshes coordinator/governance guidance (including refocus and boundary handoff packet shape) and updates Claude hook bindings.

Reviewed changes

Copilot reviewed 19 out of 19 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
CLAUDE.md	Adds Specrew-managed coordinator guidance for Claude.
AGENTS.md	Adds Specrew-managed coordinator guidance for Agents host surface.
.squad/casting/registry.json	Regenerates baseline casting registry (content-equivalent, formatting/order changes).
.specrew/config.yml	Updates platform pins (Spec Kit / Squad) for Specrew 0.38.0 baseline.
.specify/extensions.yml	Updates recorded specrew-speckit extension version to 0.38.0.
.github/skills/specrew-refocus/SKILL.md	Updates refocus skill docs with host-specific digest rule note.
.github/skills/specrew-code-rules/SKILL.md	Adds new specrew-code-rules skill for GitHub host.
.github/skills/specrew-code-rules/.specrew-managed	Marks GitHub specrew-code-rules skill directory as Specrew-managed.
.github/copilot-instructions.md	Appends Specrew-managed coordinator block for Copilot instructions.
.github/agents/squad.agent.md	Refreshes governance guidance, including six-section human re-entry packet template.
.cursor/rules/specrew-code-rules/SKILL.md	Adds new specrew-code-rules rule surface for Cursor.
.cursor/rules/specrew-code-rules/.specrew-managed	Marks Cursor specrew-code-rules rule directory as Specrew-managed.
.claude/skills/specrew-refocus/SKILL.md	Updates refocus skill docs with host-specific digest rule note.
.claude/skills/specrew-code-rules/SKILL.md	Adds new specrew-code-rules skill for Claude host.
.claude/skills/specrew-code-rules/.specrew-managed	Marks Claude specrew-code-rules skill directory as Specrew-managed.
.claude/settings.local.json	Updates Claude hook dispatcher invocations to include HostBinding payload.
.agents/skills/specrew-refocus/SKILL.md	Updates refocus skill docs with host-specific digest rule note.
.agents/skills/specrew-code-rules/SKILL.md	Adds new specrew-code-rules skill for Agents host.
.agents/skills/specrew-code-rules/.specrew-managed	Marks Agents specrew-code-rules skill directory as Specrew-managed.

[VenyaBrodetskiy]

@alonf I know I opened this PR, but basically this PR is just specrew update in this project and I saw many concerning changes which might lead to some issues in future.
I am not sure about anything, so I am asking your support to review and think if it's done by design or accidentally

[VenyaBrodetskiy]

@alonf does specrew manage local project settings of claude? do you think it's good design?

[VenyaBrodetskiy]

@alonf 2 strange things for me here:

• I didn't ask to install cursor, I am not using it, but specrew installed it just in case?
• I think for cursor you don't need to create special instruction in .cursor/rules, as cursor respects .agents/skills and agents.md

[VenyaBrodetskiy]

copilot respects skills from .agents/skills

[VenyaBrodetskiy]

@alonf it used my local squad version to change config for everyone using this repo. is it good approach?

[VenyaBrodetskiy]

there is a trick to ask Claude to read agents.md

just paste this instead of instruction:
"@AGENTS.md"

[VenyaBrodetskiy]

what if project had AGENTS.md before specrew? I think installation of specrew will override AGENTS.md in this case? is it by design?

[alonf]

@VenyaBrodetskiy — thanks for getting the self-host assets moving; they'd drifted badly (the extension registration was stuck at 0.32.0 and AGENTS.md/CLAUDE.md were missing entirely). I'd like to take this PR further: let''s make it a full catch-up — bring everything current, including the platform dependencies, and fix the breaking changes that fall out of that.

What I''d like this PR to cover

1. Bump both dependencies to current

• Squad -> 0.10.0 — you already have this; it''s the latest stable and additive (state-backends + docs), no breaking change.
• Spec Kit -> 0.11.2 (latest). This is where the real work is.

2. Fix the Spec Kit 0.10+ breaking changes
Spec Kit 0.10.0 shipped breaking changes that Specrew still depends on:

• --ai was removed (now --integration <key>; --ai-commands-dir/--ai-skills -> --integration-options). Specrew passes --ai copilot in scripts/specrew-init.ps1 (~line 621): @('init','--here','--ai','copilot','--script','ps','--ignore-agent-tools'). That must become --integration copilot — please confirm copilot is the correct integration key on 0.11.2 and that it reproduces the same agent setup.
• --no-git was removed — git is now opt-in (specify extension add git after init). Check whether Specrew relies on specify init setting up git and adjust if so (we do our own boundary commits, so it may be fine).
• Per-event hook lists + priority ordering changed (spec-kit [001-specrew-product][Iteration 009][T-902] Update iteration-artifact contract for reviewer closeout enforcement #2798) — re-validate that our extension''s hook registration (after_specify / after_plan / before-plan / after-tasks / before-implement) still fires under the new format.
• Re-check that --ignore-agent-tools is still valid, and that the new additive category/effect extension-schema fields don''t require changes to our extension.yml.
• Move the pins to speckit 0.11.2 / squad 0.10.0, and bump max_tested in scripts/internal/supported-versions.yml to match — but only after the test below passes.

3. Fix the current lint failure
The regenerated .github/agents/squad.agent.md has an MD046 violation (indented vs fenced code block, ~line 1520) — that''s the red CI Lint. Main''s copy is clean, so the regeneration introduced it.

Required validation — a real manual test

This touches the actual runtime contract with Spec Kit, so file-presence and unit-green are not enough. Please run a manual end-to-end test and paste the result into the PR:

1. Install Spec Kit 0.11.2 + Squad 0.10.0.
2. specrew init a fresh project.
3. Run a complete feature lifecycle through it — spec -> plan -> tasks -> implement -> review -> retro -> closeout — and confirm the boundaries, hooks, and slash-commands all work end to end.

That full-lifecycle run is the acceptance bar for this PR.

One more thing — Proposal 198

This drift (and the version lag) is really a symptom of a missing process step: nothing regenerates the self-host or bumps the dependencies on release, so it rots until someone notices. I''ve written Proposal 198 — Self-Host & Dependency Currency: deterministic regeneration + a release-time self-update + a per-release dependency-currency step + a CI drift gate, so this never silently happens again. (I''ll post the proposal link here in a follow-up.)

Would you be interested in picking up Proposal 198 as a feature after this PR? It''s a natural follow-on from exactly the work you''re doing here — have a read once I share it and let me know.

[alonf]

Proposal 198 is up for reading here: #2883 — have a look when you get a chance.

[alonf]

One more small source fix to fold into the catch-up while you''re in the host model:

hosts/claude/host.psd1 carries a stale comment (~lines 40-43) — "PostToolUse is UNREGISTERED per TG-004 option (a)" — that contradicts its own data: the Registrations array and DispatcherRuntime.B3DeliveryEvents both register PostToolUse (iteration 002 re-registered it for B3 delivery). Please update the comment to match the actual binding (PostToolUse registered; B3 fires on PostToolUse + UserPromptSubmit) so the next reader isn''t misled.

That, the Spec Kit 0.10+ adaptation, the pin + max_tested bumps, and the MD046 fix are all in scope for this PR.