Skip to content

archctx 0.2.0

Choose a tag to compare

View all tags
@Ancienttwo Ancienttwo released this 05 Jul 20:43
v0.2.0
9597aee

Official public npm release for archctx 0.2.0.

NPM: https://www.npmjs.com/package/archctx/v/0.2.0
Install: npm install -g archctx@latest
Tarball: https://registry.npmjs.org/archctx/-/archctx-0.2.0.tgz
License: Apache-2.0
Integrity: sha512-VQ/CdgnyqkfB8VcCGXGHJBs67HmLy5z8luG/ynNMGzXUopoowNATlLdbVHFypqGVxCU9wTkuReOJrX1WQx9QEQ==
Shasum: 8cebc9e3cccf5fe941435fc52578d3b8079e275d
SHA256: 0511a985e413a3a8f4c0fc0423a912e2a4d834244f88e505283a30b380937d54

Verified with full bun test (962 pass, 0 fail), npm dry-run readback, npm registry metadata readback (dist-tags.latest, shasum, integrity match), and direct npx archctx@0.2.0 help/doctor/update --check checks on Node 24.

What's new since 0.1.5:

  • New: archctx audit local architecture audit (opt-in via manifest, advisory-only, process-level read-only tool whitelist), plus audit approve GitHub issue publishing via a dedicated Issues:write-only PAT (ARCHCONTEXT_GH_ISSUES_TOKEN, never ambient gh auth), a public-repo confirmation token, and crash-safe resume with per-draft dedup markers.
  • Changed: the CLI now maps envelope failures to nonzero exit codes (scripts relying on an always-zero exit must adapt); the daemon now defaults to a 30-minute idle auto-exit (--idle-timeout-ms, 0 = resident); stale/incompatible daemon entrypoints are now detected and refused — run archctx daemon upgrade once after upgrading.

Boundary: audit stays opt-in and default-off; this release does not change ledger-authoritative mode or its enforcement boundary.

Assets 2
Loading