ci(release-notes): ignore CI-generated prompt/context; remove tracked files

These files are produced and consumed only by the release workflow. Keeping them untracked avoids stale content and reduces repo noise.

.gitignore

@@ -133,3 +133,7 @@ branches/
 .code/
 
 # trigger: test non-notes change (no [skip ci])
+
+# release notes (generated by CI)
+release-notes/prompt.expanded.txt
+release-notes/context.md

release-notes/context.md

@@ -1,5 +0,0 @@
-# Commit log (v0.2.82..HEAD)
-* 3ba329bf chore(release): 0.2.83 [skip ci] (GitHub Action)
-* 00ffb316 fix(apply_patch/embedded): replace fragile tree-sitter query with robust heredoc scanner; prevent panic and gracefully degrade (James Peter)
-* 722fb439 feat(tui/exec): use UI-themed syntect for JSON stdout; clear ANSI BG so output inherits theme background (James Peter)
-* ac328824 feat(tui/exec): theme-aware JSON preview in Run output; strip ANSI backgrounds and use UI-matched JSON highlighting; avoid white bg from jq -C (James Peter)

release-notes/prompt.expanded.txt

@@ -1,59 +0,0 @@
-You are Code running headless in CI to prepare a new release.
-
-Inputs
-- Version: v0.2.83
-- Date (UTC): 2025-09-07
-- Previous tag: v0.2.82
-- Commit range: v0.2.82..HEAD
-- Working directory: repo root (CHANGELOG.md lives at top-level)
-
-Primary Tasks
-1) Update CHANGELOG.md with a new entry for this version using the EXACT house style below.
-2) Generate GitHub release notes at release-notes/RELEASE_NOTES.md (concise, user‑facing), derived from the same changes.
-
-CHANGELOG.md House Style (strict)
-- File header stays as-is ("Changelog"). Do not rewrite older sections.
-- Insert the new section at the top (above previous versions), with this header format exactly:
-  ## [0.2.83] - 2025-09-07
-- Include 2–5 bullets (no more, no fewer), each a single line, focusing on user-visible features, fixes, UX, performance, or stability.
-- Keep bullets concise and scannable; avoid long prose. Use present tense.
-- When helpful, start bullets with a short scope label like "TUI:", "CLI:", or "Core:".
-- At the end of each bullet, include abbreviated commit SHA(s) in parentheses, using 7–8 hex chars, comma‑separated when multiple, like: (abc1234, def5678).
-- Map changes from the git commit log in v0.2.82..HEAD; ignore pure chores/merges unless user‑visible.
-- Do NOT add links, tables, code blocks, or subheadings. Do NOT include PR author attributions in the changelog.
-- Do NOT add any extra headers inside the changelog entry; only bullets under the version header.
-- Idempotent: if a section for 0.2.83 already exists, replace only that section’s body with the newly generated bullets and keep the header intact.
-
-Release Notes (release-notes/RELEASE_NOTES.md)
-- Write exactly these sections in order; include the optional Thanks section only when applicable:
-  1) Title: ## @just-every/code v0.2.83
-  2) One brief intro sentence (1–2 lines max).
-  3) Section header: ### Changes
-     - The same 2–5 bullets as in the changelog (you may omit SHAs).
-  4) Section header: ### Install
-     Code block with exactly:
-     npm install -g @just-every/code@latest
-     code
-  5) Optional section header: ### Thanks
-     - Include ONE line like: "Thanks to @alice and @bob for contributions!"
-     - Only include if at least one merged PR in v0.2.82..HEAD is authored by an external contributor.
-     - External contributors are any GitHub users other than: @zemaj, @andrej-griniuk, and NOT upstream contributors.
-     - Treat a username as upstream if it matches the regex /-oai$/i, or clearly belongs to the upstream org (e.g., OpenAI maintainers). Exclude such users from Thanks.
-     - Derive usernames from merge commits, Co-authored-by trailers, or PR references in commit messages. Deduplicate and prefer "@username" form.
-- Keep notes concise; no walls of text. Do not add any other sections beyond the optional Thanks.
-- Optional final line (only if a previous tag exists):
-  Compare: https://github.com/just-every/code/compare/v0.2.82...v0.2.83
-
-Rules
-- Use the provided git log as source of truth; summarize responsibly.
-- Explore codebase directly if commit messages are unclear or need additional context.
-- Keep formatting minimal (headers + list bullets). No emojis ever! Basic markdown only.
-- Never reorder older versions. Only touch the section for v0.2.83.
-- After writing files, stage and commit with message: docs(changelog): update for v0.2.83 [skip ci]
-
-Context (git log excerpt follows):
-# Commit log (v0.2.82..HEAD)
-* 3ba329bf chore(release): 0.2.83 [skip ci] (GitHub Action)
-* 00ffb316 fix(apply_patch/embedded): replace fragile tree-sitter query with robust heredoc scanner; prevent panic and gracefully degrade (James Peter)
-* 722fb439 feat(tui/exec): use UI-themed syntect for JSON stdout; clear ANSI BG so output inherits theme background (James Peter)
-* ac328824 feat(tui/exec): theme-aware JSON preview in Run output; strip ANSI backgrounds and use UI-matched JSON highlighting; avoid white bg from jq -C (James Peter)