Skip to content

chore(config,docs): cover .pmtiles.png in artifact guard; record #118 learnings#120

Merged
DocGerd merged 1 commit into
developfrom
chore/118-followups
Jul 23, 2026
Merged

chore(config,docs): cover .pmtiles.png in artifact guard; record #118 learnings#120
DocGerd merged 1 commit into
developfrom
chore/118-followups

Conversation

@DocGerd

@DocGerd DocGerd commented Jul 23, 2026

Copy link
Copy Markdown
Owner

Follow-ups from the #118 fix (PR #119), user-requested.

What

  1. .claude/settings.json artifact guard: the PreToolUse deny pattern now also matches *.pmtiles.png. The First-load vector basemap broken: GitHub Pages CDN gzips basemap.pmtiles and range-slices the compressed form (ERR_CONTENT_DECODING_FAILED) #118 rename (basemap.pmtilesbasemap.pmtiles.png) had moved the committed basemap archive out of *.pmtiles coverage, leaving the 27 MB generated binary hand-editable without a prompt. One-line change; the user's local (uncommitted) settings churn is deliberately not included.
  2. CLAUDE.md (two bullets):

Spec check (resolves the "spec still names basemap.pmtiles" flag)

docs/superpowers/specs/ contains no basemap filename references (verified by grep; the only pmtiles mention is a generic route-ordering note in the GPX spec). The old name appears only in dated historical plan documents, which correctly record what was true at the time — deliberately untouched. No spec edit needed.

Refs #118, #119 (no code changes; docs/config only).

🤖 Generated with Claude Code

…learnings

- .claude/settings.json: the PreToolUse artifact-guard deny pattern now also
  matches *.pmtiles.png — the #118 rename (basemap.pmtiles -> basemap.pmtiles.png,
  PR #119) had moved the committed basemap archive out of *.pmtiles coverage,
  leaving the generated binary hand-editable without a prompt.
- CLAUDE.md: document the basemap.pmtiles.png masquerade rationale (Pages CDN
  gzips application/octet-stream at every size and range-slices the compressed
  body; image/png is the only probe-proven exempt type; preflight+Blob fallback
  absorbs future CDN flips) and the stale-PR-head merge-verification law from
  the PR #119 incident (verify head.sha == pushed SHA + check-runs exist for
  that exact SHA before any merge; close/reopen resync fires a duplicate stale
  event whose concurrency clash cancels fresh CI - cancel stale run, then rerun).

Spec check: docs/superpowers/specs/ contains no basemap filename references
(verified) - only dated historical plan documents mention the old name, and
those correctly record what was true at the time; deliberately untouched.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@DocGerd
DocGerd merged commit 9cf5426 into develop Jul 23, 2026
5 checks passed
@DocGerd
DocGerd deleted the chore/118-followups branch July 23, 2026 09:43
@DocGerd DocGerd mentioned this pull request Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant