Skip to content

chore(sync): accept reviewed skills update at 352eaf7 as 0.1.0-canary.7 - #23

Merged
bntvllnt merged 1 commit into
mainfrom
chore/sync-reviewed-skills-352eaf7
Oct 30, 2026
Merged

bntvllnt merged 1 commit into
mainfrom
chore/sync-reviewed-skills-352eaf7

Conversation

@bntvllnt

Copy link
Copy Markdown
Contributor

Authorized sensitive baseline update

The repo owner authorized this follow-up. Accept vllnt/skills main at 352eaf7b167a6761161415711ef9d55db26d91d6 through this separate protected PR, as in #9, without changing the automatic sensitivity policy.

  • Pin moves from 472c216f2f043f0add1f83540cc46ea53d20a7cd (6 skills commits, 109 files, all reviewed through skills PRs).
  • Bump distribution 0.1.0-canary.6 to 0.1.0-canary.7.
  • Regenerate all three hosts with scripts/sync.py; no generated file was edited by hand.
  • Includes the published @vllnt/* package defaults annex, new direct improvement, session-refocusing and full-environment PR testing workflows, and refreshed quality protocols and principles copies.
  • No updater, generator, workflow, permission or branch-protection changes. Held-branch cleanup is not part of this PR.

Verification

  • 38 unit tests pass; sync.py --check matches all 551 files both offline (--source local skills clone) and over the public network; git diff --check passes.
  • Privacy guard and its tests pass locally; gitleaks over full history finds nothing.
  • Only upstream.lock.json, VERSION, CHANGELOG.md and generated plugins/** change.
  • After the protected merge, trigger the hosted updater and record whether it still holds.

Pin vllnt/skills main 352eaf7b167a6761161415711ef9d55db26d91d6 and regenerate all three hosts with scripts/sync.py. The range changes sensitive paths, so it goes through this protected PR instead of the updater.
@bntvllnt bntvllnt self-assigned this Oct 30, 2026
@bntvllnt
bntvllnt merged commit 284e188 into main Oct 30, 2026
4 of 7 checks passed
@bntvllnt
bntvllnt deleted the chore/sync-reviewed-skills-352eaf7 branch October 30, 2026 23:21
bntvllnt added a commit that referenced this pull request Oct 30, 2026
….8 (#25)

## Authorized sensitive baseline update
The repo owner asked for the stack pin to follow the skills
package-owner answers (vllnt/skills#28). Accept source
`7483dd4dfd8502fd2db376c13e44fa0cbc464161` through this separate
protected PR, as in #9 and #23, without changing the automatic
sensitivity policy.

- Pin moves from `352eaf7b167a6761161415711ef9d55db26d91d6` (1 skills
commit).
- Bump distribution `0.1.0-canary.7` to `0.1.0-canary.8`.
- Regenerate all three hosts with `scripts/sync.py`; no generated file
was edited by hand.
- Content: `@vllnt/convex-api-keys`, `@vllnt/logger`, `@vllnt/analytics`
defaults; `ui-core`/`ui-native` experimental opt-in; `dig` not yet
default.
- No updater, generator, workflow, permission or branch-protection
changes.

## Verification
- 38 unit tests pass; `sync.py --check` matches all 551 files both
offline and over the public network; `git diff --check` passes; gitleaks
over full history finds nothing.
- Only `upstream.lock.json`, `VERSION`, `CHANGELOG.md` and generated
`plugins/**` change.
- Privacy Guard is red on this PR for the same reason it is red on
`main`: the `PRIVACY_DENYLIST_EXTRA` secret has patterns `git grep -E`
rejects (see #24). It fails before scanning content.
bntvllnt added a commit that referenced this pull request Nov 4, 2026
….9 (#27)

## Reviewed sensitive baseline update
Accept skills release v0.2.0
(`06365b10b42d1c56308b946187d51ccf1efa7d33`) through a separate
protected PR, as in #23 and #25. The automatic updater holds this range,
so it is accepted here without changing the sensitivity policy.

- Pin moves from `7483dd4dfd8502fd2db376c13e44fa0cbc464161`;
distribution `0.1.0-canary.8` to `0.1.0-canary.9`.
- Regenerated all three hosts with `scripts/sync.py`; no generated file
edited by hand. Only `upstream.lock.json`, `VERSION`, `CHANGELOG.md` and
`plugins/**` change.

## Verification
- 38 unit tests pass; `sync.py --check` matches all 611 files.
- Denylist grep and gitleaks find nothing.
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