# Changelog

## Score

- CAI 69 → 69 (+0.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.

## Lenses

- Code Health 97 → 96 (-1.5)
- Architecture 97 → 97 (-0.1)
- Maturity 66 → 62 (-3.7)
- Readiness 61 → 61 (+0.0)
- Security 75 → 83 (+7.9)

## Resolved (13)

- Confusingly named duplicate: `Scaffold` (base class for Flask and Blueprint) exposes both `get` and `query` as HTTP method decorators. In standard REST conventions and Flask's own routing, 'GET' is the standard term. 'Query' is non-standard and likely a synonym for 'GET', creating unnecessary cognitive load and potential confusion for developers expecting standard HTTP method names.
- Documentation: no installation or build instructions (docs/quickstart.rst)
- Documentation: no project overview (docs/index.rst)
- Documentation: no usage examples (docs/quickstart.rst)
- Duplicate operation: `errorhandler` (decorator style) and `register_error_handler` (function style) perform the same function of registering an error handler. While decorator vs. function style is a common pattern, having both on the same class without clear distinction in utility (e.g., one being deprecated) can be confusing. More importantly, `errorhandler` returns a decorator, while `register_error_handler` takes the function directly. This is a minor inconsistency in usage pattern but represents the same underlying intent.
- Duplicate operation: `make_response` is exposed both as a method on the `Flask` application instance and as a standalone function in the `helpers` module. This mirrors the `url_for` inconsistency.
- Duplicate operation: `url_for` is exposed both as a method on the `Flask` application instance and as a standalone function in the `helpers` module. While they share the same signature, exposing the same functionality via two different entry points (instance method vs module-level function) creates redundancy and confusion about which one to use.
- No ADRs found
- Off-boarding risk: anonymized user #1
- Rotate the exposed credentials — git history can't be un-committed
- Secret: generic-api-key (docs/config.rst)
- Secret: generic-api-key (docs/config.rst)
- Secret: generic-api-key (docs/tutorial/deploy.rst)

## New (10)

- Edited copy of a member (10 corresponding lines) (src/flask/templating.py)
- Edited copy of a member (21 corresponding lines) (examples/tutorial/flaskr/blog.py)
- Edited copy of a member (25 corresponding lines) (src/flask/app.py)
- Edited copy of a member (7 corresponding lines) (src/flask/app.py)
- High CVE: [GHSA redacted] (examples/celery/requirements.txt)
- Hotspot: src/flask/app.py (src/flask/app.py)
- Medium CVE: [GHSA redacted] (examples/celery/requirements.txt)
- Medium CVE: PYSEC-2026-2151 (examples/celery/requirements.txt)
- No ADRs found (pyproject.toml)
- Off-boarding risk: anonymized user #1

## Changes since last survey

- 4 commits — 4 feature/other, 0 fixes

## By area

- src/flask — 2 commits
- (repo) — 1 commit
- docs/errorhandling.rst — 1 commit

## Notable commits

- change: add `versionchanged` for ctx signature change
- change: add `versionchanged` for ctx signature change (#6176)
- change: fix example typo
- change: werkzeug 3.2 compat
