Skip to content

v2.6.0 — viewer-v2, rich rules, deep-scan skill, telemetry

Latest
Latest

Choose a tag to compare

View all tags
@gbrbks gbrbks released this 14 May 12:54
· 50 commits to main since this release
v2.6.0
97ed17a

First npm release since 2.5.3 — an 89-commit catch-up. Highlights:

Added

  • Unified local viewer — /archie-viewer now runs the same React UI as the hosted share viewer. Blueprint + Files tabs, per-folder CLAUDE.md browser, click-to-view generated-files tree, an inline rule-management dashboard, and a "Fix this" button that generates agent-agnostic fix prompts for findings & pitfalls.
  • Anonymous, opt-in usage telemetry + npm update checks — config.py, telemetry_sync.py, update_check.py, analytics.py. Consent is asked in-session by the slash commands (via a shared _shared/telemetry-consent.md fragment), not by the npx install — so CI / pipe / agent installs can't silently skip it. Three tiers: community / anonymous / off.
  • /archie-deep-scan is now a modular skill — a SKILL.md router plus self-contained per-step files and fragments. The long pipeline survives /compact and resumes mid-run (--continue, --from N).
  • Rich rules pipeline — rules carry inline severity_class / why / example / forced_by-enables-alternative; the rule synthesizer is the single producer of the unified shape; rule_index.py pre-computes a hot-path enforcement index.
  • ARCHIE_TELEMETRY_ENDPOINT env override so test runs can't hit production.

Changed

  • AGENTS.md is now the canonical agent context; CLAUDE.md is a thin pointer to it. .claude/rules/ topic files plus a browsable enforcement/ directory.
  • Installer hardening — Node 18+ preflight, rejects unknown flags + --help, builds the local viewer at install time (cached by version).
  • README + ARCHITECTURE.md fully resynced with the current architecture.

Fixed

  • JUST_UPGRADED no longer prints "X → X" (installer overwrote the version marker before mark-upgraded re-read it).
  • /archie-scan telemetry runs are now actually uploaded — the legacy telemetry.py path never fired the sync.
  • config.py should-prompt answers via a stdout token, so a crash can't masquerade as "already prompted".
  • Non-interactive installs surface a clear notice instead of silently skipping telemetry consent.
  • Deep-scan Phase 0 scope + Intent Layer prompts are mandatory decision gates, not skippable clarifying questions.
  • A degenerate from == to upgrade marker is dropped instead of emitted.

Full changelog: v2.5.3...v2.6.0

Assets 2
Loading