---
name: project-release-authority
description: LexAI releases — the owner tests load-unpacked personally and holds the tag; a v*.*.* tag publishes live to the Chrome Web Store with no manual approval step
metadata:
  type: project
---

The owner does the real-page (load-unpacked) verification himself and reports it back; agents should treat that as the DOM/selection acceptance evidence rather than trying to reproduce it. The `v*.*.*` tag is his to fire.

**Why:** pushing a `v*.*.*` tag runs `deploy-chrome.yml`, which uploads *and publishes* to the Chrome Web Store in the same run — there is no draft/approval gate, and a published CWS version cannot be unpublished in place (only superseded by a higher version). Tags v1.0.1 and v1.0.2 were never created on the remote even though those versions exist in `package.json` history, so remote tag state must be read (`git ls-remote --tags origin`) rather than inferred from `package.json`.

**How to apply:** take a release through bump → gates → merge to `main` → stop. Park the tag as an owner decision in `docs/PROGRESS.md`. Never create a tag without an explicit, specific go. See [[feedback-owner-approval-style]].
