Repository quality standard: address gaps from 2026-09-17 conformance assessment

[trsdn]

Context

Canonical baseline: trsdn Repository Quality Standard (v1.11.1, 2026-09-02)

A fresh assessment on 2026-09-17 (after closing #1) found the Baseline, Public Repositories, and Software Repositories sections in good shape — README, licensing, community files, CI, branch protection, Dependabot, and workflow security (pinned actions, scoped permissions, no untrusted-PR secret exposure) all pass. The gaps below are what's left, bundled into one issue since most are small or share a root cause.

Update (2026-09-17): findings 2–8 are resolved in #9 (merge pending). See docs/self-assessment.md on that branch for the full per-criterion result. Only finding 1 (release automation) remains open here.

Findings

1. No release automation (R01–R08) — still open

Tags exist (v1.0.0, v1.0.1, v1.1.0) but gh release list is empty — no GitHub Releases, no release notes, no automated artifact build. The actual signed/notarized DMG pipeline lives in trsdn/macos-notarization-broker, whose OpenPromptr profile is still stale per #7. This overlaps with #7 — resolving the broker profile and adding a release workflow here closes both. Not attempted in #9: it needs a reviewed change in that other repo plus Apple Developer credentials this session had no access to.

2. Product Identity gaps (I02, I04, I06) — resolved in #9

Version is now derived from the git tag/commit count at build time (with a fallback if the tag is malformed), the repo/issue-tracker URL is embedded in the bundle, and the About panel plus a --version flag show both.

3. No AGENTS.md (G01–G08) — resolved in #9

4. Missing conformance record and topic (B11, B12) — resolved in #9

.github/conformance.yml and docs/self-assessment.md added; trsdn-standard topic added.

5. Accessibility undocumented and largely unverified (X01, X02, X03, X05) — resolved in #9

Accessibility labels added to icon-only/hidden-label controls, the color-only login-item status line now also carries an icon, and a README section states what's verified (code review) versus not (no end-to-end VoiceOver pass). Note for whoever picks up #4: its proposed green/red-only status light would fail X03 as specced — pair it with an icon or shape change, not color alone.

6. Minor language-surface inconsistency (L07) — resolved in #9

Issues #4 and #6 translated to English; .gitignore comment fixed.

7. No linter/formatter in CI (S03) — resolved in #9

Adopted swift format (built into the toolchain, no new dependency) as a CI gate, after a one-time reformat.

8. Published Site profile applies and is unmet (W01–W08) — resolved in #9

GitHub Pages landing page added at docs/index.html, vendoring Instrument Workshop v1.5.1 from trsdn/design-system. Pages is enabled and the repo homepage is set; will be live at https://trsdn.github.io/OpenPromptr/ once #9 merges.

Remaining minor gaps, not tracked separately

• B05: no single documented "validate everything" command combining build + test + lint + bundle check (documented as separate commands in README/AGENTS.md).
• I03: no license identifier embedded in the app bundle itself (only in the repository's LICENSE file).
• L03: no explicit "English-only, no localization planned" statement.
• P08/P09: badge convention and self-hosted repo-activity visualization not fully verified against the .github repo's specific conventions.
• R01/R02: no formal versioning/compatibility policy document beyond "tags are semver, see CHANGELOG."

Out of scope

Documentation (T) sections don't apply — this repo's primary product is the app itself, not documentation. Deployable (D) and Archived (A) also don't apply.

Acceptance criteria

• Each numbered finding above is either resolved with evidence, or explicitly deferred/declined with a recorded reason.
• A conformance record exists after remediation, dated and versioned against the standard.

[trsdn]

Update (2026-09-17): progress on the R01–R08 gap via #7 — the broker profile is fixed (trsdn/macos-notarization-broker#49) and AppUpdater is integrated (#10), both merged. R03–R08 stay fail until an actual signed release is cut through the broker; tracked in #7.

[trsdn]

Update (2026-09-17): v1.2.0 is published — https://github.com/trsdn/OpenPromptr/releases/tag/v1.2.0. Signed, notarized, verified.

R03–R08 (release automation) are now real, not aspirational: a tag produces installable, notarized artifacts through automation (R03), the AppUpdater-required OpenPromptr-{version}.dmg naming is in place (R04), the build is smoke-tested via the broker's own preflight/validate_app_tree (R05), and release notes come from the CHANGELOG entry (R06) — though not yet automatically enforced from it (R07 stays a gap; nothing currently fails a release if the CHANGELOG entry is missing). R08 (provenance) is covered: the broker's provenance.json is uploaded as a release asset and records the source commit, tag, and build identity.

Updating .github/conformance.yml/docs/self-assessment.md to reflect this is a small follow-up, not done in this comment.

[trsdn]

Update (2026-09-17): R07 done — trsdn/macos-notarization-broker#53 makes release-notes-from-CHANGELOG an enforced gate, not just a documented habit: `--publish` fetches `CHANGELOG.md` at the tag and refuses to publish if the entry for that version is missing, empty, or still sitting under `[Unreleased]`. Mandatory for every app on that broker, not just this one.

`.github/conformance.yml`/`docs/self-assessment.md` updated to match. That was the last open item from the 2026-09-17 assessment — closing.