Skip to content

feat(user-interface): absorb emil kowalski's gestures skill and re-pin the upstream record #14208

Description

@kyle-sexton

Parent

Source: PLAN Phase 2, topic emil-kowalski-upstream-sync

Depends on

Outcome

The user-interface gesture guidance teaches Emil Kowalski's latest: one rule for driving linked visuals from a single progress value, reduced motion that keeps pointer tracking, no spring while tracking, a fast spring-back, and a team-settable dismiss distance. The upstream record names his gestures skill at his latest commit, and the one-off drift check for his skills no longer runs.

Demo: Read the gesture guidance and find the linked-progress rule and the reduced-motion exception, change the dismiss distance through its one config key, and see the upstream record's link check pass with the one-off drift check gone.

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).

Load-bearing assumptions

Assumption Source Falsifying check Response if false
His newest commit at work time adds no new skill beyond /gestures (AC3) Brief Check: the commit list since 5206a95 names no added skills/<name>/ other than gestures Moderate: pin at the last commit before it; the next drift run files the remainder (AC3)

Decisions

  • Q64: Read his latest commit when this work runs and pin at it, under the AC3 stop below. If any commit past the chain-reviewed 5206a95 exists up to the pin, the PR body lists each commit and the paths it touched, and this ticket applies the do-not-merge label to the PR. The owner removes the label once they have read the list. While it holds, this issue stays open, which keeps tickets 3 and 4 blocked by design.
  • AC3 stop: The re-pin stops before any commit that adds another new skill. The pin is the commit that stop leaves, or his latest when none does. The next drift run files the remainder.
  • D8: This ticket removes the user-interface:write-animation matrix row of the weekly drift workflow together with the script that row calls.
  • D11: One home per absorbed rule. Linked visuals and no-spring-while-tracking go in the gestures reference; "fast" and the distance key go in the drag-to-dismiss behavior; the tracking exception goes in the catalog's reduced-motion section.

Key interfaces

  • Key: animation.gesture.distance_threshold (default 0.4), beside animation.gesture.velocity_threshold. It is a fraction of travel, a number from 0 to 1, not a px value. The plugin's defaults file holds it, the team schema validates it, and the plugin README lists it.
  • Config keys: leave inline in the existing cascade; project tokens beat every layer.
  • Record marker: <owner>/<repo>@<40-hex> with an under clause, a pin-carrying link per row including root files, a ## Map section for omitted units, no blob SHA column. After ticket 1 there is no blob SHA to update: the re-pin updates the pin and the row links in the record, and this ticket retires the script that stored blob SHAs (AC18).
  • Conventions followed: the upstream-drift contract, "Pinned git upstreams"; the Emil Kowalski upstream record; the AI-for-UI course record, which wins any conflict with his repo; plugin option naming (snake_case, _threshold suffix).

Done when

  • AC1: grep -c "linked-progress" plugins/user-interface/reference/animation/gestures.md is at least 2 (the section and its Contents: entry), and the section gives one rule for driving linked visuals from one progress value.
  • AC1: gestures.md direct-manipulation states no spring or transition while tracking; behaviors.md drag-to-dismiss names animation.gesture.distance_threshold and calls the spring-back fast; catalog.md reduced-motion keeps pointer tracking, drops momentum and bounce, and adds no position settle.
  • AC1: No new standalone skill exists under plugins/user-interface/skills/. The record's row for skills/gestures/SKILL.md rejects the 500ms duration and the position settle, and the course record wins any conflict.
  • AC2: docs/upstream/emilkowalski-skills.md has a row for skills/gestures/SKILL.md at the new pin, and bash scripts/check-upstream-drift.sh --links --page docs/upstream/emilkowalski-skills.md exits 0.
  • AC2: bash scripts/check-upstream-drift.sh --report --page docs/upstream/emilkowalski-skills.md prints status=clean, or status=drift naming only commits past the AC3 stop point.
  • AC3: gh api repos/emilkowalski/skills/commits read when this work runs shows no added skills/<name>/ beyond gestures up to the new pin, and the pin is the latest commit that the one-new-skill stop leaves.
  • gh pr view <n> --json labels,body shows do-not-merge and the commit list exactly when commits past 5206a95 exist up to the pin (Q64).
  • AC18: plugins/user-interface/scripts/check-emilkowalski-drift.sh and plugins/user-interface/tests/check-emilkowalski-drift.test.sh are deleted, and grep -rn "check-emilkowalski-drift" .github docs/upstream plugins/user-interface/scripts plugins/user-interface/tests returns no match.
  • AC18: .github/workflows/maintenance-check-upstream-drift.yml has no user-interface:write-animation matrix row (D8), and docs/test-wall-clock-baseline.md has no row for the deleted test.
  • AC24: plugins/user-interface/reference/defaults.yaml sets animation.gesture.distance_threshold: 0.4 with a comment stating its meaning and units; plugins/user-interface/reference/team.schema.json holds it under animation.gesture as a number from 0 to 1; plugins/user-interface/README.md has a config table row; the record's gestures row names the key and its source; the PR body states whether any measured fact or accessibility floor changed his value.
  • AC24: node --test --test-concurrency=4 plugins/user-interface/tests/defaults.test.mjs plugins/user-interface/tests/detect.test.mjs exits 0 with the key added to CONTRACT and to the values and provenance.
  • A .changes/user-interface/<slug>.md fragment with bump: minor exists, made by scripts/new-changelog-fragment.sh user-interface minor, and validates under scripts/check-changelog-fragments.sh.

Out of scope

  • A new standalone gestures skill.
  • The one filer and the weekly workflow change (tickets 3a and 3b).
  • Literal measurements elsewhere in the references (Q51's separate effort).
  • All t3dotgg/tstack work: evaluation, upstream record, its drift-check entry, the council port.

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 8, 2026
  2. github-actions commented on Nov 8, 2026

    @github-actions
    Contributor

    Proposed work class: none

    Size: Medium
    Complexity: Medium
    Uncertainty: Known
    Flags: none
    Blocked by: none

    Understood: absorb Emil Kowalski's gestures guidance into the user-interface references. That means the linked-progress rule, the reduced-motion tracking exception, no spring while tracking, a fast spring-back, and a new animation.gesture.distance_threshold key. The work also re-pins the upstream record and retires the one-off drift script, its test, and its matrix row.

    The body states its outcome, done-when items, key interface and decisions (Q64, AC3 stop, D8, D11) precisely, so I found no open intent question. #14207 is not in the open issue list, so I treat it as no longer blocking. I found no open duplicate. An earlier admission note says a builder session must take it, because it touches a protected workflow file.

    Automated triage. A maintainer reviews it.

  3. added and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 8, 2026
  4. melodic-automation-lanes commented on Nov 8, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane: its body or a criterion names .github/workflows/maintenance-check-upstream-drift.yml, which the issue lane cannot push (patch-protected-path); a builder session takes it. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).

  5. melodic-automation-lanes commented on Nov 9, 2026

    @melodic-automation-lanes
    Contributor

    A blocker of this issue closed after admission parked it at status: confirmed, so work-unblock set its Work status to needs-triage, and the hourly triage sweep sends it back to intake triage.

  6. github-actions commented on Nov 9, 2026

    @github-actions
    Contributor

    The triage sweep dispatched intake triage for this issue (dispatch 2; 2 runs that reach intake, or 6 dispatches, hand it to a maintainer).

  7. added
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 9, 2026
  8. removed
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    Work status

    confirmed

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions