Dev Control Room v0.18.2

Dev Control Room v0.18.2

Released 2026-09-13. The source version is 0.18.2, and the Windows amd64
package, CI, and remote asset verification are complete.

v0.18.2 is a backward-compatible patch release on top of
v0.18.1. It keeps the existing application, CLI, HTTP, and artifact contracts
and does not add a public API or persistence schema migration.

P1 correctness and first-use fixes

• Resets the Assurance AI-candidate checkbox layout so its text remains
  readable beside the control.
• Separates artifact evidence state and reason from retention state. Coverage
  profiles from failed or timed-out runs are partial; truncated or unparseable
  profiles are invalid. Non-valid artifacts do not count as assurance evidence,
  score input, trace completion, or report evidence.
• Uses one selected Worktree state across Work, discovery, action, external,
  guidance, and Assurance controls.
• Preserves the selected Worktree across discovery requests and refreshes, and
  reports an explicit empty result for the requested target.

P2 product-usability fixes

• Groups repositories and Worktrees discovered from a parent folder instead of
  presenting unrelated checkouts as one flat list.
• Makes the first Assurance action and the plan → approve → run sequence
  explicit when no plan or score exists yet.
• Reduces repeated scheduled no-op activity noise and keeps meaningful events
  prominent.
• Compacts Diagnostics provider rows and replaces excessive status-rail space
  with readable status content.
• Gives dynamic selects and checkbox controls stable form identity where they
  participate in a form.

Release boundary

• The only release asset target is a Windows 11 amd64 ZIP plus SHA256SUMS.
• Linux, macOS, and arm64 packages are not release assets.
• No production, Jenkins, Scheduler, destructive cleanup, or package-manager
  action is performed by this patch or by package generation.
• Native Full, browser regression, package, CI, and release acceptance are
  complete and recorded in docs/VERIFICATION_v0.18.2.md; separate
  company/provider/second-device acceptance remains outside this evidence.

Publication

• Release: v0.18.2,
  published 2026-09-13T07:01:20Z, non-draft and non-prerelease.
• Source/tag: commit 6e2a52ff1f5886adb95cdc50b39c63c4ddf80719, annotated tag
  object e599973b771e65c2e13654c4af7b1d7cb4b8e306.
• CI: run 34743438251
  passed; Linux completed 2026-09-13T06:43:55Z and Windows completed
  2026-09-13T07:00:16Z. Node20/cache warnings were non-fatal.
• Published assets are exactly dev-control-room_0.18.2_windows_amd64.zip
  (13,812,720 bytes) and SHA256SUMS (109 bytes). The downloaded ZIP
  SHA-256 is
  bf19ea76591ff1216c12aca319ebc960fb5e7adba22f776906b043fd2a69036d, and
  the extracted native Windows executable version JSON reports 0.18.2.

Dev Control Room v0.18.1

Dev Control Room v0.18.1

Updated: 2026-09-13

Repository-quality correctness

• Treats reviewed Ruff, pytest, ESLint, and Vitest exit code 1 as a structured
  result while keeping unexpected exit codes as tool failures.
• Maps failed Python and Node test runs to tests_failed and prevents
  deterministic self-improvement from adding unavailable checks.
• Verifies inspection result artifact size and SHA-256 before using it, and
  returns reviewed inspection plans with a current valid digest.
• Restores the selected repository's latest inspection run after a target
  switch and prevents stale browser responses from overwriting the new target.

Component-aware installation and Action safety

• Detects the matching Python/FastAPI or Node/Vue component in a mixed
  repository, resolves its project environment, and executes the approved
  installer from that verified component directory.
• Binds component identity, component root, affected files, writable paths,
  executable, and working directory into the immutable Action Plan.
• Reuses repeated install plans without immutable-plan conflicts and repairs a
  missing planned audit event on a safe retry without creating duplicates.
• Keeps v0.18.0 install plans readable but blocks approval or execution when
  they lack a verified component binding. A pre-upgrade lock is released when
  such a plan is rejected.

Windows storage reliability

• Distinguishes a file-lock timeout that occurs before a storage operation
  starts from an execution-time SQLite busy result.
• Retries only the pre-execution lock case in the cross-process stress harness,
  so an INSERT whose execution status is ambiguous is never replayed.
• Keeps the production five-second lock budget unchanged.

Startup diagnostics test stability

• Verifies that the captured-writer startup test emits no interactive pause
  prompt instead of enforcing a machine-speed wall-clock threshold; the
  focused test passed 50 normal and 20 race repetitions.

Release boundary

• Publishes one Windows 11 amd64 ZIP and SHA256SUMS.
• Does not publish Linux, macOS, or arm64 assets.
• Package installation remains opt-in and requires the existing human approval
  ceremony; no package manager runs while generating a preview.

Dev Control Room v0.18.0

주요 변경\n\n- 저장소별 검사 계획과 실제 실행 가능한 도구를 기준으로 한 품질 검사 흐름\n- Python Ruff/pytest, Node ESLint/Vitest, Go 검사 실행기\n- 결정론적 저장소 품질 점수와 전후 비교\n- 실행 결과 기반 enum-only 개선 제안과 stale evidence 재검증\n- 프로젝트 Python 환경 우선 도구 설치 미리보기와 승인 경계\n- P1/P2 보완: 원자적 CAS 적용, 실행기/버전 digest, writable scope, 승인 거부·취소 fail-closed\n\n## 배포 범위\n\nWindows 11 amd64 ZIP만 제공합니다. Linux/arm64는 릴리즈 자산으로 제공하지 않습니다.\n\n## 검증\n\n- go test ./... -count=1: PASS\n- go vet ./...: PASS\n- focused race tests: PASS\n- UI syntax/tests: PASS\n- Windows amd64 package/version/hash smoke: PASS\n\n실제 패키지 설치나 Jenkins/production 변경은 릴리즈 검증에서 실행하지 않았습니다.

Dev Control Room v0.17.0

Dev Control Room v0.17.0

Updated: 2026-09-10

What changed

• Project setup now detects bounded, read-only evidence for Python/FastAPI,
  Vue, JavaScript/TypeScript, and Go in a selected registered checkout.
• Automatic detection and manual language filters keep mixed-repository
  evidence visible; changed HEAD/configuration evidence resets the filter.
• Setup guidance distinguishes recognized configuration, setup-needed,
  unsupported, and ambiguous states, with the existing Go root checks retained.
• Registration, bounded repository discovery, refresh, reload persistence, and
  responsive first-use flows received the v0.17.0 UX updates.

Support boundary

Python/FastAPI and Vue are read-only setup guidance in M1. This version does
not run their analyzers or tests, install packages, write configuration or
lockfiles, invoke AI, upload source, or add a generic shell runner. A fixture
coverage result is not main-repository coverage. The inspector remains bounded
and does not follow links or special files.

Verification status

Native Full and final browser acceptance passed for source 998325b; the exact
gates, fixtures, hashes, screenshots, and remaining native folder-picker gap
are recorded in VERIFICATION_v0.17.0.md.

The release target is one Windows amd64 ZIP plus SHA256SUMS. The bundled
verification record is a pre-package snapshot; the repository copy also records
the subsequent CI, package, and publication checks when completed.

Dev Control Room v0.16.0

Dev Control Room v0.16.0

Verified release record

• Release commit/tag: 804faf0ea8c84ea182cacd9b07322d5b984dc555 / v0.16.0.
• GitHub CI run 34132276325: Linux and Windows passed. Windows explicitly passed Go tests, race tests, vet, build, and module verification under Go 1.23.0.
• The CI workflow now checks native PowerShell command exits. Windows path-sensitive fixtures use canonical expected paths while preserving raw short-path inputs and foreign-runner routing; no production-code changes were made.
• Dogfood run dogfood-e125339045844519a9e99a79e21142d5: required gate PASS, coverage 58.7%, health 5/5, state 5/5, validator 0, import 201, and dashboard ID matched.
• Journey validation: 373 assertions passed. Native resilience: 15 assertions passed. Browser acceptance covered 7 routes, one h1, main focus, no overflow at 1244 CSS px and 485 CSS px (390 px override rendered 485 px), guide slide 2 persisted after reload, zero console errors, and real-repository registration/read-only scan.
• Windows amd64 package smoke passed: dev-control-room_0.16.0_windows_amd64.zip, 9 archive entries, version returned 0.16.0, and SHA-256 134592f7d0a680e026435d0ef8058e852c832b828939f5a60383d125c3cfa10c matched SHA256SUMS.

Remaining evidence boundaries: the Go 1.23 build-tag test, mutation campaign, and causal quality score were not established by this release record.

v0.15.2 - Dogfood measurement dashboard

Dev Control Room v0.15.2

이번 patch 릴리즈는 v0.15.1의 reproducible dogfood measurement foundation을
실제 제품 workflow에 연결하고, 그 foundation에서 확인된 세 가지 경계를
보강합니다. 측정 결과는 품질 점수나 생산성 주장이 아니라, 제한된 명령과
선택적 관찰을 보존하는 근거 manifest입니다.

포함 내용

• v0.15.1에서 추가한 versioned DogfoodMeasurementRun/Measurement 계약,
  bounded summary, reproducibility envelope, PowerShell dogfood runner와
  contract validator를 유지하면서 release-prep 결과를 실제 API workflow로
  확인했습니다.
• 실제 manifest import/list/get/dashboard workflow를 제공합니다. JSON 파일을
  POST /api/assurance/measurement-runs/import로 검증·저장하고,
  /api/assurance/measurement-runs에서 목록을 조회하며,
  /api/assurance/measurement-runs/{runID}에서 상세 manifest를 조회하고,
  /api/assurance/measurement-runs/dashboard에서 안전한 최신 요약과
  비교 정보를 조회합니다. UI의 파일 선택과 검증 대시보드도 같은 경계를
  사용합니다.
• 저장소 masking 경계를 measurement 전용으로 보강했습니다. run,
  measurement, command identity/reference 필드는 masking 때문에 변하지
  않도록 복원하고, masking 후 JSON을 다시 decode·validate한 뒤에만
  저장합니다. token-shaped ID가 보존되고 자유 텍스트의 secret은 계속
  가려지는 regression test를 추가했습니다.
• safe text 검증은 문자열 앞부분만 확인하지 않고 embedded Windows drive,
  UNC, Unix absolute path token도 거부합니다. go version ... windows/amd64,
  GET /api/health 같은 안전한 version/HTTP command token은 허용합니다.
• measurement 최신 결과가 존재할 때 legacy Assurance empty state가 계속
  보이는 UI 모순을 수정했습니다. measurement load 완료 후 legacy DOM도
  다시 렌더링하며, embedded UI regression test가 이 상태 전환을 확인합니다.

실제 clean dogfood 결과

release-prep를 시작하기 전 clean tree인 commit
3dec04eeffb74bb82b5896a4317b131bff7e124b에서 native Windows PowerShell
7.6 dogfood을 실행했습니다. Run ID는
dogfood-e878541d582343d091bffea3872f382d이며, manifest는 12개 measurement,
overall status pass, required failures none, Go total statement coverage
58.4%를 기록했습니다. commit과 head는 모두 위 SHA이고 dirtyState는
clean입니다. 선택적 server probe는 실행하지 않았으므로 /api/health와
/api/state는 각각 unknown/unavailable 및 0 samples로 기록되었습니다.

재현 명령과 별도 contract 검증 명령은 다음과 같습니다.

pwsh -NoProfile -File .\scripts\measure-dogfood.ps1 -OutputDirectory artifacts\dogfood-v0.15.2
pwsh -NoProfile -File .\scripts\verify-measurement-contract.ps1 -ManifestPath artifacts\dogfood-v0.15.2\dogfood-measurement.json

유지되는 경계

• 릴리즈 산출물은 Windows amd64 portable ZIP과 SHA256SUMS만 제공합니다.
  Windows arm64는 검증용 cross-build일 뿐 release asset이 아니며, Linux나
  arm64 release package는 만들지 않습니다.
• runner와 import 경계는 command output, secret, repository/output absolute
  path를 저장하거나 출력하지 않습니다. unknown/unavailable은 pass가
  아니며 비교 가능한 evidence를 얻지 못했다는 뜻입니다.
• 이번 patch는 aggregate score, 외부 CI authority, mutation runner,
  patch adoption, causal productivity claim을 추가하지 않습니다.

v0.15.1 - Reproducible dogfood measurements

Dev Control Room v0.15.1

이번 patch 릴리즈는 제품 자체의 첫 production dogfood을 반복 가능하게
측정할 수 있는 foundation을 추가합니다. 측정 결과는 품질 점수나 생산성
주장이 아니라, 고정된 검증 명령과 제한된 선택적 관찰을 보존하는 근거
manifest입니다.

포함 내용

• 순수 Go internal/measurement 패키지에 DogfoodMeasurementRun과
  Measurement JSON 계약을 추가했습니다. quality, performance, process,
  runtime 범주와 pass/fail/unknown status, measured/estimated/inferred/
  unavailable provenance, bounded raw samples, min/p50/p95/max, optional
  baseline/delta, 재현성 envelope를 명시합니다.
• percentile 계산은 정렬된 bounded sample의 선형 보간으로 결정론적으로
  계산합니다. 비어 있는 pass evidence, non-finite 값, summary 불일치,
  128개 초과 raw sample, 절대 경로 형태의 identity를 fail-closed로
  거부합니다.
• PowerShell 7.6 scripts/measure-dogfood.ps1가 gofmt, 일반/race Go
  test, vet, module verification, build, embedded UI JavaScript syntax를
  고정 명령으로 측정하고 JSON manifest와 human report를 생성합니다.
  coverage와 loopback /api/health, /api/state latency는 optional이며,
  선택되지 않았거나 사용할 수 없으면 unknown/unavailable로 기록합니다.
• scripts/verify-measurement-contract.ps1가 manifest의 version, status,
  provenance, bounded samples, deterministic summaries, required gate,
  absolute-path 경계를 별도로 확인합니다.
• 측정 계약과 evidence boundary를
  docs/DOGFOOD_MEASUREMENT.md에 기록하고 README 및 handoff에 사용법과
  범위를 연결했습니다.

실제 clean dogfood 결과

커밋 f193287a5749757b0e0e0cc7d37c14bdf153c3d5에서 native Windows
PowerShell 7.6 환경으로 clean worktree dogfood을 실행했습니다. Run ID는
dogfood-be829600397d4f0a841c4aa09b9a52e2이며, 12개 measurement가 생성되고
required gate는 pass, Go total statement coverage는 57.9%였습니다.
선택적 loopback probe는 실행하지 않았으므로 /api/health와 /api/state
metric은 각각 unknown/unavailable/0 samples로 기록되었습니다.

유지되는 경계

• 릴리즈 산출물은 Windows amd64 portable ZIP과 SHA256SUMS만 제공합니다.
  arm64는 검증용 교차 빌드만 수행하며 Linux/arm64 릴리즈 asset은 만들지
  않습니다.
• 이번 foundation은 aggregate score, Prometheus/OpenTelemetry, 외부 CI
  authority, mutation runner, patch adoption, causal productivity claim을
  추가하지 않습니다.
• runner는 native Windows에서 검토된 고정 명령만 실행하며, 명령 output·
  secret·repository/output absolute path를 manifest와 report에 넣지
  않습니다. 외부 서버나 destructive Action을 호출하지 않습니다.

Dev Control Room v0.15.0

Dev Control Room v0.15.0

이번 마이너 릴리즈는 처음 사용하는 사람이 실제 작업을 끝까지 이어갈 수
있도록 사용법 화면을 제품의 실행 흐름에 맞춰 구체화합니다.

포함 내용

• 사용법을 추상적인 개념 설명에서 실제 첫 사용 순서로 바꿨습니다.
  프로젝트 → 진단 → 개선 → 작업 → 검증 → 활동의 화면 이동을 한눈에
  보고, 각 단계에서 누를 것과 완료 기준을 확인할 수 있습니다.
• 제품이 해결하는 범위와 사람이 결정해야 하는 경계를 분리해 설명합니다.
  Git·Worktree와 결정론적 점검은 자동 확인 대상으로, Agent·외부 작업과
  승인은 사람의 판단이 필요한 대상으로 안내합니다.
• 사용법 화면에 화면 연결 지도와 Jenkins·릴리즈·Agent를 위한 별도 경로를
  추가했습니다. 각 안내 항목은 실제 화면으로 이동하는 링크를 가집니다.
• 가이드의 슬라이드 상태를 #guide?slide=N으로 유지하고, 키보드 포커스·
  의미 있는 링크·ARIA 안내 영역을 함께 점검합니다.
• README, 사용자 가이드, handoff 기록과 UI 정적 계약을 현재 흐름에 맞춰
  갱신했습니다.

경계

• 릴리즈 산출물은 Windows amd64 portable ZIP과 SHA256SUMS만 제공합니다.
  arm64는 교차 빌드 검증만 하고 Linux/arm64 릴리즈 asset은 만들지 않습니다.
• 이번 릴리즈는 기존 승인·Action Broker·artifact 무결성 경계를 바꾸지
  않습니다. 사용법 안내는 실행 권한을 추가하지 않습니다.
• 가이드의 예시·설명은 저장된 효과나 비용 집계에 포함되지 않습니다.

Dev Control Room v0.14.0

Dev Control Room v0.14.0

This document records the v0.14.0 preparation scope for the local quality
improvement workflow. The final gate and publication status are intentionally
not recorded here.

Included in this scope

• Quality Objective is a user-owned aggregate with the explicit primary
  lifecycle draft → baseline_pending → ready → running → review → adopted.
  blocked, stale, and rejected are explicit exception paths. Decisions
  are human dispositions applied through the existing revision/CAS boundary;
  adoption requires a fresh improved revalidation on the current HEAD.
• Go coverage is a reviewed native runner using a server-owned absolute .out
  profile, -mod=readonly, a fixed test command, bounded profile parsing, and
  structured Quality Run evidence. A coverage signal is not treated as
  improved unless the runner configuration digest, current HEAD, and intact
  server-owned artifact are all verified; missing, mismatched, failed, or
  unverified evidence remains inconclusive or not improved.
• Quality-tools discovery is a fixed, read-only local view. It performs PATH
  lookup only and does not execute candidates, probe versions, install tools,
  persist a registry, infer an unselected target, or report execution
  readiness from discovery alone. Present candidates remain unverified.
• The UI adds a deterministic QualityHome improvement queue and objective
  detail path, clearer empty/loading/error/retry states, a read-only
  quality-tools diagnostic surface, live diagnostic announcements, and an
  explicitly non-persistent Assurance example view. Example data is excluded
  from storage, cost, and effect totals.

Preserved boundaries

• Release packaging remains Windows amd64-only. No Linux or arm64 release
  asset is produced.
• Artifact policies remain fail-closed: a missing, deleted, out-of-root,
  symlinked, unreadable, or hash-mismatched artifact cannot establish improved
  coverage or permit adoption, retention changes, or restoration as verified
  evidence.
• Approval policies remain fail-closed: Quality Objectives, Quality Runs,
  agents, schedulers, MCP, and read-only discovery cannot grant approval.
  External, production, destructive, and other high-impact Actions still
  require the existing exact-plan, Worktree, Action Broker, and human-approval
  checks.
• No Linux/arm64 asset, generic shell surface, unrestricted file-read tool, or
  new final-gate PASS/release-complete claim is introduced by this preparation.

Dev Control Room v0.13.1

Dev Control Room v0.13.1

Windows amd64 patch release for the local repository control room. This release
carries the v0.13 product-surface work and corrects the last visible spacing
defect in the diagnostics page.

Included

• Diagnostic provider rows keep the state label in a bounded 116–140px column,
  so provider names and recovery actions stay aligned on wide displays.
• Empty diagnostic context slots are no longer reserved, and the required-tool
  health message uses a compact content-sized row.
• The embedded CSS and JavaScript URLs are pinned to v0.13.1 so a running
  browser does not retain the previous patch's layout assets.
• The first-use guide, Explorer-backed Windows folder picker, typed Jenkins MCP
  boundary, evidence-ledger UI, and shared release-version package from v0.13
  remain included.

Preserved boundaries

Loopback-only serving, credential references, masking, Worktree identity,
Action Broker approval, idempotency, and the Windows amd64-only portable release
policy remain unchanged. ARM64 is verification-only, Linux is CI-only, and no
generic shell or unrestricted file-read MCP tool is included.