fix: complete aveproject/ave org-move cleanup - #49
Merged
Conversation
Repo transfer (bawbel/ave -> aveproject/ave) and Pages cutover (ave.bawbel.io -> aveproject.org) landed earlier; this finishes the remaining unblocked cleanup items: - repoint the "AVE Registry" self-citation in all 56 records from the non-neutral api.piranha.bawbel.io to github.com/aveproject/ave, and add the missing citation to records 52-56 for corpus consistency - update schema $id (ave-record-1.1.0 and the unversioned alias) to aveproject.org; leave the 1.0.0 schema's $id untouched as documented permanent/historical - repoint crosswalk $schema/url fields to aveproject.org - sweep README, CONTRIBUTING, GOVERNANCE, LANGUAGE, ARCHITECTURE, PRODUCT, SECURITY, CLAUDE.md and docs/ for bawbel/ave and ave.bawbel.io, leaving bawbel/scanner and api.piranha.bawbel.io untouched (still Bawbel products, not the standard) - correct stale "51 records" counts in CLAUDE.md and PRODUCT.md to 56 - add the org-move checklist/brief docs to the repo All 56 records validated against schema/ave-record-1.1.0.schema.json; rule coverage and fixture checks pass.
Status section and checklist item 13 still said "ready to run" / "not yet run" for the AVE Registry reference repoint after it had already landed (commit 1b640d9). Update both to reflect the confirmed state: all 56 records repointed, zero remaining api.piranha.bawbel.io/records matches.
AVE_ORG_MOVE_CHECKLIST.md, AVE_PROJECT_CLEANUP_TASKS.md, and AVE_V1.1.0_MIGRATION_BRIEF.md were working planning/status docs for this session's cleanup, not meant to live in the repo long-term.
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.
Repo transfer (bawbel/ave -> aveproject/ave) and Pages cutover (ave.bawbel.io -> aveproject.org) landed earlier; this finishes the remaining unblocked cleanup items:
All 56 records validated against schema/ave-record-1.1.0.schema.json; rule coverage and fixture checks pass.
Type of change
Description
AVE record(s)
Checklist
For new AVE record submissions
schema/ave-record-1.1.0.schema.jsonbehavioral_fingerprintis one clear sentence describing what the component DOESindicators_of_compromisehas at least one entry a defender can actually search forowasp_mcpis present with at least one entryaivssblock is complete — required sub-fields: cvss_base, aars, thm, mitigation_factor, aivss_score, spec_versionaivss.aivss_scoreagrees withseverity(CRITICAL >= 9.0, HIGH 7.0–8.9, MEDIUM 4.0–6.9, LOW < 4.0)aivss_scorematchesaivss.aivss_scoreif both are presentreferenceshas at least one citable primary sourceresearcheris setFor updates to existing records
last_updatedis set to today in ISO 8601 formataivss_scorechanges: AARF rationale for each changed factor is in the PR descriptionFor schema changes
schema/ave-record.schema.json(alias) updated to mirror the new canonicalschema/ave-record-1.2.0.schema.json) — prior versioned files stay frozen, never editedFor all PRs
ave_idvalues are immutable — no renumbering1.0.0