Bridge the CODESTYLE Python profiles to build/lint-only - #445
Merged
Conversation
The type model declares a Python profile as build or lint-only, with Project/Scripts as the structural pyproject shapes. Name each shape's declared profile in CODESTYLE so the vocabulary matches project-types.json: the Project shape is the build profile, the Scripts shape is the lint-only profile. Also split the pre-existing semicolon in the Project bullet. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Aligns the Python profile vocabulary in CODESTYLE.md with the profile names used by the type model (build / lint-only), while keeping “Project” / “Scripts” as the structural pyproject.toml shapes the audit validates.
Changes:
- Updates the “Two profiles” description to name the declared profiles as
buildandlint-only. - Clarifies that the “Project” shape corresponds to the
buildprofile and “Scripts” corresponds tolint-only. - Replaces a semicolon splice in the Project bullet with two sentences.
Uh oh!
There was an error while loading. Please reload this page.
ptr727 added a commit
that referenced
this pull request
Jul 25, 2026
#446) ## Promote develop to main Three doc/spec-only changes (no code path, no release): - **#443** - backlog: standardize `OPERATIONS.md` as the extraction target for operational content, and add a canonical clang-format config for the `cpp` type. - **#444** - name the post-push review race in the merge gate (AGENTS.md + copilot-instructions): a push turns checks green before the re-review lands, so confirm a review on the current head SHA before reading merge-state. - **#445** - bridge the CODESTYLE Python profiles (Project/Scripts) to the declared `build`/`lint-only` names. ## Verification `spec/validate.py` OK; `spec/audit.py --selftest` PASS. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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 freeto 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.
The tracked follow-up to the type-model work: CODESTYLE described the two Python profiles as Project/Scripts, while project-types.json now names the declared profiles
build/lint-only(with Project/Scripts as the structural pyproject shapes). Bridge them - each shape bullet now names its declared profile (Project =build, Scripts =lint-only) - so the vocabulary is consistent across the two docs. Also splits a pre-existing semicolon in the Project bullet.Carried doc (intent), re-vendors fleet-wide.
spec/validate.pyOK.🤖 Generated with Claude Code