Skip to content

docs: stop telling readers that status.json fixes itself - #1068

Merged
abrichr merged 1 commit into
mainfrom
docs-correct-status-json-provenance
Jul 28, 2026
Merged

docs: stop telling readers that status.json fixes itself#1068
abrichr merged 1 commit into
mainfrom
docs-correct-status-json-provenance

Conversation

@abrichr

@abrichr abrichr commented Jul 28, 2026

Copy link
Copy Markdown
Member

validate_platform_manifest.py compares this manifest against
https://openadapt.ai/status.json and reports skew as a warning. Both the
docstring and the warning text explained that choice by saying status.json
"regenerates on its own cadence in openadapt-web".

It does not regenerate. It is a hand-edited file. Nothing derives it from PyPI
or from this manifest, and no component release writes back to openadapt-web.
On 2026-07-28 it advertised openadapt-flow 1.24.0 and openadapt 1.10.0 while
PyPI had 1.25.1 and 1.10.1, and this validator had been quietly warning about
exactly that.

The severity is unchanged and deliberately so: status.json lives in another
repository, and a release here must not be blocked by an edit nobody in this
repo can make. What changes is that the message no longer tells the reader the
problem is transient. A warning that explains itself away is a warning nobody
acts on, and that is how the skew survived.

Both texts now say what is actually true, name openadapt-web's own daily guard
(scripts/check_published_version_claims.mjs) as after-the-fact detection rather
than prevention, and name the two files a person has to edit.

No behaviour change. python scripts/validate_platform_manifest.py --strict-status passes with 0 warnings against the current live status.json.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01NyCHrzA1psrKMFfroYbzaM

`validate_platform_manifest.py` compares this manifest against
https://openadapt.ai/status.json and reports skew as a warning. Both the
docstring and the warning text explained that choice by saying status.json
"regenerates on its own cadence in openadapt-web".

It does not regenerate. It is a hand-edited file. Nothing derives it from PyPI
or from this manifest, and no component release writes back to openadapt-web.
On 2026-07-28 it advertised openadapt-flow 1.24.0 and openadapt 1.10.0 while
PyPI had 1.25.1 and 1.10.1, and this validator had been quietly warning about
exactly that.

The severity is unchanged and deliberately so: status.json lives in another
repository, and a release here must not be blocked by an edit nobody in this
repo can make. What changes is that the message no longer tells the reader the
problem is transient. A warning that explains itself away is a warning nobody
acts on, and that is how the skew survived.

Both texts now say what is actually true, name openadapt-web's own daily guard
(scripts/check_published_version_claims.mjs) as after-the-fact detection rather
than prevention, and name the two files a person has to edit.

No behaviour change. `python scripts/validate_platform_manifest.py
--strict-status` passes with 0 warnings against the current live status.json.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NyCHrzA1psrKMFfroYbzaM
@abrichr
abrichr merged commit 3771129 into main Jul 28, 2026
12 checks passed
@abrichr
abrichr deleted the docs-correct-status-json-provenance branch July 28, 2026 02:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant