Skip to content

Commit 993e4b4

Browse files
committed
chore(release): v0.244.0 — version coherence bump, changelog section cut, 0.209.0 rotated to historical archive
1 parent ff03a3c commit 993e4b4

5 files changed

Lines changed: 22 additions & 21 deletions

File tree

.claude-plugin/marketplace.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99
{
1010
"name": "devt",
1111
"description": "Zero-dependency multi-agent development workflow plugin. Language-agnostic — adapts to any project via .devt/rules/ convention. Commands -> Workflows -> Agents architecture with learning loops.",
12-
"version": "0.243.0",
12+
"version": "0.244.0",
1313
"source": "./",
1414
"author": {
1515
"name": "Emre Camdere",

.claude-plugin/plugin.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"name": "devt",
33
"displayName": "devt",
44
"description": "Zero-dependency multi-agent development workflow plugin. Language-agnostic -- adapts to any project via .devt/rules/ convention. Commands -> Workflows -> Agents architecture with learning loops.",
5-
"version": "0.243.0",
5+
"version": "0.244.0",
66
"defaultEnabled": false,
77
"author": {
88
"name": "Emre Camdere",

CHANGELOG.md

Lines changed: 3 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,12 @@ All notable changes to devt will be documented in this file.
44

55
Format follows [Keep a Changelog](https://keepachangelog.com/). Versions follow [Semantic Versioning](https://semver.org/). The `[Unreleased]` section below stages changes for the next version — when bumping, rename it to `## [X.Y.Z] - YYYY-MM-DD` so the release workflow's changelog extractor (`scripts/extract-changelog.sh`) can find it.
66

7-
Older releases (v0.1.0–v0.208.0) are rotated into `docs/archive/CHANGELOG-historical.md` — the root file keeps `[Unreleased]` plus the most recent releases (rotation ceiling enforced by smoke gate K288).
7+
Older releases (v0.1.0–v0.209.0) are rotated into `docs/archive/CHANGELOG-historical.md` — the root file keeps `[Unreleased]` plus the most recent releases (rotation ceiling enforced by smoke gate K288).
88

99
## [Unreleased]
1010

11+
## [0.244.0] - 2026-08-18
12+
1113
### A parallel review stamped three phases DONE without executing them — and six more findings from the first full-fan-out field run
1214

1315
A third field evaluation — the first real five-lane parallel review on a downstream project — filed six problem findings, then (in calibration mode, answering targeted questions) disproved two of its own diagnoses. What survived validation against the code and the run's artifacts became this batch; what didn't shaped what was deliberately NOT built.
@@ -890,19 +892,3 @@ Post-release adversarial validation of the 0.205.0–0.209.0 batch: every new ga
890892
### Added
891893

892894
- **Gate K326 — state-router ReferenceError sweep.** Invokes every router verb (73 at gate time) in a minimal fixture and asserts none dies on an unresolved identifier — the regression net for the facade-split risk class, where a function moved between state submodules references a name its new home doesn't import and fails at CALL time (both real breaks of this class — `_assertLanesRegistered→listLaneOutputs` and `computeGraphifyImpactPlan→_activeRange` — shipped past load checks and a flat import audit). Known limit stated in the gate: a verb that swallows the error in a bare catch hides it from the sweep too; per-verb behavioral gates remain the deep net. Current sweep: 0/73 hits.
893-
894-
895-
## [0.209.0] - 2026-07-26
896-
897-
### Added
898-
899-
- **The memory-doc batch — three decisions the sessions kept re-deriving are now tombstoned.** `ADR-003` (Agent Teams adoption deferred: experimental + non-`/resume`-restorable, while file-based state is load-bearing for `/devt:next` — trigger named in RETIREMENT-WATCH), `REJ-003` (no OpenTelemetry/telemetry SDK: zero-dep contract, SDK init would dwarf the measured 26–73ms hook fires, no cross-process audience — JSONL side-channels + aggregation verbs are the stack), `REJ-004` (no Rust/native CLI rewrite: zero-build Node stdlib IS the distribution contract; node startup ~26ms is the measured floor, a binary buys ~25ms/call for a per-platform build matrix). All indexed, FTS-retrievable, and keyword-armed against re-proposal.
900-
901-
### Removed
902-
903-
- **`scripts/check-docs.sh` retired.** Doc-completeness checker for a user project's `.devt/rules/documentation.md`, invoked by no workflow, agent, skill, or CI surface — the same maintained-but-unwired class as the retired injection scanner. RETIREMENT-WATCH records it as revivable receipt-gated if a docs workflow ever wants a deterministic completeness leg.
904-
905-
### Validated non-issues (measured, not shipped)
906-
907-
- **Lazy facade requires — refuted by measurement.** The entire 5-submodule state family parses in **+2ms** over bare node startup (28ms vs 26ms; full CLI verbs 37–39ms warm). Lazy getters plus ~50 call-site rewrites to save 2ms fails the receipt bar; the earlier ~440ms stop-hook reading was load-inflated, not require-dominated.
908-
- **bash-guard in-process fast path — deferred with a named trigger.** Measured chain: runner-node 26ms + bash ~8ms + CLI-node 39ms = **73ms warm**; in-process would save ~45ms/call (~1–2s/day at observed frequency) at the cost of a second execution model inside the runner. Recorded in RETIREMENT-WATCH's receipt-gated list — TRIGGER: sustained warm p50 > 250ms on a PreToolUse guard, or an order-of-magnitude frequency jump.

VERSION

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
0.243.0
1+
0.244.0

docs/archive/CHANGELOG-historical.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,26 @@
1-
# devt — Historical Changelog (v0.1.0–v0.208.0)
1+
# devt — Historical Changelog (v0.1.0–v0.209.0)
22

33
Older release sections rotated out of the root CHANGELOG.md, newest first. The root file keeps the [Unreleased] section plus the most recent releases; everything older lives here.
44

55
Format follows [Keep a Changelog](https://keepachangelog.com/).
66

77
---
88

9+
## [0.209.0] - 2026-07-26
10+
11+
### Added
12+
13+
- **The memory-doc batch — three decisions the sessions kept re-deriving are now tombstoned.** `ADR-003` (Agent Teams adoption deferred: experimental + non-`/resume`-restorable, while file-based state is load-bearing for `/devt:next` — trigger named in RETIREMENT-WATCH), `REJ-003` (no OpenTelemetry/telemetry SDK: zero-dep contract, SDK init would dwarf the measured 26–73ms hook fires, no cross-process audience — JSONL side-channels + aggregation verbs are the stack), `REJ-004` (no Rust/native CLI rewrite: zero-build Node stdlib IS the distribution contract; node startup ~26ms is the measured floor, a binary buys ~25ms/call for a per-platform build matrix). All indexed, FTS-retrievable, and keyword-armed against re-proposal.
14+
15+
### Removed
16+
17+
- **`scripts/check-docs.sh` retired.** Doc-completeness checker for a user project's `.devt/rules/documentation.md`, invoked by no workflow, agent, skill, or CI surface — the same maintained-but-unwired class as the retired injection scanner. RETIREMENT-WATCH records it as revivable receipt-gated if a docs workflow ever wants a deterministic completeness leg.
18+
19+
### Validated non-issues (measured, not shipped)
20+
21+
- **Lazy facade requires — refuted by measurement.** The entire 5-submodule state family parses in **+2ms** over bare node startup (28ms vs 26ms; full CLI verbs 37–39ms warm). Lazy getters plus ~50 call-site rewrites to save 2ms fails the receipt bar; the earlier ~440ms stop-hook reading was load-inflated, not require-dominated.
22+
- **bash-guard in-process fast path — deferred with a named trigger.** Measured chain: runner-node 26ms + bash ~8ms + CLI-node 39ms = **73ms warm**; in-process would save ~45ms/call (~1–2s/day at observed frequency) at the cost of a second execution model inside the runner. Recorded in RETIREMENT-WATCH's receipt-gated list — TRIGGER: sustained warm p50 > 250ms on a PreToolUse guard, or an order-of-magnitude frequency jump.
23+
924
## [0.208.0] - 2026-07-26
1025

1126
### Fixed

0 commit comments

Comments
 (0)