Repository navigation
feat(overlay): the scheduled sync can accept skill folders, and --accept says [y] by name - #696
Merged
mboiman merged 2 commits intoNov 18, 2026
Conversation
…n be answered The behavioural gate needs a person's [y] per skill folder, and --yes deliberately does not cover it. In an agent session or a shell without a tty the prompt meets end of input, which counts as no, so a new skill folder stayed withheld however often sync ran. sync, apply and add take --accept UNIT...: the same [y], given by name. It writes the named units whole and leaves every other gated unit withheld. --yes never implies it. A name no gate asked about fails the run (exit 1), and --unattended refuses the option (exit 2). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Signed-off-by: Axel von Dielingen <avd@reinvent-it.de>
…folders The scheduled run withholds every skill folder that has one new file in it, and nobody is there to say [y]. An overlay that ships a new reference or test with most skill changes then falls behind although the job runs every morning: seven skill folders, 59 files, on the instance this comes from. materialize.unattended_accept in the subscription is the consumer's standing answer, per overlay, default none: known a skill folder the consumer already holds a file of all every behavioural unit, a new skill or sub-agent included It never covers a folder that would overwrite a file of the consumer's own or delete one; that folder waits whole, as before. CORE-refusal and the leak gate run on every accepted file. Only --unattended reads it; --yes and an interactive sync are unchanged. The summary line names what was accepted, status shows the setting, an unknown value reads as none. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Signed-off-by: Axel von Dielingen <avd@reinvent-it.de>
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.
Why
The daily overlay job (
sync --unattended) withholds every skill folder that has one new file in it, and no person is there to say[y]. An overlay that ships a new reference or test with most skill changes falls behind although the job runs every morning. Measured on one instance: seven skill folders, 59 files pending, five of them skills that had been accepted long ago.An agent session has the same problem from the other side: without a tty the prompt meets end of input, which counts as no.
What
Two commits, the second builds on the first.
1.
--accept UNIT...(sync, apply, add). The same[y], given by name, for a place where no prompt can be answered. It writes the named units whole and leaves every other gated unit withheld.--yesnever implies it. A name no gate asked about fails the run (exit 1).--unattendedrefuses the option (exit 2).2.
materialize.unattended_acceptin the subscription. The consumer's standing answer for the scheduled run, per overlay:none(default)knownallWhat stays as it is:
--yesand an interactivesyncdo not read the setting.The summary line names what was accepted (
accepted: skills/<name>/),statusshows the setting, and an unknown value reads asnone.Open for review
Hard gate 3 of the overlay skill called the behavioural
[y]non-negotiable. This PR makes it negotiable by an explicit, per-overlay opt-in of the consumer, never by the publisher and never by default. Ifallgoes too far for CORE,knownalone already fixes the measured case of accepted skills falling behind.Tests
bash scripts/tests/test-overlay.sh: 430 passed, 0 failed (new sections 30 and 31).python3 scripts/check-all.py: 27 green.🤖 Generated with Claude Code