Conventional Comments Toolkit 1.0.0-beta.9

1.0.0-beta.9 — September 4, 2026

The extension no longer gets in the way of a pull request's own description, no longer goes quiet on a page that starts out empty, and finally says why when it cannot read your configuration.

✨ Features

• When the configuration cannot be read, the options page now shows why — HTTP 429, a TypeError, a 404 that cannot be told from a refusal — together with the level it came from, instead of the bare word unreachable. The reason stays on your machine: it goes to chrome.storage.local and nowhere else.

🐛 Bug fixes

• A pull request's own description is no longer treated as a review comment. The convention says nothing about it, yet the label toolbar was drawn on it — and under enforce the submit guard applied to its Update button, so a description without a label: prefix could not be saved at all. Badges are gone from it too. Where a future GitHub rendering names things differently, the description simply behaves as it did before, never worse.
• The "Configuration unread" banner no longer appears on every repository. Every configuration read was failing before it left the browser, on public and private repositories alike, with a configuration file and without — so the extension always fell back to its degraded state. Repository-level configuration is readable again.
• A page that had nothing to show no longer stops watching after five seconds. On the Files changed view of a pull request with no thread yet, the first comment posted afterwards got neither badge nor banner until a full reload — and so did coming back to Conversation from another tab of the same pull request. A page that has not moved is still left alone; one that gains a comment, a thread or a published result is rendered again.
• A missing page is no longer read as a hidden one while you are signed in. GitHub masks a private resource as missing, and the extension trusted a page-scraped "private" signal that could be wrong on a public repository. Two independent signals must now agree before a 404 means an unreadable configuration.
• The selector degradation journal is usable again. Visiting a single closed pull request filled all fifty lines with one entry and evicted every real degradation, because the merge button it looks for is legitimately absent there. One line per selector now — and the opt-in telemetry, which inflated for the same reason, with it.

Relevé complet, contraintes et cas limites compris : CHANGELOG.md. Notes de version en français : docs/release-notes-1.x-fr.md.

---

Installation sans chaîne de build

Aucun Node, npm ni Git requis : télécharger l'archive, la décompresser, charger le dossier.

Navigateur	Archive	Comment charger
Chrome, Edge, Chromium	conventional-comments-toolkit-1.0.0-beta.9-chromium.zip	chrome://extensions → Mode développeur → Charger l'extension non empaquetée → le dossier décompressé
Firefox	conventional-comments-toolkit-1.0.0-beta.9-firefox.zip	about:debugging#/runtime/this-firefox → Charger un module temporaire → le manifest.json du dossier décompressé

Décompressez ailleurs que dans le dossier des téléchargements : Chromium relit ce dossier à chaque démarrage, le supprimer désactive l'extension. Sous Firefox, un module temporaire est retiré à la fermeture du navigateur.

Chaque archive contient un INSTALLATION.txt reprenant ces étapes (FR et EN). Guide détaillé : docs/extension-setup-fr.md (EN : docs/extension-setup-en.md).

L'extension démarre en mode assist : elle aide et signale, elle ne bloque jamais l'envoi. La source de vérité reste le compagnon serveur (composant B).

Empreintes SHA-256

9a9b03eba92d484effd84e8d2a86d01292afc0a5fb74ea88ca04479ce09cdf02  conventional-comments-toolkit-1.0.0-beta.9-chromium.zip
7bb7f2e761201d7e81b520f379e68a1759d7476ddd21fba5f3be6e1d6126e158  conventional-comments-toolkit-1.0.0-beta.9-firefox.zip

Construit depuis a0e5647e8b6de5ceb6984e35ad9004c8a863e6b1 — bundle vérifié sans code distant (§10), manifestes MV3 Chromium et Firefox chargeables, suite de tests rejouée.