chore(release): v0.2.0, since new checks are a minor and the ref is a pointer

BADGE-COUNT and README-LANGUAGE are additions, so this is a minor rather than a
patch. The catalog ref still sat on v0.1.1 against a released v0.1.3; bumping it
to v0.2.0 clears that lag in the same move, because a ref points, it does not
queue.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mf1zhujv5QjYuAn1a9HcgW
This commit is contained in:
Kjell Tore Guttormsen 2026-08-04 09:55:21 +02:00
commit 75f2149761
5 changed files with 17 additions and 5 deletions

View file

@ -1,6 +1,6 @@
{
"name": "repo-standard",
"version": "0.1.3",
"version": "0.2.0",
"description": "Per-repo gate for the open/ presentation standard: README first screen, install block, files required by the repo's class, and dead repo references.",
"author": {
"name": "Kjell Tore Guttormsen"

View file

@ -4,7 +4,7 @@ All notable changes to this project are documented here.
Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/);
versioning is [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
## [0.2.0] — 2026-08-04
### Added
@ -37,6 +37,17 @@ count (would fire on 9 of 18 — textbook "suspect the CHECK"); Mermaid source
length and `#gh-dark-mode-only` (zero occurrences, and the instance's actual
limit is not readable via the API, so any threshold would be a guess).
### Changed
- The skill now carries diagram guidance, deliberately as judgement and not as a
check. Mermaid is verified to render on this forge; that is capability, not
justification, and every claim that visuals improve a README was refuted. What
the guidance covers is a diagram that already exists — height, node labels,
the silent degradation past `MERMAID_MAX_SOURCE_CHARACTERS`, and the fact that
`#gh-dark-mode-only` is unavailable below Gitea 1.26.0. The org's own measured
example renders at 1,459 px and wraps node text mid-word while its neighbour
sits at 191 px: rendering and rendering well are separate questions.
## [0.1.3] — 2026-08-03
### Fixed
@ -194,6 +205,7 @@ First release. Covers the checks that a single repository can answer on its own.
- No hook ships in this release. A blocking gate has to be precise enough not to
fail a correct repository first.
[0.2.0]: https://git.fromaitochitta.com/open/repo-standard/src/tag/v0.2.0
[0.1.3]: https://git.fromaitochitta.com/open/repo-standard/src/tag/v0.1.3
[0.1.2]: https://git.fromaitochitta.com/open/repo-standard/src/tag/v0.1.2
[0.1.1]: https://git.fromaitochitta.com/open/repo-standard/src/tag/v0.1.1

View file

@ -10,7 +10,7 @@ checks that surface in one repository and reports what it finds.
*AI-generated: all code produced by Claude Code through dialog-driven development.*
![Version](https://img.shields.io/badge/version-0.1.3-blue)
![Version](https://img.shields.io/badge/version-0.2.0-blue)
![Platform](https://img.shields.io/badge/platform-Claude_Code_Plugin-purple)
![Skills](https://img.shields.io/badge/skills-1-orange)
![License](https://img.shields.io/badge/license-MIT-lightgrey)

View file

@ -1,6 +1,6 @@
{
"name": "repo-standard",
"version": "0.1.3",
"version": "0.2.0",
"private": true,
"type": "module",
"engines": {

View file

@ -12,7 +12,7 @@ description: >-
"fiks install-blokka", "finn døde repo-referanser", "gjør repoet presentabelt".
Trigger when someone is about to release, publish, or hand over a repository
and wants its public surface to hold up.
version: "0.1.3"
version: "0.2.0"
---
# repo-standard — the per-repo gate