feat(intent): maintainer-requested PR-channel cap (~10 open) + two friction findings - #50
Merged
Conversation
…open PRs Zious11 (via operator, 2026-07-24) asked that concurrent open measured-side PRs stay around 10: the ~25-PR backlog preceding the 2026-07-19/22 drains overloaded his analysis tooling. Encoded as manifest v0.5 maintainer_capacity.pr_channel (soft cap) so §6b governance conditions on it, plus a SKILL §6b rule-6 hook making channel caps a read-per-run contract. Also refreshes observed_windows with 2026-07-23 (the run-17 window — the per-run refresh step §6b already mandates).
…-021 Captured before working around per tooling-friction rule: the check recipe fails wholesale on machines without PyYAML in system python; validation for this session ran via uvx --with pyyaml. Fix shape (uvx in the recipe or probe-and-skip like lint) recorded in the finding, not applied here.
…finding-022 Same key, same config: accepted by 140.82.112.3, rejected by 140.82.114.4 within minutes. Correct response is retry (or HTTPS/443 fallback), not local key/agent/config surgery — recorded to stop future sessions from rewiring ssh chasing a transient.
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
1 participant
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
Zious11 asked (via the operator, 2026-07-24) that we keep concurrent open measured-side PRs to around 10 — the ~25-PR backlog before the 2026-07-19/22 drains overloaded his analysis tooling. That is direct maintainer guidance on the interaction channel itself (B3: maintainer engagement is the compass), and it constrains beadle's own next move: the A4 discharge path calls for shipping SDL fix PRs, and those pushes now need to stagger under the cap rather than land as another batch. Encoding it in the intent manifest puts the constraint where the instrument actually reads it, instead of leaving it as conversation lore that the next session re-violates.
What
targets/vsdd-factory.intent.yaml→ v0.5:maintainer_capacity.pr_channel(max_open_measured_prs: 10, soft cap, provenance noted) +observed_windowsrefreshed with 2026-07-23 (the per-run refresh §6b already mandates — owed from run-17).skills/beadle-triage/SKILL.md§6b rule 6: channel caps declared in the manifest are now an explicit read-per-run contract._kos/findings/finding-021—just checkassumes PyYAML in system python; fails wholesale on clean machines (validated viauvx --with pyyamlinstead; fix shape recorded, not applied)._kos/findings/finding-022— GitHub SSH endpoint-intermittentpublickeydenial; retry, don't rewire local config.Verification
All five YAML manifests validate (
uvx --with pyyaml), including an assertion on the newpr_channelblock and the window refresh. Open measured PRs at capture: 1 (#729) — currently well under the cap.