Repository navigation
Preserve approved imports during upstream maintenance - #51
Merged
Merged
Conversation
thecolormaroun
changed the title
thecolormaroun
changed the title
thecolormaroun
marked this pull request as ready for review
November 13, 2026 17:35
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
thecolormaroun
added a commit
that referenced
this pull request
Nov 13, 2026
Adds two new skills from emilkowalski/skills at f8ff3b0a1b6edbad62a6cd7fc0d06ef2a6f7e4ab: - emil-gestures (design): drag, swipe, and sheet interactions that track the finger and stay interruptible. - emil-learn-taste (design): turns a user's design corrections into rules in DESIGN.md, a project skill, or a lint check. The importer bumps the whole Emil pin (c8a7962 -> f8ff3b0). The existing Emil skills change only in their pinned-commit lines; their upstream content is unchanged. Counts in docs/skill-architecture.md and README now read 161 capabilities (153 active, design 33). They also pick up stageshow (#53), which never updated them. Cut from 73136f9 (after #51), so the materializer keeps review-animations' retained STANDARDS.md at its original inspected commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Restore maintenance materialization when curated David and Matt imports disappear upstream. Apply the owner-approved retention entries for 13 David skill directories, Matt's merge-conflict skill, and Matt's legacy CONTEXT-FORMAT.md at their existing inspected revisions. Existing approved retentions remain intact; no skill is deleted or rebound to a new source.
The materializer also reports absent upstream directories as upstream_deletion_requires_approval and preserves each retained support file's original inspected commit across subsequent provider advances. Legacy Markdown and per-file Markdown/JSON provenance round-trip, including mixed-origin files; malformed records fail closed. A regression validates every curated retained target against its existing source metadata.
Validation: 79 focused tests passed (materializer, runner and upstream packages), metadata/doctor/bootstrap checks and git diff --check passed, and a fresh independent read-only review returned no findings. Direct materialization checks using the exact audited David and Matt commits pass with the approved rules and produce no replacement bytes for retained targets or the legacy support file.
Retention policy was explicitly approved by the owner on November 9, 2026. Merge, runtime installation/publication, vendor restoration, plugin mutation and cleanup remain outside this change's execution authority. Receipt-bound prepare always uses the exact audited main commit; successful PR-branch checks do not establish canonical workflow success before this draft is integrated.