Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .specfuse/VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.32.0
0.33.0
15 changes: 15 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,21 @@ Entries below cover only work landing from FEAT-2026-0064 onward.

## [Unreleased]

## [0.33.0+umbrella.0.17.0] - 2026-11-14

### Added

- monitoring.yml gains a backlog-stalled check type: a component reports each work queue it keeps in its own data store (outbox or job table) as a BacklogSnapshot event, and the App Insights adapter files one finding per backlog when its oldest pending item passes stall_after, or when no snapshot arrives within the optional silent_after. The emission contract is in design-for-diagnosis.md, and /derive-monitoring proposes a target per discovered backlog or flags a missing emission. (#3576)
- monitor: `dependency-regression` check type. Within `window_after_deploy` after a deployment, a (dependency type, target) pair with at least `min_failures` failed calls (default 5) and 3x its pre-deploy failure rate files one finding per deployment, read from App Insights `AppDependencies` scoped to the role name and app version. Shares the `deploy_signal` block with `http-status-regression`; `/derive-monitoring` proposes it for components with a version stamp and a data store. Failures only: latency is out of scope by decision. (#3577)

### Changed

- Monitoring scope: a component data store is monitored through the component, never directly. The design-for-diagnosis rule and the monitoring schema doc state the boundary, and derive-monitoring audits data-store components for owned signals (data-store-signals) and routes platform health to infrastructure alerting. (#3578)

### Fixed

- `specfuse monitor run` no longer crashes with `TruncatedListingError` once a repo holds 100+ finding issues: the listing limit is raised to 2000, and a filing error is now reported per component instead of aborting the whole run (#3579)

## [0.32.0+umbrella.0.17.0] - 2026-11-03

### Fixed
Expand Down
5 changes: 0 additions & 5 deletions changelog.d/3576-monitoring-yml-gains-a-backlog-stalled-c.md

This file was deleted.

5 changes: 0 additions & 5 deletions changelog.d/3577-monitor-dependency-regression-check-type.md

This file was deleted.

5 changes: 0 additions & 5 deletions changelog.d/3578-monitoring-scope-a-component-data-store.md

This file was deleted.

5 changes: 0 additions & 5 deletions changelog.d/3579-specfuse-monitor-run-no-longer-crashes-w.md

This file was deleted.

2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"

[project]
name = "specfuse-loop"
version = "0.32.0"
version = "0.33.0"
description = "Local-first executor for the Specfuse Plan + Work Unit gate-cycle methodology."
readme = "README.md"
requires-python = ">=3.10"
Expand Down
2 changes: 1 addition & 1 deletion specfuse/loop/data/VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.32.0
0.33.0
2 changes: 1 addition & 1 deletion specfuse/loop/loop.py
Original file line number Diff line number Diff line change
Expand Up @@ -135,7 +135,7 @@
REPO_ROOT = SPECFUSE_DIR.parent
FEATURES_DIR = SPECFUSE_DIR / "features"
VERIFICATION_PATH = SPECFUSE_DIR / "verification.yml"
DRIVER_VERSION = "0.32.0"
DRIVER_VERSION = "0.33.0"
# Oldest scaffold layout this driver can drive. init.sh stamps the scaffold's own
# version into `.specfuse/VERSION`; check_scaffold_version() fails loud at startup if
# the consumer's scaffold is older than this, pointing at `specfuse upgrade`. Bump
Expand Down
Loading