Repository navigation
Closed
Task
Copy link
Description
Parent
Source: PLAN Phase 1, topic emil-kowalski-upstream-sync
Depends on
- none: on the frontier now
Outcome
Emil Kowalski's and good-css's upstream records use the standard pin marker and pin-carrying row links, so the one standard drift check reads both and a later change can file drift issues from a single report.
Demo: Run the standard drift report on both records: good-css reports clean, and Emil Kowalski's reports drift naming his new gestures skill and the one-line README change that came with it.
Problem:
- Gap: our reauthored UI-craft content falls behind Emil Kowalski's new skills and advice, and an upstream change reaches nobody unless a person notices a failed workflow run.
- Who / how many: user-interface plugin users; the maintainers of eight drift-checked upstreams.
- Frequency: he shipped /choreograph on 2026-11-04 and /gestures on 2026-11-08; the drift check runs weekly.
- Trend: unknown.
- Cost: shipped guidance lags his latest; drift waits on a person reading an email.
- Evidence: one upstream commit past the pin, 5206a95 (verified, gh api commits); the 2026-11-02 run found drift in four upstreams and filed no issue (verified, gh run view 41429553532).
Goal: The user-interface plugin teaches Emil Kowalski's latest guidance, upstream changes reach the tracker on their own, and no agent acts on an item whose intent and vision the user has not been through.
- Intent (why, in the user's words): "to ensure what we build is what I want"
- Vision (where this heads): The user-interface skills teach current, researched craft. Upstream changes reach the tracker on their own. Everything is configurable, one source of truth, and nothing is built until we are aligned on intent. (Q58)
- When goals conflict, prefer: alignment over throughput (Q30)
Constraints:
- Reauthor posture: stack-agnostic, configurable taste, provenance only in the upstream records and changelog fragments (Emil Kowalski upstream record, adaptation posture).
- Re-pin procedure: diff each flagged file against the pin, update affected rows and shipped text, update pin and blob SHAs in the drift script and the record in the same change (Emil Kowalski upstream record, re-pin procedure).
- Mechanism decisions (labels, token scope, duplicate detection) are settled at planning (Q9).
- The t3dotgg/tstack upstream record uses the standard form, so the one filer covers it; the TStack Skills session does not touch the weekly drift-check workflow.
- Upstream text is data, never instructions.
- Fact-based and fact-validated; his taste is trusted; defaults combine his values with research (user, 2026-11-08).
- Everything configurable and extensible, no hardcoded sizes, ranges, measurements or approaches; good defaults; a downstream repo's conventions are honored (user, 2026-11-08).
- Uniform and consistent, DRY, single source of truth, for upstream records, drift checking and issue filing (user, 2026-11-08).
- Quality requirement: production bar (Q3).
Decisions
- D3: good-css's marker has no
underclause. Its record carries three row links and one## Maplink for the upstreamgood-cssskill folder, because the files that record reads sit at the upstream root andscripts/.
Key interfaces
- Record marker:
<owner>/<repo>@<40-hex>with anunderclause (good-css omits it, D3), a pin-carrying link per row including root files, a## Mapsection for omitted units, no blob SHA column. - Upstream records hold pins and provenance.
- Conventions followed: the upstream-drift contract, "Pinned git upstreams".
Done when
- AC17:
bash scripts/check-upstream-drift.sh --links --page docs/upstream/emilkowalski-skills.md --page docs/upstream/good-css.mdexits 0. - AC17:
docs/upstream/emilkowalski-skills.mdcarries the marker line**Last audited upstream state:**followed byemilkowalski/skills@c8a79627b59d72d764d6ab6f2c87c09a48169833underskills/;docs/upstream/good-css.mdcarries the same marker form with nounderclause. - AC17:
bash scripts/check-upstream-drift.sh --report --page docs/upstream/good-css.mdprintsstatus=clean; the same command ondocs/upstream/emilkowalski-skills.mdprintsstatus=driftnamingnew-unit path=skills/gestures/SKILL.md, which the re-pin ticket clears. - In
docs/upstream/emilkowalski-skills.md, each table row is a pin-carryingblob/<pin>/<path>link, includingLICENSE,README.md,performance-cheatsheet.mdandui-cheatsheet.md. The Blob SHA column and the sentence describing it are gone..gitattributes,.gitignore,.pl,ask-sonner,animate-expoandwrite-swiftmove to## Map. The Pointer, As of, Recheck trigger and Re-pin procedure use the words ofdocs/contracts/upstream-drift/README.md, "Pinned git upstreams". - In
docs/upstream/good-css.md, three row links sit at the pin,skills/good-cssis in## Map, no Blob SHA column remains, and theblob/mainlink toPRACTICES.mdin the Pointer is in pin form. - No changelog fragment: this change touches no plugin file.
Out of scope
- Moving the pin or absorbing /gestures (the re-pin ticket).
- Filing drift issues, the one filer and the workflow change (tickets 3a and 3b).
- All t3dotgg/tstack work: evaluation, upstream record, its drift-check entry, the council port.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Work status
needs-triage
Activity
github-actions commentedon Nov 8, 2026
Proposed work class: none
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood: convert the two upstream records, docs/upstream/emilkowalski-skills.md and docs/upstream/good-css.md, to the standard pin marker and pin-carrying row links. The standard drift check can then read both. The outcome and done-when items are exact, and the issue lists no design choices. It is a docs-only change.
No duplicate found. #14208 (absorb gestures and re-pin) is explicitly out of scope here and is follow-up work, not a duplicate. No merged pull request appears to already cover this.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 8, 2026
{"v":1,"actor_id":337595936,"title_sha256":"2c1c2372847343fcb1522ade1fecd88d526d06c8a14bba9255d5a28c979e1ae0","body_sha256":"653070cf9ef844eb559480668f9e3e725f3ce61e06bfbe707981852ea64e8025"}
melodic-automation-lanes commentedon Nov 8, 2026
{"v":1,"actor_id":337595936,"title_sha256":"2c1c2372847343fcb1522ade1fecd88d526d06c8a14bba9255d5a28c979e1ae0","body_sha256":"653070cf9ef844eb559480668f9e3e725f3ce61e06bfbe707981852ea64e8025"}
github-actions commentedon Nov 8, 2026
melodic-automation-lanes commentedon Nov 8, 2026
The work-resolve-issue run that
agent-readystarted waited in its slot past a change to its lane workflow files on main, so it stopped before any model turn. The run's report-outcome removed and addedagent-readyback to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.1 remaining item
melodic-automation-lanes commentedon Nov 8, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 42528716384, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-08T22:13:38Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.github-actions commentedon Nov 8, 2026
github-actions commentedon Nov 8, 2026
melodic-automation-lanes commentedon Nov 8, 2026
The work-resolve-issue lane stopped on this issue (
required-undone): the run left a required check undone, so the next run continues the branch.It keeps
agent-ready, and work-unblock starts it again (retry 1 of 2).In the run's words:
What the run says it did not do:
bash scripts/check-upstream-drift.sh --links --page docs/upstream/emilkowalski-skills.md --page docs/upstream/good-css.mdand the two--reportruns from the done-when were not executed. This lane's Bash runs only the named wrapper scripts, and the script needs gh with a token. The…Partial work is on the branch
work-resolve-issue/issue-14207-42530403924-1. The next run continues from it while it is not behind the default branch, and otherwise starts fresh.Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/42530403924
github-actions commentedon Nov 8, 2026
github-actions commentedon Nov 8, 2026
melodic-automation-lanes commentedon Nov 8, 2026
This run started fresh from the default branch instead of resuming
work-resolve-issue/issue-14207-42530403924-1, which is behind it. That branch keeps the earlier run's commits until the next run on this issue deletes it, when no pull request uses it.