v1.43.1

Changed

• Two lint messages name things the way a person would, and leave the element id to the hint. A consumer may show a diagnostic's message to someone who never sees the source, and 1.43.0's reworded W_PATH_TOO_NARROW and W_FURNITURE_WALL_COLLISION quoted ids there. W_PATH_TOO_NARROW now names a bottleneck door by the rooms it joins, the room nearer where the walk starts first: — the bottleneck is the door between "Hall" and "Bath", 640 mm clear (was door "d_bath"), or the door from outside into "Hall" for a front door; a list of several takes a comma before its last and. W_FURNITURE_WALL_COLLISION says penetrates the partition wall at x 4000 (was partition wall "w_part" at x 4000), or a partition wall when the wall is curved or diagonal. The ids are unchanged in the hints, which already carried them (Widen door "d_bath" to …, wall "w_part"), so an agent edits by the same handle; the clause shapes (— the bottleneck is …, N mm clear, — the bottlenecks are …: widen them together) are kept. W_FIXTURE_BACK_TO_ROOM and W_ROOM_NO_FIXTURE already quoted only a room or fixture name and are unchanged. lint() message text only: no SVG, describe(), compile diagnostic, code, span or hint moved, and no diagnostic was added or withdrawn.

• @chanmeng666/arch-plan 0.1.1 is published by the release workflow. The element is unchanged; the version exists so the package's first trusted-publishing release (OIDC, with provenance) goes through release.yml instead of the owner's machine, as the core and the shim already do.

• @chanmeng666/archlang-mcp 0.2.26 marks every tool read-only. Each tool declares MCP annotations: readOnlyHint true, destructiveHint false, idempotentHint true, openWorldHint false. Every tool computes over its arguments and returns text or an image; none writes to the caller's environment, and link builds its URLs locally. tools/list is otherwise unchanged. The hosted server already serves them.

• The portable plugin manifest carries the OpenAI plugin directory's fields. npm run gen:agent-manifests writes them, and npm run build:openai-plugin builds the directory's upload ZIP with the hosted MCP server; plugins/archlang/mcp.json keeps the local stdio server. The brief-to-plan and edit-plan skills gain a Scope section: the commands they run and the files they change.

• The MCP shim's and the VS Code extension's core ranges are re-pinned to this release, and the shim re-bakes its spec, llms-full.txt, grammar and schemas when it is packed.

Changed — internal, output byte-identical

• Net internal area is computed once per storey and once per room. On a schedule rooms plan 1.43.0 rebuilt every storey's wall bands and redid each room's exact area on every path that reads it (the resolver's margin-table count, the drawn ROOM SCHEDULE, describe()'s rooms[] and schedule[]), and a multi-storey plan resolves each storey twice; describe() of examples/hillside-villa.arch built each storey's bands four times. Both are now memoised on their exact inputs (src/analyze/net-area-memo.ts; clearCache() empties it), so every figure, SVG byte, describe() and lint() result is unchanged and no byte-identity row was re-measured. On examples/hillside-villa.arch (best of six interleaved medians, ms) compile() 74 → 43, describe() 120 → 54, lint() 90 → 49.

Security

• The two advisories the nightly audit reported are cleared, lockfile-only (issue #124). npm audit --omit=dev --audit-level=high goes from 2 vulnerabilities (1 high, 1 critical) to 0, with no manifest change and no --force: @modelcontextprotocol/sdk 1.29.0 → 1.32.1 (GHSA-6qxp-vccf-f47h, the SDK's OAuth client sending credentials to an authorization server the MCP server names) and proxy-addr 2.0.7 → 2.0.8 (GHSA-jqcg-44mw-7w3h, an IPv4-mapped IPv6 trust subnet matching every address), the latter through the SDK's express. Neither path is reachable in what ships: the shim and the Worker are MCP servers (stdio and Web-standard Streamable HTTP), which the SDK advisory names as not affected, and the only client in the repository drives the stdio server in build:mcpb's proof; nothing configures an Express trust subnet, and neither the .mcpb bundle nor the Worker bundle contains express or proxy-addr. Both manifests keep ^1.29.0, which already resolves to a fixed SDK on a fresh install, so no shim version bump is due.
• The nightly secret scan is green again. Nine generic-api-key findings were measured SHA-256 byte-identity baselines keyed by accessible (the rule's key-ish word "access"), the documented false positive; each is excluded by its one-line fingerprint in .gitleaksignore, and test/import-module-lets.test.ts, new to that file, gains a content rule in test/opaque-literal-guard.test.ts (digests and corpus directory names only).