Skip to content

feat(skills): wave-5.1 — tool-bootstrapping skill + SSOT #31-#37 atomic landing - #34

Merged
artyhoo merged 1 commit into
mainfrom
feat/wave-5.1-tool-bootstrapping-skill
May 11, 2026
Merged

feat(skills): wave-5.1 — tool-bootstrapping skill + SSOT #31-#37 atomic landing#34
artyhoo merged 1 commit into
mainfrom
feat/wave-5.1-tool-bootstrapping-skill

Conversation

@artyhoo

@artyhoo artyhoo commented May 11, 2026

Copy link
Copy Markdown
Owner

Summary

Confirmed §11 decisions: D1=b D2=b D3=b D4=d D5=c D6=a D7=a D8=a D9=c (user-confirmed 2026-05-11).

Sub-waves 5.2 (setup.sh context7 bootstrap, D3=b) and 5.3 (AGENTS.md bullet + UserPromptSubmit hook D7=a + audit-ai-docs probe D4=d) follow as sequential PRs.

§1.7 Self-discipline check (REQUIRED if PR touches discipline-bearing files)

§1.7 Forward-check applied

Source: research-patch §13.1 (2026-05-10) — copied verbatim per kickoff carry-forward. The proposed «Project-Aware Tool Bootstrapping» discipline complies with each currently-active enforcement layer:

  1. Code-level (R1-R20). No new TypeScript code in Wave 5.1 (skills are .md). R1-R20 do not apply to markdown — formal complies-trivially.
  2. Principle-level (01-09). Principle 09 (doc-authority) applies to new SKILL.md files. Wave 5.1 ships compliant > **Authoritative for:** headers. Both .claude/skills/tool-bootstrapping/SKILL.md and skills/tool-bootstrapping/SKILL.md appear in canonical list; canonical-list extension landed in same commit (mirrors §13.21 Wave 2 pattern).
  3. Capability-commit gate. No new explicit dep; no ≥50 LOC under new packages/core/<new-dir>/; no ≥80 LOC under packages/. Wave 5.1 is NOT a capability commit. Prior-art: trailers cite fix: wave-5 readiness — AIF Handoff overlap analysis + scope annotations (SSOT #27-#29) #31 and chore(pr-template): add §1.7 forward+backward stubs + Skipped guidance #33 positively per CLAUDE.md.
  4. Build-vs-reuse SSOT. Seven new entries (fix: wave-5 readiness — AIF Handoff overlap analysis + scope annotations (SSOT #27-#29) #31-chore(wave-5-trio-followup): §13.25 closure + D-3 test + MD040 fix #37) land atomically with Wave 5.1 first artefact per prior-art-evaluations.md §3. Entry chore(wave-5-trio-followup): §13.25 closure + D-3 test + MD040 fix #37 (Windsurf Cascade) added per reviewer m2 carry-forward.
  5. Trigger sweep (§1.6). Run in research O0.1. Two CASCADE-RELEVANT entries (§13.18, §13.19) + one MEDIUM (§13.22) surfaced and explicitly handled in D8/D9 decisions + SSOT entry chore(pr-template): add §1.7 forward+backward stubs + Skipped guidance #33 cross-link.
  6. Doc-authority on artefacts produced. Both SKILL.md files carry Authoritative-for headers; references/decision-format.md files carry headers per doc-authority-hierarchy.md §3.

§1.7 Backward-check applied

Source: research-patch §13.2 (2026-05-10) — copied verbatim per kickoff carry-forward. Complete sweep of existing artefacts under the new rule's scope.

Scope: applies to (a) project onboarding moments — when user first runs setup.sh or first opens AI agent in a fresh consumer project; (b) dep-change moments — when package.json deps change after onboarding.

Artefact Status in this PR Remaining work
README.md deferred — pointer to skill + tool-decisions.md convention Wave 5.2 cross-link
INSTALL-FOR-AI.md deferred Wave 5.2 directly
INSTALL.md deferred Wave 5.2 cross-link
packages/core/templates/shared/AGENTS.md.template deferred Wave 5.3 (D4=d)
setup.sh deferred Wave 5.2 directly

Exemption: packages/*/research/fixtures/** and packages/*/fixtures/** — mirrors §13.21 Wave 2 pattern. Exemption meta-test (positive + mutation pair) ships in Wave 5.3 as part of audit-ai-docs.sh probe + negative-test deliverable.

Test plan


2026-05-12 retroactive Wave 8.5 note: This PR's §1.7 Forward-check section would not pass the Wave 8.1 substance gate (no file:line citations present). Pre-Wave-8 acceptance — kept as historical evidence of the #discipline-theatre gap that motivated §13.29.

…ic landing

§13.25 tool-bootstrapping discipline implementation per research-patch
2026-05-10-§13.25-tool-bootstrapping-research.md.

Confirmed §11 decisions: D1=b D2=b D3=b D4=d D5=c D6=a D7=a D8=a D9=c
(user-confirmed 2026-05-11 in orchestrator session).

Adds: project-internal + shipped tool-bootstrapping skill (D5=c); SSOT
entries #31-#37 atomic (#37 Windsurf Cascade per reviewer m2); principle
09 REQUIRED_HEADER_DOCS extension per Wave 2 precedent; install.sh ship
block mirror of rules-as-tests pattern; open-questions §13.25 status.

Sub-waves 5.2 (setup.sh context7 bootstrap, D3=b) and 5.3 (AGENTS.md
bullet + UserPromptSubmit hook D7=a + audit-ai-docs probe D4=d) follow
sequentially.

§13.18 cascade (D9=c): if AIF deep-alignment trigger fires negative in
Phase 11, rules 1-4 reuse-via-thin-wrapper (D8=a) is reversible — full
rewrite cost bounded by references/decision-format.md schema stability.

Prior-art: prior-art-evaluations.md#31 (AIF /aif ADOPT — foundation for rules 1-4 thin-wrapper reuse, D8=a).
Prior-art: prior-art-evaluations.md#33 (Continue.dev permissions.yaml DEFER — vocabulary source for decision-format.md schema design).
@artyhoo
artyhoo merged commit 593680b into main May 11, 2026
18 of 19 checks passed
@artyhoo
artyhoo deleted the feat/wave-5.1-tool-bootstrapping-skill branch May 22, 2026 18:10
artyhoo added a commit that referenced this pull request Jul 11, 2026
…audit) (#965)

## Summary

Manifest↔filesystem drift audit of `extension.json` (AIF extension Path A), observed during PR #956: the `factory`, `scripts`, `templates.shared` and `templates.react-next` sections referenced paths that don't exist on disk (`factory/*`, `scripts/audit-ai-docs*.sh`, `templates/shared/*`, `templates/react-next/*`). Every entry now points at the real source path that `install.sh` + `setup.d/` actually copy, keeping the upstream-draft key structure (lee-to/ai-factory PR #34).

## Changes

- `factory.templates`: `DESCRIPTION.md`/`ARCHITECTURE.md` → `packages/core/templates/shared/{DESCRIPTION.template.md,ARCHITECTURE.ts-server.md}`; base `RULES.md` → shared multi-stack `packages/preset-next-15-canonical/RULES.md` (source of truth: `setup.d/30-templates.sh:20-29`)
- `factory.react-next` → `packages/preset-next-15-canonical/{templates/ARCHITECTURE.react-next.md,RULES.react-next.md}` (per `setup.d/30-templates.sh:45-46`)
- `factory.rules` → `packages/core/templates/shared/integration-rules.md` (per `setup.d/30-templates.sh:31`)
- `scripts` → `packages/core/audit-self/audit-ai-docs.sh` + `packages/preset-next-15-canonical/audit-self/audit-ai-docs.react-next.sh` (per `install.sh:340,359`)
- `templates.shared` → prefixed `packages/core/` (all six files exist there, incl. dotfiles)
- `templates.react-next` → `packages/preset-next-15-canonical/templates/*` + the two `.storybook` files delivered by `setup.d/40-configs.sh:71-72` (post-#956 the old `packages/core/templates/react-next/` holds only these)
- `templates.ts-server`: paths were already correct (root `templates/ts-server/` is the real source per `setup.d/40-configs.sh:286-295`); added the shipped-but-unlisted `github-actions-workflow-integrity.yml`
- New `$paths-comment` documenting that paths are repo-root-relative source paths mirroring the install.sh fallback, and that react-spa/react-native stacks are deliberately not yet listed
- `skills` block left untouched — PR #954 renames it (`skills/rules-as-tests` → `skills/getff`) in flight; different hunks, no conflict

## Prior-art consult

- [x] Capability commits in this PR carry a `Prior-art:` trailer — N/A: no capability commit (path-value fixes in an existing JSON manifest; no new dependency, no new code module)
- [x] If a new capability area surfaced during this PR — none surfaced
- [x] If existing entries matched — none touched
- [x] context7 queries for new capability areas — N/A (no new capability area)

## Test plan

- [x] `jq empty extension.json` green; all 27 referenced paths verified to exist on disk (loop over every path-bearing value → zero MISS)
- [x] `bash tests/plugin/opencode-adapter.test.sh` → PASS=7 FAIL=0 (the only in-repo executable consumer of extension.json)
- [x] Pre-push hook full gate set green on push (first attempt hit the known principle-11 F1 30s vitest timeout flake; clean on re-run)
- [ ] §1.7-свод lands in squash-body (`gh pr merge --squash --body "$(gh pr view <N> --json body -q .body)"`)

## §1.7 Self-discipline check (REQUIRED if PR touches discipline-bearing files)

### §1.7 Skipped: mechanical maintenance — path-value fixes in extension.json manifest to match the filesystem; no discipline rule introduced or extended
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