research(meta-orchestrator): G — full refactor design + F.3 binding scope - #204
Merged
Merged
Conversation
…cope Sub-wave G R-phase: design research for full /meta-orchestrator skill refactor. Outputs two research-patches (S3 split — both under 500 lines). Main patch (277 lines): §-1 cold review (GO), §1.1 findings registry (7 sources), §1.2 autonomy design (B=REJECT/C-hybrid=DEFER/status-quo=KEEP), §1.3 UX redesign (Format 1: true 1-liner + Format 2: 3-layer output structure), §1.4+§1.5 summary pointer, §1.6 out-of-scope forks (6), §1.7 forward+backward self-check, §1.8 T19 own cold-QA. Two D-G DECISION-NEEDED items for maintainer. Companion patch (454 lines): full §1.4 tech-debt audit (Class A/B/C check for 11 sections — all accurate; mirror diff — 2 files differ, both intentional; Gap-1 regex reproduction with command+output; principle 18 test TypeScript spec). §1.5: 12 binding F.3 scope items (M1 dispatch fix, D3-MAJOR misattribution, M2 injects-terminology, 3 MINORs, 2 antipatterns, 3-layer §10 headers, references/output-format.md, Gap-1 fix, REPORT reconciliation, mirror sync obligation), all with file path + WHAT + WHY + falsifier + owner. Prior-art: skipped — research-patch only, no new capability
…tches Add <!-- scope:... --> first-line annotations (principle 10) and §1.7 self-review substance to companion file (principle 13 forward-check arm). Both files now pass principles 10 + 13 pre-push gate. Prior-art: skipped — fix only, no new capability
This was referenced May 25, 2026
artyhoo
added a commit
that referenced
this pull request
May 25, 2026
… detection) (#220) Run `bash .claude/skills/meta-orchestrator/helpers/plan-currency-check.sh` (L2 Stage 3 detection shipped in #217) → 88 UNTRACKED-N entries surfaced between the 2026-05-22 reconciliation and origin/staging tip (#217). Map each to an existing §0 / Track row by adding the PR number to its evidence cell, or to a new §0 row for two umbrellas that landed in full since the prior snapshot. Re-run helper → 0 UNTRACKED remaining. Key changes: - Snapshot date 2026-05-22 → 2026-05-25 (header + §0). - N8 row: A-phase 🔲 → 🟡 — C1 SSOT-existence (#170), C2 kickoff T-enumeration floor (#174), C3 principle 13 §1.7 substance (#178), C4 delivery-channel marker (#177), activation #180. C5 + cost-levers remain gated on §5.3 utilisation trigger. - Track M.1 / M.4 → DONE: M.1 codified T20 via #212 (with NB note — recommendation-laziness took the T20 slot, mutation-equivalence T-bump 20→21 still pending); M.4 6 paired-negative bash-hook tests shipped #195/#196/#197/#198/#199/#200. - Two new §0 rows: Meta-orchestrator skill (Track P) — BUILD #186 + audit rounds #192/#193/#194/#201/#202 + UX refactor #203/#204/#205 + planner-completeness #213/#214/#217 + §1.7 PR-body mandate #216; Recommendation-laziness discipline — R-phase #206/#207, benchmark #210, I-phase Sub-waves A/C/D #211/#212/#215. - N7 row: + dogfood research-patch #135 / §4 demotion #166 / live-trial verified #171. N4b row: + design #136 / record #118. - Infra paragraph: PR refs for I.1 follow-ups (#121/#123/#124/#125/ #128/#130/#131/#143/#145/#146/#147/#148/#149/#172/#187), I.2 (#139/#142/#154/#175), I.3 DN-4 (#126/#132/#133/#138/#140/#152/ #159/#161/#162/#167). - Track 2.3 (channel-earliness audit) → DONE 2026-05-23 (#181); removed from "What actually remains". - Footer subsection: standalone work (#191 satellite-arch / #189 guard-liveness / #173 storm-readiness / #176 §10 port / #182 cleanup), Wave 10 follow-ups (#110/#112/#113), plan-revision history (#108/ #109/#153/#155/#157/#160/#164/#165/#168/#179/#185). Verification: - `bash .claude/skills/meta-orchestrator/helpers/plan-currency-check.sh | grep -c '^UNTRACKED'` → 0 (down from 88). - `npx markdownlint-cli docs/meta-factory/wave-sequencing-plan.md` → no violations. - `npx vitest run packages/core/skills/plan-currency-check.test.ts` → 14/14 passed. Prior-art: skipped — chore, doc reconciliation only, no new capability or rule introduced.
artyhoo
added a commit
that referenced
this pull request
Sep 1, 2026
…1550) * docs(s3-c5): D1 derivable-prose population inventory + entry re-verification 19 rows / 5 classes; enumeration strictly BEFORE migration (T5/T10). Findings: presets row trigger fired (MIGRATE-now), INSTALL-FOR-AI rosters derivable from setup.d manifest (MIGRATE-now x2), README count claims live- drifted (20 hooks vs measured 21; 8 agents vs shipped 10 -> PROPOSE-to-owner), aif-version population drifted 4 -> 6 files (P-2 park stands). T7 counter- prompt run cold, non-empty; T15 self-application section present. * feat(docs-gen): INSTALL-FOR-AI install-roster → getff:begin generated section + drift gate S3 D2 (beta-ai-docs-agnosticism), inventory row B1: the «This installs» roster (INSTALL-FOR-AI.md:76-96) becomes a getff:begin generated section rendered from the installer manifests (setup.d/20-agents.sh skip-list + factory-gated pair, setup.d/10-skills.sh cp-literals, setup.d/lib.sh GETFF_SKILLS_* constants). Drift gate: scripts/render-install-roster.mjs --check (write/check modes, render-rule-index.mjs pattern), wired into audit-self.yml manifest-render-check. Caveat prose (KEEP-AIF notes, --profile core) preserved outside the fence (T17). Inventory B2 verdict revised MIGRATE-now → STAYS-PROSE with owner+trigger (§7 addendum: tree sits inside a ```text block + annotation-bearing judgment). Prior-art: prior-art-evaluations.md#208 (deterministic digest renderer — same render-rule-index/fence.ts pattern extended to a second source class; fence.ts reused verbatim, zero new fence logic). * feat(docs-gen): AI-USAGE-GUIDE §6a Launch presets → getff:begin rendered from shipped preset data S3 D2+D5(i) (beta-ai-docs-agnosticism), inventory row A3: the §6 honesty-table row «Launch presets … not shipped … this guide gains a §Presets rendered from the shipped preset data» had its own trigger fire (beta-delivery-ux S2 merged, presets on disk) — the row leaves the not-shipped table and the promised section lands as a generated one. Renderer scripts/render-presets.mjs parses .claude/skills/pipeline/references/presets/*.json (same source list-presets.sh reads; line shape mirrors its output), writes the `pipeline-presets` fence via the shared fence.ts machinery. Drift gate --check wired into audit-self.yml. Baselines: 11 install fingerprints regenerated (SNAPSHOT_MODE=capture); audited diff = only .ai-factory/AI-USAGE-GUIDE.md + .ai-factory/refresh-baseline.json hashes; SNAPSHOT_MODE=compare 15/15 pass. Prior-art: prior-art-evaluations.md#208 + #203/#204 (same render/--check + marker-region drift-gate family — fence.ts reused verbatim, zero new fence logic). * feat(agents): claims-conformance-auditor — cold docs-claims vs shipped-reality auditor S3 D4 (beta-ai-docs-agnosticism, spec C5 r3 + §8): the named cold auditor the assembly gate runs over docs-site claims (compliance-verifier class agents/*.md; attention-is-not-a-mechanism §1 — checklist is merge authority, agent is the detection layer). Cold-by-construction dispatch, claim taxonomy, per-claim VERIFIED/GAP/UNVERIFIABLE with T3 evidence, GO/REVISE/STOP output grammar, promotion trigger = spec §6 falsifier (repeated claim drift → deterministic check). tools: line = harness-universal only (principle 21 green: 14/14). Acceptance dry-run over README.md executed cold (56 claims: 47 VERIFIED / 6 GAP / 3 UNVERIFIABLE) — output pasted in the stage PR body; GAP rows are maintainer-owned README drift → routed to the D3 proposal, never direct-edited here. Prior-art: prior-art-evaluations.md#228 (fidelity-auditor class — session-bound cold agent under no-paid-llm-in-ci; shape precedents compliance-verifier + backward-sweep-auditor reused, protocol novel to the claims-taxonomy slice). * S3 D3: owner-gated proposals (P1 zcode rollup renderer, P2 living-docs, P3 README) + install-roster regen P1 ships scripts/render-zcode-parity-rollup.mjs — PROPOSAL renderer for the zcode-parity-doctrine §2 derivable rollup (hook population / plugin twins / classification counts; per-row rationale stays prose per the D7 falsifier). --check refuses (exit 2) until the maintainer lands the target fence, so a premature CI wiring fails loud, never silently green. Verified: --emit parses 21/21 census rows (escaped-pipe-aware + §2-scoped), rollup matches the hand count at doctrine:65; plugin twins 15 of 21. P2 (living-docs-auditor /aif-verify contradiction) and P3 (README claim drift from the cold-auditor dry-run: agent count, ESLint major, husky/depcruise wiring steps, probeR4 pass-vs-warn, Wave B status, hook count) are evidence tables awaiting maintainer sign-off — zero direct edits to owner-gated paths. INSTALL-FOR-AI.md roster regenerated after claims-conformance-auditor.md landed (10 → 11 shipped agents) — the drift gate caught the same-PR change, which is the live discrimination proof for this stage's D2. * fix(s3-c5): cold-QA/fidelity round-1 findings — fail-loud roster guard + P3 ESLint retraction Cold-audit rework (T19/T21 + fidelity Round 1, 2026-09-01): - render-install-roster.mjs: zero-match skip-list now throws (fail-loud) instead of silently rendering ALL agents as shipped if setup.d/20-agents.sh is restructured. - owner-proposals patch: P3 ESLint row RETRACTED — README:30 "ESLint 10 flat config" is correct (packages/core/package.json:94 "eslint": "^10.4.0"; root package.json has no eslint key; the dry-run's quoted probe was unreproducible). 6 GAP rows -> 5 actionable. - same patch: "three S3 gates" -> two (render-rule-index/render-rules predate S3). Fidelity Round-1 MAJOR (kickoff host-verify runner lines) is NOT discharged here: the kickoff edit is harness-classifier-blocked for this session (sensitive file) — stays as park P-KICKOFF for operator egress. * fix(s3-c5): rework round-1 — sweep rows, prettier, baselines, P1 scope reconciliation - wire install-roster-check + presets-check into run-local-ci-sweep.sh gate_table (coverage test PASS=9 FAIL=0; closes the two unwired CI commands) - prettier-canonical output: format auditor + AI-USAGE-GUIDE; render-presets now emits prettier-canonical fence bodies (blank lines around the bullet list) so --check stays green after format:check - re-capture 11 install baselines on the final tree (new claims-conformance-auditor ship line + prettierignore + guide hash); diff audited — only expected line-classes; byte-identical compare 15/15 - P1 scope reconciliation (fidelity MAJOR): owner-proposals §P1 now states the narrow scope explicitly — §2 rollup counts convert; §2 Status col judgment-bearing (D7 falsifier, :61/:62 quoted); §3 table PARKED under §6 with Option A/B; inventory row A2 + §8 addendum made verbatim-consistent with P1 - P2 P-GH park resolved: S1's replacement wording carried verbatim from PR #1311 body (parked question 3), provenance recorded; still proposal-only (zero owner edits) Prior-art: skipped — rework round 1: gate-table wiring + formatting + baseline regen + proposal scope reconciliation; no new capability * docs(kickoff-s3): host-verify runner lines for the two S3 drift gates (W-1, coordinator host-side — container Edit on kickoffs is classifier-blocked) * docs(s3-c5): owner-proposals patch — principle 10 scope slug + principle 13 §1.7 self-application section (pre-push meta-tests) * docs(s3-c5): owner-proposals §1.7 — correct the P1 renderer reuse claim (no fence.ts import until the fence lands; round-3 fidelity note) --------- Co-authored-by: Test <test@example.com>
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.
Summary
Sub-wave G R-phase: design research for full
/meta-orchestratorskill refactor.Outputs two research-patches (S3 split applied — both under 500 lines).
Main patch (
2026-05-24-meta-orchestrator-refactor-design.md, 278 lines):Companion patch (
2026-05-24-meta-orchestrator-refactor-f3-scope.md, 473 lines):Blocks F.3 implementation — companion §1.5 = F.3 binding spec.
§1.7 Forward/Backward-check applied
Forward: build-first-reuse-default.md §3 — F.1 prior-art (10 candidates, 6-item checklist) ingested; CC constraint verified from primary sources; no BUILD-without-search. no-paid-llm-in-ci.md §1 — session-bound R-phase; principle 18 = deterministic test. doc-authority-hierarchy.md — research-patches folder authority inherited. ✅
Backward: does not supersede
2026-05-23-meta-orchestrator-prior-art.md(BUILD verdict for capability unchanged). Does not supersede2026-05-24-meta-orchestrator-ux-research.md(G ingests F.1 as input). F.3 must cite companion §1.5 as binding spec. ✅Test plan
<!-- scope:... -->annotations on first line (principle 10)