audit: 360° maturity audit ahead of v0.2.0 — release-readiness findings#12
Merged
Merged
Conversation
Full-tree audit after the Python-implementation removal. Code, tests, templates, and the knowledge layer are clean; findings concentrate in release metadata: stale version strings (CITATION.cff, README BibTeX, install manifest), the still-unimplemented approved release-check spec, a v0.1.0-hardcoded release checklist, one stale CI step name, and the CodeQL default setup still analyzing the removed Python (red on main). Report is [inferred] per provenance rules — human audits before acting. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Sk86kqPkLWRHj1jdy1nbWA
There was a problem hiding this comment.
Pull request overview
Adds an agent-drafted, provenance-marked (“[inferred]”) release-readiness/maturity audit report ahead of v0.2.0, focusing on post–Python-removal cleanup items that sit outside the code/test surface (release metadata/version strings, checklist/spec gaps, and a GitHub CodeQL setting).
Changes:
- Introduces a new pre-v0.2.0 “360° Codebase Maturity Audit” report capturing pass/fail signals and release-blocking findings.
- Documents concrete remediation items (CodeQL language detection, version string sync locations, unimplemented
release-checkspec, and stale CI checklist wording). - Proposes an ordered sequence for release prep actions.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -0,0 +1,89 @@ | |||
| <!-- Copyright (c) 2026 Kunal Suri (CEA LIST). All rights reserved. --> | |||
| coverage report, cli-docs-sync. None of its touch list exists yet — no | ||
| `test/release-check.mjs`, no `release-check` npm script, no workflow, no checklist | ||
| step. Either implement it before tagging (recommended — it is small and Node-only) | ||
| or run its §"The checks" table by hand for this release. |
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.
Full-tree audit after the Python-implementation removal. Code, tests,
templates, and the knowledge layer are clean; findings concentrate in
release metadata: stale version strings (CITATION.cff, README BibTeX,
install manifest), the still-unimplemented approved release-check spec,
a v0.1.0-hardcoded release checklist, one stale CI step name, and the
CodeQL default setup still analyzing the removed Python (red on main).
Report is [inferred] per provenance rules — human audits before acting.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01Sk86kqPkLWRHj1jdy1nbWA