skills-staging: session-derived campaign-ops skill library (2026-07-30)

skills-staging/2026-07-30-campaign-ops/MANIFEST.md

@@ -0,0 +1,89 @@
+# MANIFEST — campaign-ops library (2026-07-30)
+
+Project skill library distilled from the 2026-07-29/30 contributor-PR
+campaign session (transcript: `chat-history.md`, local untracked file;
+public session id `session_01WMbbZQ8ZMMsNRGyV2nvJR8`, stamped in the
+session-authored commits' trailers — e.g. `f529014`; the
+GitHub-generated merge commits carry no trailer). Staged, NOT
+installed: nothing under `skills-staging/` auto-loads. Every
+repo-facing claim was re-verified against the repository on
+2026-07-30; what could not be verified is in `UNCERTAINTY.md`, not in
+the skills.
+
+Covenant scope: the README House covenant's probe/marker regime
+governs the pack roots (`skills/`, `design-pack/skills/`). This staged
+library ships under the retiring-architect MANIFEST/UNCERTAINTY regime
+instead — its rules are verified operating records, not covenant-bound
+pack doctrine, and this delivery is not precedent for shipping pack
+rules without markers.
+
+Delivery note: `skills-staging/` is gitignored by owner decision
+(`92314a6`). This library is delivered by explicit force-add on the
+owner's instruction for this delivery only; `.gitignore` itself is
+untouched. Once tracked, these files behave like any tracked file.
+
+One line per skill — loading condition ← session evidence ← repo
+evidence ← verification status:
+
+- **contribution-gate-playbook** — contributor PRs open + owner ask to
+  review/integrate/merge, or a live combined-*/integrate-* branch ←
+  the session's three campaigns end to end ← PR #90/#93/#97 bodies,
+  merge commits `a148180`/`92077a7`/`79ca49c`, `gh pr list/checks`,
+  reviewDecision fields, #91 createdAt vs #90 mergedAt, commits
+  `f529014`/`814d116` ← **verified** (cadence wording
+  partially-verified: UNCERTAINTY 2; comments: UNCERTAINTY 7).
+- **gate-adjudication-and-folds** — a lens verdict landed and needs
+  fold/reject/stop; opposite-fix convergence; non-converging lens;
+  runtime-semantics finding ← r1–r11 fold/reject decisions, the #91
+  precedence adjudication, the #96 execution chain ← commits
+  `6fa6154`/`5fa241b`/`83a038d`/`1560b97`, PR #90/#93/#97 bodies,
+  #91/#96 evaluation comments, cross-model-review §§3–4 ←
+  **verified** (the rejection specifics, the r8 pre-declaration, and
+  the fold-introduced attribution are transcript-recorded and labeled
+  so in place; the `→` count was re-run in-repo 2026-07-30).
+- **doctrine-change-conventions** — editing rule text in
+  skills/*/SKILL.md heading to commit/merge; Provenance work; a rule
+  with no probe ← integration fixes, covenant handling, width/glyph
+  rejections, no-bump observation ← README House covenant paragraph,
+  issue #92 body, `.github/checks.py` (read in full: no width check;
+  sweep scope), `git tag -l`, version badge lines, `32c6929`,
+  `f529014`/`814d116` ← **verified**.
+- **repo-boundaries-and-sync** — about to stage/commit; post-merge
+  sync; unexpected diff-loop output; untracked file at repo root ←
+  the session's staging discipline and closing privacy flag ←
+  `.gitignore` + `git check-ignore`, `git ls-files` top-level,
+  `92314a6` message, live-copy diffs run 2026-07-30, README
+  Maintainer Notes, evaluation comments ← **verified**
+  (no-owner-quotes directive is session/memory-recorded, corroborated
+  by the read comments' shape; skill-vetting install intent:
+  UNCERTAINTY 4).
+- **failure-archaeology** — about to hand-roll a CI wait, ship
+  runtime-semantics prose, adopt/delete leftover branches, or re-open
+  settled items ← the session's dead ends and residue ← same commits
+  and bodies as above plus `git branch -vv` and
+  `git branch --merged main` observed 2026-07-30 ← **verified**
+  (entry 1's loop internals are transcript-only — the loop never
+  landed anywhere; the entry carries that label in place).
+
+Claims rejected or downgraded during verification (full list with
+evidence in `UNCERTAINTY.md`):
+
+- "bump the version every substantive PR" (2026-07-12-era rule) →
+  **historically-valid**; contradicted by observed practice #84–#97
+  (0.1.16 unchanged; tags end at alpha-0.1.2).
+- The 2026-07 reviewer lineup recorded in the older local library
+  (gpt-5.5 xhigh + grok-4.5 max) → **historically-valid**; the
+  campaign lineup differs and is itself date-stamped volatile.
+- Session-memory phrase "evals/round4 … COMMITTED" → not supported by
+  the repo (`evals/` is gitignored, zero tracked files); treated as
+  loose wording, recorded in UNCERTAINTY 8.
+- Installed-copies "cmp-verified @ merge SHA" → **verified with an
+  exception the session itself disclosed**: `skill-vetting` absent
+  from both installs (expected state; UNCERTAINTY 4).
+
+Review status: three fresh-context reviews (factual / doctrine /
+usability) ran 2026-07-30 over these files; every BLOCKING and
+IMPORTANT finding was applied in place before delivery, and the
+dispositions are summarized in the delivering PR's description (the
+PR that adds this directory). Unresolved and evidence-dependent items
+live in `UNCERTAINTY.md`.

skills-staging/2026-07-30-campaign-ops/START-HERE.md

@@ -0,0 +1,83 @@
+# START HERE — campaign-ops library (2026-07-30)
+
+What this library is: the distillation of the 2026-07-29/30 maintainer
+session that integrated contributor PRs #85–#89, #91, and #94–#96 into
+main through three combined gates — PR #90 (merge `a148180`), PR #93
+(`92077a7`), PR #97 (`79ca49c`) — and opened the probe-debt tracker,
+issue #92. The engineering core is not the doctrine content those PRs
+carried; it is operating the contributor-PR pipeline (combined branch →
+tri-lens cross-model gate → owner-authorized merge → post-merge duties)
+without breaking the house covenant, the privacy boundaries, or the
+published-record conventions.
+
+Authored 2026-07-30 by the retiring architect from the session
+transcript (`chat-history.md`, a local untracked file at the repo root)
+with every repo-facing claim re-verified against the repository on
+2026-07-30. Companion files: `MANIFEST.md` (per-skill evidence),
+`UNCERTAINTY.md` (everything NOT settled — read it before trusting a
+claim near its topics).
+
+## Canonical-source map (who wins on disagreement)
+
+| Topic                     | Canonical source                        |
+|---------------------------|-----------------------------------------|
+| Cross-model gate doctrine | `skills/cross-model-review/SKILL.md`    |
+| Authoring/covenant method | `skills/skill-authoring` + README       |
+|                           | ("House covenant" paragraph)            |
+| Execution discipline      | `skills/operational-rigor`              |
+| Practice records          | PR #90/#93/#97 bodies, per-PR           |
+|                           | evaluation comments, issue #92          |
+| This library              | repo-specific operating layer, dated    |
+|                           | 2026-07-30 — canon and records win      |
+
+## Current-state triage (as observed 2026-07-30)
+
+Facts a fresh session must not misread as its own breakage:
+
+- At authoring time: 0 open PRs; 1 open issue (#92) — #92 is DESIGNED
+  to stay open while any `unprobed` marker exists; it is a queue, not
+  a stale ticket. This delivery itself adds issue #100 (transcript
+  disposition; UNCERTAINTY item 1) and, while open, the delivering PR.
+- The repo root carries UNTRACKED private session transcripts
+  (`chat-history.md`, `security-enhancement.md`). Never stage them;
+  see `repo-boundaries-and-sync`. Owner disposition pending (#100).
+- `skills-staging/` is gitignored by owner decision (`92314a6`);
+  this library was force-added on an explicit owner instruction —
+  that delivery is not license to publish other ignored zones.
+- The README per-skill sync loop currently errors on `skill-vetting`
+  (present in `skills/`, absent from both live installs) — a known
+  pre-existing state, not drift you introduced.
+- Many local branches are residue of merged or abandoned campaigns —
+  do not adopt-and-finish them (see `failure-archaeology`).
+
+## Reading order
+
+1. `contribution-gate-playbook` — the pipeline end to end.
+2. `gate-adjudication-and-folds` — judging lens verdicts.
+3. `doctrine-change-conventions` — what any doctrine diff satisfies.
+4. `repo-boundaries-and-sync` — what may be staged, synced, published.
+5. `failure-archaeology` — dead ends and residue from this session.
+
+## Relationship to the older local library (2026-07-12)
+
+`skills-staging/` also holds a 12-skill library authored 2026-07-12
+(local-only, unpublished, gitignored — its existence is public via
+`92314a6`'s commit message). Overlap map, verified 2026-07-30:
+
+- Partially superseded by this library: cross-model-gate-ops,
+  release-and-publish, repo-state-and-sync (verified stale examples
+  in `UNCERTAINTY.md` item 5: the 2026-07 reviewer lineup, the
+  bump-every-PR rule, the `README.zh-TW.md` filename).
+- Old editing-skills-and-docs overlaps the new
+  doctrine-change-conventions — and is itself stale (its description
+  counts "the eight SKILL.md files"; `skills/` now has ten).
+- NAME COLLISION: the old library and this one BOTH carry a skill
+  named `failure-archaeology` (different content). Never install both
+  libraries into one skills directory without renaming one.
+- Everything unlisted (architecture-contract, build-and-env,
+  config-and-flags, debugging-playbook, diagnostics-and-tooling,
+  eval-operations, validation-and-qa) has the old library as sole
+  source — verify each claim against the repo before relying on it.
+
+Precedence for overlapping topics: canon skills first, then the newer
+dated statement, then the older library.

skills-staging/2026-07-30-campaign-ops/UNCERTAINTY.md

@@ -0,0 +1,132 @@
+# UNCERTAINTY — campaign-ops library (2026-07-30)
+
+Findings that are useful but cannot be stated authoritatively. Each
+entry: claim / where it appeared / repo evidence / status / why
+uncertain / what would resolve it / issue created? Every entry ends in
+a safe default a zero-context reader can act on.
+
+## 1. Untracked private transcripts at the repo root
+- Claim: `chat-history.md` and `security-enhancement.md` (both full
+  session transcripts — private content) sit untracked in the public
+  repo's working tree; any stage-everything command would publish
+  them.
+- Appeared: the session's closing report flagged
+  `security-enhancement.md` to the owner and asked for a disposition;
+  no answer had arrived by session end. `chat-history.md` appeared
+  after that session (it is that session's own transcript).
+- Repo evidence: both present and untracked on 2026-07-30
+  (`git status --short`); never in any commit; `92314a6`'s message
+  names the exact threat ("a stray `git add -A`").
+- Status: verified (existence/exposure risk); **user-must-provide**
+  (disposition).
+- Resolves it: owner picks a `.gitignore` pattern or relocates the
+  files out of the repo. `.gitignore` is outside this delivery's
+  allowed paths.
+- Issue: yes — #100 (created 2026-07-30, single consolidated issue):
+  https://github.com/F-e-u-e-r/opus-pack/issues/100
+- Safe default: never stage them; pathspec-only adds; never quote
+  their content anywhere public.
+
+## 2. Exact wording of the standing gate cadence
+- Claim: grok-4.5 high + gpt-5.6-luna ultra every round; gpt-5.6-sol
+  max on "every 3rd round + pre-commit" (session-memory phrasing).
+- Repo evidence: #90's body "gpt-5.6-sol max from r3" (fold commits
+  show sol at r3 then r6–r11, the terminal candidates); #93's body
+  "r2 pre-commit (grok + luna + sol-max)"; for #97 the cadence line
+  lives in its constituents' evaluation comments ("gpt-5.6-sol max
+  from r2"), not the body. All consistent with the phrasing; none
+  states it as a standing rule.
+- Status: **partially-verified** (pattern verified across three
+  campaigns; the governing rule text is owner-set, session-recorded).
+- Resolves it: owner confirmation, or the next campaign PR body.
+- Safe default: run sol on every 3rd, every pre-commit, and every
+  terminal-candidate round; when unsure, include sol — an extra lens
+  costs a round, a missing lens costs the gate's meaning.
+
+## 3. Merge-bypass mechanics ("admin merge")
+- Claim: campaign merges used the owner's admin authority to bypass
+  required review.
+- Repo evidence: #90/#93/#97 all show reviewDecision REVIEW_REQUIRED
+  with zero reviews, yet merged — a bypass demonstrably occurred.
+- Status: bypass **verified**; the exact mechanism (gh `--admin`
+  flag, ruleset bypass list contents) **user-must-provide** (ruleset
+  config needs owner/admin access to read).
+- Resolves it: owner states the flag/ruleset arrangement.
+- Safe default: a session never merges without the owner's ask for
+  that campaign; if a merge is blocked, surface the blocker — do not
+  probe for bypass paths.
+
+## 4. `skill-vetting` absent from both live installs
+- Claim: deliberate pending-adoption state (the advisory hook is
+  opt-in; "Workstream B"), not an overlooked sync failure.
+- Repo evidence: `skills/skill-vetting/` exists; both live installs
+  lack it (diffs run 2026-07-30); README documents the hook as
+  optional. Intent is session/memory-recorded only.
+- Status: state **verified**; intent **user-must-provide**.
+- Resolves it: owner either installs it or records the deferral.
+- Safe default: do not install or uninstall it yourself; expect the
+  README sync loop to error on exactly this directory.
+
+## 5. The 2026-07-12 local library's stale spots
+- Claim: the older root-level `skills-staging/` library (local-only,
+  gitignored) is stale where it overlaps current practice.
+- Verified examples (2026-07-30): its release-and-publish requires a
+  version bump per substantive PR (contradicted by #84–#97 at
+  0.1.16); its re-verify command greps `README.zh-TW.md` (renamed
+  `README.zh-Hant.md` in `c15c29d`-era work — the old path no longer
+  exists); its gate-ops file records the 2026-07 lineup gpt-5.5 +
+  grok-4.5 max (differs from the campaign lineup; both are
+  date-stamped volatile by their own rules).
+- Status: **historically-valid**; the files are the owner's local
+  scratch, not touched by this delivery.
+- Resolves it: an owner-sanctioned refresh or retirement of the old
+  library.
+- Safe default: for overlapping topics, canon skills win, then this
+  dated library; verify any old-library command against the repo
+  before running it.
+
+## 6. The sol-unverified r11 folds in #90
+- Claim: the final two r11 folds (`git add --` hardening; the
+  fast-forward scope sentence) merged without sol re-review.
+- Repo evidence: the two folds are named in `83a038d`; #90's body
+  discloses that the final two folds land sol-unverified without
+  naming them; grok/luna never objected; CI green.
+- Status: **verified** as a disclosed, accepted residual.
+- Resolves it: nothing owed; a future finding against those folds is
+  a new finding.
+- Safe default: do not re-open #90's gate; treat the disclosure as
+  the record.
+
+## 7. Evaluation comments — verification depth
+- Claim: all nine constituent PRs (#85–#89, #91, #94–#96) carry a
+  maintainer evaluation comment.
+- Repo evidence: #85, #94, #96 read in full on 2026-07-30 (shape and
+  no-owner-quotes confirmed); the remaining six confirmed present the
+  same day with matching "Evaluation record (maintainer)" openers
+  (on #86 it is the SECOND comment — the first is the contributor's).
+- Status: **verified** (presence, all nine; full-text read, three).
+- Resolves it further: read the remaining six in full before citing
+  their details.
+- Safe default: when writing new evaluation comments, follow the
+  three fully-read ones' shape.
+
+## 8. Session-memory phrase "evals/round4 … COMMITTED"
+- Claim (memory, 2026-07-23): round-4 eval design "committed".
+- Repo evidence: `evals/` is gitignored with zero tracked files
+  (2026-07-30) — nothing eval-related is committed to this repo.
+- Status: memory claim **unverified as written**; repo state
+  verified. Likely loose wording for "written to the private evals
+  tree".
+- Resolves it: owner's private tree; not resolvable here.
+- Safe default: treat `evals/` as private and ignored; never cite a
+  tracked evals path.
+
+## 9. This library's own delivery mechanism
+- Claim/process note: delivering skills under a gitignored path
+  required `git add -f`, per the explicit retiring-architect task
+  instruction; `.gitignore` was not modified.
+- Status: verified (this delivery).
+- Safe default: this is NOT precedent for publishing other ignored
+  zones (`evals/`, `internal/`, `.claude/`, `guideline*.txt`,
+  `pack-eval-artifacts/`) — those stay private absent the same kind
+  of explicit owner instruction.