Add the cpp type and the profile vocabulary to the spec

[ptr727]

Slice 2 of the lint-only language type work (slice 1: the model doc, merged). Vocabulary + schema + validation only - the audit does not consume the new fields yet, so behavior is unchanged.

What

• project-types.json: new cpp lint-only type (.clang-format, style only - the downstream compile does semantic/static analysis); profiles on python (build/lint-only) and csharp (build); minProfile: "build" on the four build-requiring checks (both *.coverage.codecov, python.uvlock.pinned, python.pyright.config). Also splits the pre-existing semicolons in those four asserts (touched lines).
• project-types.schema.json: minProfile on a check, profiles on a type.
• registry/repos.schema.json: a profiles map property.
• validate.py: a declared profile must name one of the repo's types and a profile that type allows.

Design note

Declared profile is a parallel profiles map (types stays a string list), not an object-or-string types entry: audit.py does set(entry.get("types")) and dict.get(t), which crash on an unhashable dict. validate.py cross-checks the map against types, so they cannot drift.

Verification

spec/validate.py OK; both validation branches tested (bad type, bad profile value); spec/audit.py --selftest PASS; JSON valid; no semicolon splices in the diff.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR extends the spec’s type system with a new lint-only cpp type and introduces a “profile” vocabulary (lint-only vs build) that can be declared per repo-type, with schema and validation support. It is part of the ongoing lint-only language type work and is scoped to vocabulary + schema + validation (audit behavior unchanged).

Changes:

• Add cpp as a new lint-only project type in spec/project-types.json.
• Introduce profiles on types and minProfile on checks in the spec schema and type definitions.
• Extend registry schema + spec/validate.py to validate declared repo profiles against repo types and allowed profiles.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
spec/validate.py	Validates profiles declarations in registry entries against repo types and type-allowed profiles.
spec/project-types.schema.json	Adds schema support for per-type profiles and per-check minProfile.
spec/project-types.json	Defines cpp type and adds profile vocabulary to csharp/python plus minProfile on build-only checks.
registry/repos.schema.json	Allows an optional profiles map on repo entries with constrained profile values.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

spec/validate.py:146

• The new profiles validation assumes repo["types"] is a list of strings, but validate.py intentionally runs without JSON-schema validation. If types is accidentally set to a string/object, the current logic will iterate characters or do substring membership checks, producing confusing errors and making the profiles cross-check unreliable. Add a small shape guard for types, and consider validating each profile value is a string for clearer diagnostics.

 # A declared profile must name one of the repo's types and a profile that type allows (spec/type-model.md).
# CI runs no JSON-schema validation, so guard the shape here rather than crash on .items().
profiles_decl = repo.get("profiles", {})
if not isinstance(profiles_decl, dict):
errors.append(f"{name}: profiles must be an object mapping a type to its profile")

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.