Repository navigation
v0.4.2
Fixes
archsteer steercrashed on real repos that already had a.cursor/rules/directory (Cursor's own convention) — the CLI tried to write a file where a directory existed. Steering now targets.cursor/rules/archsteer.mdcdirectly and injects proper frontmatter (alwaysApply: true) into empty or frontmatter-less.mdcfiles.- MCP registry
server.jsonused a deprecated schema (2025-07-09 snake_case) — the live registry validates against 2025-12-11 camelCase. Fixed field names and trimmed the description under the registry's 100-char limit.
0.4.1 (rolled into this release — no separate tag was pushed)
- Python dependency resolution was broken: relative imports (
from .x,from ..pkg.mod) and same-package absolute imports (from mypkg import mod) were never resolved to internal edges — only JS/TS relative imports were. Every Python repo'smodel.jsonshowed zero internal dependencies. Fixed. - Manifest dependency extraction now reads
project.dependencies(runtime only) viatomllibinstead of a regex that swept up dev-tooling strings and license identifiers. mcppromoted from an optional extra to a base dependency —uvx/registry runners can't express extras, soarchsteer mcpwas failing on a plain install for exactly the agentic audience the MCP listing targets.- archsteer now dogfoods itself: ships its own
architecture.yaml(engine must not import cli/steer/docs/mcp; stays network-free) and passesarchsteer checkclean. - Listed on the official MCP registry (
io.github.einvoice-dev1/archsteer).
Full diff: v0.4.0...v0.4.2