obscura-release-logging

name	obscura-release-logging
description	Use when updating Obscura code, docs, GitHub issues, releases, or roadmap state and the work needs to be logged both locally and on GitHub. Keeps DEVLOG, CODEMAP, release notes, issue comments, and prod/dev branch state consistent.

Obscura Release Logging

Use this skill for any Obscura update that changes behavior, release state, public docs, GitHub issues, or roadmap status.

Read First

1. AGENTS.md
2. docs/DEVLOG.md newest entries
3. docs/CODEMAP.md
4. docs/release/current-release-status.md
5. Relevant feature/release docs for the changed area

Local Logging Checklist

• Add a newest-top docs/DEVLOG.md entry with branch, done list, verification, and contract impact.
• Update docs/CODEMAP.md for any added/moved/deleted file or changed module description.
• Update release docs when package version, release links, checksums, signing status, or public website copy changes.
• Update roadmap/docs when scope, priority, or acceptance criteria change.
• Do not commit release binaries, media, SQLite files, .env, or secrets.

GitHub Logging Checklist

• If the change touches an open GitHub issue, comment with:
  • what shipped;
  • commit or release version if available;
  • remaining work;
  • verification run.
• If new work is discovered, create or update a GitHub issue instead of burying it in chat.
• For releases, publish immutable versioned artifacts and keep latest aliases only for the approved current release.
• GitHub Release notes must use absolute links to prod-branch docs, not local relative links that break on release pages.

Branch And Version Rules

• Feature work happens on a short-lived branch, then dev.
• prod is the public release branch.
• Do not overwrite released tags or versioned artifacts.
• If a released EXE is wrong, publish a new prerelease version.
• Keep unsigned-alpha warnings visible until Authenticode signing is real and verified.

Verification

Run the smallest relevant checks first, then scale with risk:

• Docs-only: git diff --check.
• Type/code changes: npm run typecheck.
• Backend/media/OpenRouter changes: focused Vitest files.
• Release changes: npm run dist:win, checksums, signature status, and latest download URL verification.