Revert to 0.14.0, remove internal strategy docs, honest README status, fix ADK tools fail-open#249
Merged
Conversation
…, fix ADK tools fail-open Reconcile the version story and tighten the pre-1.0 posture. Version: revert 1.0.0a1 -> 0.14.0 across pyproject and __init__ and the ~84 files that pin or stamp it (install snippets, .well-known, schema defaults, version-stamped goldens and test assertions, regenerated llms-full.txt). `tool.version`, `cli_version`, and the generated Action pin all derive from __version__, so those moved in lockstep. Rewrite STABILITY.md's migration note as a 0.x continuation (not a new "alpha" line) and turn CHANGELOG "Unreleased" into a dated 0.14.0 section documenting why the 1.0 line was withdrawn: report schema is still 0.28, classifier is still Beta, and no detection-accuracy baseline is published. Classifier stays "4 - Beta", now consistent with the version. Remove internal strategy / GTM material from the public repo: docs/shipgate-strategic-engineering-review.md, docs/decks/ (incl. the VC deck PDF/PPTX), and marketing/. Reconcile referrers: de-link CONTRIBUTING, drop the now-moot decks/marketing excludes from pyproject sdist + ruff, and clean the dead docs/decks rules from .gitignore. NOTE: removed from HEAD only; git history still contains them. README: add a pre-1.0 / beta status banner, and a "here's the failure mode" note after the two-PR demo — real dynamic tool surfaces return insufficient_evidence by design and detection accuracy is still being validated against a labeled corpus. Fix a fail-open in inputs/google_adk.py: a `tools:` value that is present but not a list (templated string, env var, mapping) in an Agent Config silently collapsed to a confident tool_count: 0. It now records a warning plus a dynamic GoogleAdkToolset marker (mirroring the Python entrypoint's dynamic-tools handling), routing to SHIP-ADK-DYNAMIC-TOOLSET-NOT-ENUMERABLE instead of a silent zero. Adds a regression test. Audited every other input parser for the same `else []` shape; the rest are benign sub-field coercions. Full `pytest -n auto -m "not perf"` green; ruff clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Follow-up to the 0.14.0 revert: the version-token sweep replaced `1.0.0a1` but missed the separate "alpha contract" prose, which contradicted the withdrawn 1.0.0-alpha line. - docs/faq.md: "v0.14.0 is the current alpha contract version" -> "current pre-1.0 beta contract version" (it already said "stable across the 0.x series" in the next sentence). - tests/test_public_surface_contract.py: the faq phrase doubles as the version-extraction regex, so update it in lockstep. - skills/agents-shipgate/SKILL.md and adoption-kits/claude-code-skill/ SKILL.md (byte-identical bundled + rendered copies): "current alpha contract line" -> "current 0.x contract line"; refresh the claude-code SKILL.md render-hash snapshot. Full `pytest -n auto -m "not perf"` green; ruff clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reconcile the version story and tighten the pre-1.0 posture. Four related changes:
1.0.0a1→0.14.0, made consistent everywhere. The engine is deterministic and well-built, but a1.0label was indefensible: the report contract is stillreport_schema_version: "0.28", the classifier is still4 - Beta, the last released tag isv0.13.0, and no real-world detection-accuracy baseline is published. Revertedpyproject/__init__and the ~84 files that pin or stamp the version (install snippets,.well-known, schema defaults, 17 version-stamped goldens, 4 test assertions, regeneratedllms-full.txt).tool.version,cli_version, and the generated Action pin all derive from__version__, so they moved in lockstep.STABILITY.md's migration note is rewritten as a0.xcontinuation (not a new "alpha" line);CHANGELOGUnreleasedbecomes a dated0.14.0section documenting why the 1.0 line was withdrawn.docs/shipgate-strategic-engineering-review.md(internal SWOT),docs/decks/(incl. the VC deck PDF/PPTX), andmarketing/. Referrers reconciled (CONTRIBUTING,pyprojectsdist + ruff excludes,.gitignore). Note: removed fromHEADonly — git history still contains them.insufficient_evidenceby design, and detection accuracy is still being validated.inputs/google_adk.py. Atools:value that is present but not a list (templated string, env var, mapping) in an Agent Config silently collapsed to a confidenttool_count: 0. It now records a warning + a dynamicGoogleAdkToolsetmarker (mirroring the Python entrypoint), routing toSHIP-ADK-DYNAMIC-TOOLSET-NOT-ENUMERABLEinstead of a silent zero. Regression test added. Audited every other input parser for the sameelse []shape — the rest are benign sub-field coercions.Type
Verification
CI is authoritative for
python -m ruff check .,python -m compileall -q src tests, andpython -m pytest.Additional local checks run:
ruff check .→ clean;compileallof changed source → OKpytest -n auto -m "not perf"→ green (1 skip), incl. version-stamped goldens, the 5 refreshed render-hash snapshots,test_docs_links,test_public_surface_contract, and the new ADK regression testshipgate --version→Agents Shipgate 0.14.0Release-readiness notes
docs/checks.md— no new check IDs; the ADK fix routes to the existingSHIP-ADK-DYNAMIC-TOOLSET-NOT-ENUMERABLESTABILITY.md— no report-schema change;STABILITY.mdheader + migration note updated for the0.14.0line