WebDev Agent Kit v0.2.0

This release turns WebDev Agent Kit from a Codex/Claude portable skill bundle into a more complete multi-client agent operating kit with capability-first MCP handling, smarter verification, stricter frontend anti-patterns, native client installation paths, and release-ready download artifacts.

Highlights

• Added client-specific packages for Codex, Claude Code, Cursor, VS Code Codex, and VS Code Claude.
• Added a capability-first MCP/tool model instead of assuming specific server names.
• Added smart verification budgeting to prevent over-testing small changes.
• Added strict rules preventing agents from reading or editing host-project README/docs during normal work.
• Added stronger frontend anti-patterns, including useCallback misuse, parallel status booleans, implicit return types, function declarations, and test authoring by default.
• Added Russian installation guides for each supported client.
• Added README download links for stable latest release artifacts.

Release Artifacts

Download the package that matches your client:

• webdev-agent-kit-codex.tar.gz
• webdev-agent-kit-claude-code.tar.gz
• webdev-agent-kit-cursor.tar.gz
• webdev-agent-kit-vs-code-codex.tar.gz
• webdev-agent-kit-vs-code-claude.tar.gz

Versioned copies are also published for this release, together with:

• SHA256SUMS

Added

Client-specific package targets

The build and release flow now produces dedicated packages for:

• Codex
• Claude Code
• Cursor
• VS Code Codex
• VS Code Claude

The release workflow also keeps legacy generated targets for current validators.

Capability-first MCP/tool model

Added:

• tool-capabilities-manifest.json
• common/tool-capability-model.md
• common/mcp-installation-policy.md

Skills now describe required capabilities such as:

• project_files
• current_library_docs
• web_platform_docs
• rendered_visual_evidence
• repo_metadata

Instead of assuming that a named MCP server exists, agents must detect whether the current client actually provides the required capability. If not, they must use an allowed fallback and clearly report confidence impact or blocked checks.

Native client adaptation

Added:

• common/client-adaptation-policy.md
• templates/project/client-profile.md
• templates/project/mcp-profile.md
• root pointer templates for Codex, VS Code Codex, Cursor, and Claude Code

Onboarding now records client/tool facts in local-only project overlays instead of mixing host-client state into reusable bundle rules.

Smart verification budget

Added:

• common/smart-verification-budget.md
• common/diff-impact-verification-rules.md
• common/mcp-availability-detection-rules.md

Small CSS-only changes, such as background color or decorative mask updates, should no longer trigger full-repo lint, full typecheck, dev server startup, route discovery, or browser QA by default.

Repeated visual failures can still escalate to targeted rendered visual QA when the task requires it.

Host README/docs boundary

Added:

• common/host-project-documentation-boundary.md
• common/anti-patterns/no-host-readme-or-docs-edits-without-approval.md
• scripts/check_readme_boundary.py

Agents must not read, use as context, route from, derive facts from, or edit a host project’s README/docs during normal implementation, bugfix, refactor, onboarding, visual QA, or review work.

README/documentation edits require an explicit documentation task and approved scope.

New frontend anti-patterns

Added or tightened anti-pattern rules for:

• no implicit return types
• no function declarations by default
• prefer object destructuring
• no parallel lifecycle/status booleans
• no test authoring by default
• no console file reads before filesystem/project-file capability
• no host README/docs edits without approval
• strict useCallback boundary

useCallback is now explicitly forbidden by default unless there is a proven identity-sensitive consumer, a real observed issue, and a safe dependency explanation.

Pattern library manager

Added:

• skills/pattern-library-manager

This skill maintains reusable approved patterns and anti-patterns with bad/good examples, source-sourcing rules, graph links, and eval updates.

Link checking

Added:

• scripts/check_links.py
• .github/workflows/link-check.yml

Local Markdown links are checked on PR/push. External link checks run on a scheduled workflow.

Russian installation guides

Added draft Russian guides under docs/install/**:

• Codex
• Claude Code
• Cursor
• VS Code Codex
• VS Code Claude

These guides explain archive choice, native pointers, MCP capability behavior, fallback behavior, onboarding via адаптируйся, and validation expectations.

Changed

• mcp-toolchain-manager now reports capabilities, providers, missing tools, fallbacks, approval needs, and confidence impact.
• project-onboarding-adapter now detects installed client targets and creates local-only client/MCP profiles.
• frontend verification rules now use a cost-aware verification ladder.
• README has been rewritten as a human-facing release/download guide and explicitly excluded from runtime policy.
• Release workflow now publishes stable and versioned client archives.
• validate_skill_pack.py now includes README-boundary validation.
• CHANGELOG.md and AUDIT_AND_OPTIMIZATION_PLAN.md now reflect the release-prep state.

Validation

Before merging the release-prep PR, the following checks passed:

• skill-pack-ci
• quality-ci
• link-check

The release workflow validates:

• schemas
• source bundle
• skill eval fixtures
• generated targets
• Codex target
• Claude target
• excluded paths
• release artifacts and checksums

Upgrade Notes

For existing projects:

1. Download the package that matches your agent client.

2. Replace reusable .agents/** bundle files.

3. Preserve local-only project overlays such as:

   • .agents/project/**
   • project/client-profile.md
   • project/mcp-profile.md

4. Keep root pointers small:

   • Codex / VS Code Codex / Cursor: AGENTS.md
   • Claude Code / VS Code Claude: CLAUDE.md

5. Run:

адаптируйся

6. Review any proposed local overlay changes before accepting durable project facts.

Do not copy host-project README/docs into reusable bundle rules, and do not let agents edit project documentation unless that documentation task is explicit and approved.

Known Notes

• GitHub Wiki pages still need to be published manually from the repo-side drafts in docs/install/**.
• A dedicated installed-bundle update skill was planned but not included in this release because the current implementation needs a cleaner follow-up pass.
• The VS Code Claude target uses the Claude-style root pointer shape.

Можно еще сделать короткую версию для GitHub Release textarea, если хочешь меньше текста.