Push the FC show-art spec: it exists only on an unpushed local branch

[schmug]

Task

The Frontier Commits ASCII commit-rail show-art design exists only as three docs-only commits on an unpushed local branch in /Users/cory/portfolio. One git branch -D loses it. Push the branch (or land the docs) so the design survives outside one working copy.

Context

Filed by concern triage from https://github.com/schmug/agent-notes/issues/18 (session 4ac4cff5-dd94-4c24-8183-e3219bc58a46, 2026-09-02). Verified still unpushed on 2026-09-07: the local branch claude/ascii-git-history-89a430 is at d1d16f6 ("docs: name this repo correctly in the show-art spec"), and git ls-remote --heads origin claude/ascii-git-history-89a430 returns nothing.

The cover work it describes has since shipped in schmug/clodcast (_cover_commit_rail), so the spec is now documentation of a live design rather than a proposal — which makes losing it worse, not better.

Reproduction

1. git -C /Users/cory/portfolio branch --list 'claude/ascii-git-history-89a430' -vv → exists at d1d16f6, no upstream.
2. git -C /Users/cory/portfolio ls-remote --heads origin claude/ascii-git-history-89a430 → empty.

Expected: design docs live on the remote.
Actual: they live in one working copy.

Pointers

• Branch: claude/ascii-git-history-89a430 in /Users/cory/portfolio (remote git@github.com:schmug/cortech.online.git), three docs-only commits, head d1d16f6.
• docs/superpowers/specs/2026-08-24-fc-show-art-design.md — the spec.
• docs/superpowers/plans/2026-08-24-fc-show-art.md — the plan.
• The implementation that shipped from it: _cover_commit_rail in skills/daily-podcast/render.py in schmug/clodcast.
• Source concern: https://github.com/schmug/agent-notes/issues/18

Constraints

• Docs-only — do not let this turn into a code change.
• Check the branch still exists before doing anything; if it is already gone, say so and close, rather than reconstructing the spec from memory.
• Per ~/.claude/CLAUDE.md §"The issue → PR loop", land it as a PR rather than pushing to main.

Acceptance criteria

• The three commits are on origin, either as the pushed branch or merged via PR.
• The spec and plan files are reachable from the remote, verified with gh api or git ls-remote.
• The spec's description of the commit-rail cover matches what actually shipped in schmug/clodcast, or the gap is noted in the PR.

Out of scope

Any change to the cover implementation, and #193 (the Spotify feed submission).

Reasoning guidance

Prioritize responding quickly rather than thinking deeply. This is a push-or-PR of existing commits, not authorship.