owfadev 0.3.2 → 0.4.0

package/.agents/skills/owfa-check/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: owfa-check
+owner: framework
+description: "Audit the repository's health: hard-structure checks on the foundation and plugins + semantic checks on plugins and pages. Triggers on: check, 健康检查, 检查插件, lint."
+---
+
+# owfa-check: repository health audit
+
+This is an audit, not a guardrail. It outputs a graded report: error = structural breakage requiring action; warning = a suggested to-do. Check rules come from two places: the foundation part of this file (protocol level) + the injection region below (a mechanical projection by owfa-kernel from each plugin manifest's checks list; presence means registration).
+
+## Purpose
+
+Run one health audit over the entire instance (foundation + plugins + wiki pages).
+
+## Scope
+
+Read: everything (.owfa/, the AGENTS.md injection region, .agents/skills/, the wiki/, vault/ directory trees)
+Write: one line in wiki/log.md (type "check"); regenerable zones are rebuilt directly per the action discipline (scripts: injection region / registry / command copies; semantics: index / tags / hot eviction / log archiving / hash recomputation)
+
+## Steps
+
+1. **Foundation hard checks** (protocol level):
+   - **Static self-check script**: `python .owfa/scripts/owfa_kernel.py validate` (directory completeness, manifest seven fields + optional commands, id consistency, dependency existence, acyclicity, command binding owner×commands bidirectional consistency) — any error means FAIL
+   - **Idempotent rebuild**: `python .owfa/scripts/owfa_kernel.py all` (injection region / registry plugin section / command copies — mechanical and automatic; drift is fixed here, the script source is the rule list)
+   - `.owfa/protocol/registry.yaml` is in place with the protocol / reserved sections intact (the script never touches these two sections; a missing section is an error)
+   - **Value-set violation**: scan the frontmatter of all wiki/ pages; a type / status value outside the registry value set → error
+   - Every `.owfa/command/` SKILL.md has frontmatter (name / description / owner; optional consumes — an ordered list of plugins whose write-side contracts are consumed; referenced plugins must be present with a usage list; mandatory for owner-driven commands)
+2. **Plugin checks**: first run the attached audit `python .owfa/scripts/owfa_kernel.py audit` (mechanical items: each plugin's scripts/check.py executed on audit discovery, read-only reporting; errors count toward FAIL); then execute the items marked "semantic" in the injection-region blocks below
+3. **Semantic checks**: read plugin and command files, looking for dangling references (a command referring to nonexistent structure), ghost fields (page fields with no owning plugin and not registry-reserved), and injection-region blocks inconsistent with the PLUGIN.md Checks section
+4. Summary output: PASS / WARN / FAIL counts + graded details + vault backlog count (informational)
+5. **Fixes are executed by grade per the action discipline** (`.owfa/protocol/actions.md`): mechanical-automatic items are done directly — `pipeline.py index` / `tags` (index rebuild), `owfa_kernel.py all` (registry / injection region / copies), hash recomputation (raw_sha256 of changed frontmatter); hot / log overflows are converged by their own write-pipeline commands; mechanical-confirmation items present a list and ask once; semantic items are reported only; historical entries are never automatically changed
+6. Prepend one line to wiki/log.md (type "check", via `pipeline.py log check "<one line>"`); if anything changed (fixes / a log line), commit per the commit discipline (`检查: <conclusion>`, see `.owfa/protocol/actions.md`)
+
+## Tools
+
+grep / file reading suffice; no second scan when one read is enough (call frugality).
+
+## Parameters
+
+- None: full-repository audit
+- Plugin id: check that plugin only
+
+## Injected Section (plugin check blocks)
+
+> This region is a owfa-kernel projection from each plugin manifest's checks list (rebuilt by `inject` / `all`; presence means registration); handwritten content does not belong here — to change check rules, edit PLUGIN.yaml.
+
+<!-- check-inject:start -->
+
+<!-- check-inject:end -->

package/.agents/skills/{docs → owfa-docs}/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: docs
+name: owfa-docs
 owner: framework
 description: "Docs thin-router: points to the documentation map and the behavior/feedback protocol — no norms live in this skill. Fire when the user reports dissatisfaction with agent behavior (possible plugin/kernel cause), asks where something is documented, or how to file feedback. Triggers on: docs, 查文档, 文档在哪, 框架问题, 行为自检, agent-behavior, 怎么提issue."
 ---
 
-# docs: thin router to the documentation layer
+# owfa-docs: thin router to the documentation layer
 
 S-layer pointer only — the norms live in the documents (L layer). Re-read what you cite; never quote from memory.
 
@@ -13,12 +13,12 @@ S-layer pointer only — the norms live in the documents (L layer). Re-read what
 When the user reports dissatisfaction with your behavior, do **not** launch an analysis on your own:
 
 - **Not a plugin/kernel matter** (pure conversation, execution slip)? Ignore the rest of this skill — respond to the user directly, fix in-session.
-- **Possibly a plugin or kernel problem?** First ask the user whether to run a behavior self-audit (**recommended** — it produces the evidence base for a real fix). Only on consent, follow the protocol: [`.meta/docs/agent-behavior.md`](../../docs/agent-behavior.md) — feedback handling → routing → the seven-step standard.
+- **Possibly a plugin or kernel problem?** First ask the user whether to run a behavior self-audit (**recommended** — it produces the evidence base for a real fix). Only on consent, follow the protocol: [`.owfa/docs/agent-behavior.md`](../../docs/agent-behavior.md) — feedback handling → routing → the seven-step standard.
 
 ## 2. "Where is X documented?" / "how does X work?"
 
-Read [`.meta/docs/map.md`](../../docs/map.md) — the routing table (what to read when), framework docs and package-repo docs both.
+Read [`.owfa/docs/map.md`](../../docs/map.md) — the routing table (what to read when), framework docs and package-repo docs both.
 
 ## 3. Filing feedback / issues
 
-The routing table lives in [`.meta/docs/agent-behavior.md`](../../docs/agent-behavior.md) §Routing: framework → owfa; package members → the matching `pkg-*` repo; new-plugin proposals → incubation on owfa.
+The routing table lives in [`.owfa/docs/agent-behavior.md`](../../docs/agent-behavior.md) §Routing: framework → owfa; package members → the matching `pkg-*` repo; new-plugin proposals → incubation on owfa.

package/.agents/skills/{wiki_plugin_kernel → owfa-kernel}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: wiki_plugin_kernel
+name: owfa-kernel
 owner: framework
-description: "Kernel and mechanics reference: the projector's subcommands (7 convergence — ls/validate/audit/inject/registry/deploy/all — plus 8 package-lifecycle: plan/install/uninstall/list-remote/migrate/upgrade/pkg/residual) + a full account of the plugin mechanics — manifest / dependencies / the three projections / command binding / bridge rules / layering principles (a bb-domain worked example). Triggers on: 插件内核, wiki_plugin_kernel, kernel, 注入块更新, 投影重建, 插件机制, 更新注入."
+description: "Kernel and mechanics reference: the projector's subcommands (7 convergence — ls/validate/audit/inject/registry/deploy/all — plus 8 package-lifecycle: plan/install/uninstall/list-remote/migrate/upgrade/pkg/residual) + a full account of the plugin mechanics — manifest / dependencies / the three projections / command binding / bridge rules / layering principles (a bb-domain worked example). Triggers on: 插件内核, owfa-kernel（旧 owfa-kernel）, kernel, 注入块更新, 投影重建, 插件机制, 更新注入."
 ---
 
-# wiki_plugin_kernel: kernel and mechanics reference
+# owfa-kernel: kernel and mechanics reference
 
-`python .meta/scripts/wiki_plugin_kernel.py <subcommand>` — the framework side's only projector: PLUGIN.yaml is the body; the AGENTS.md injection region, the check check blocks, the command usage blocks, the registry plugin section, and the command and connector skill copies are all its projections. Idempotent, runnable at any time; drift is fixed on the run. This skill also serves as the **mechanics master outline**: a deployed instance carrying only the AGENTS.md injection region + skill copies is self-sufficient; this file is the authoritative home of the mechanics on the deployment side.
+`python .owfa/scripts/owfa_kernel.py <subcommand>` — the framework side's only projector: PLUGIN.yaml is the body; the AGENTS.md injection region, the check check blocks, the command usage blocks, the registry plugin section, and the command and connector skill copies are all its projections. Idempotent, runnable at any time; drift is fixed on the run. This skill also serves as the **mechanics master outline**: a deployed instance carrying only the AGENTS.md injection region + skill copies is self-sufficient; this file is the authoritative home of the mechanics on the deployment side.
 
 ## Subcommands
 
@@ -17,10 +17,10 @@ description: "Kernel and mechanics reference: the projector's subcommands (7 con
 | `audit` | attached audit: executes each plugin's `scripts/check.py` on discovery, read-only report (may take a plugin id to check just one) | none |
 | `inject` | rebuilds the three projections: the AGENTS injection region + the check check blocks + the command usage blocks | AGENTS.md, command SKILL.md files containing injection regions |
 | `registry` | rebuilds the registry.yaml plugin section (from each manifest's `fields`) | registry.yaml |
-| `deploy` | syncs skill masters (`.meta/command/*/` commands + `connectors/*/` connectors) → `.agents/skills/` copies; orphan copies are reported only (deletion belongs to the human) | copies |
+| `deploy` | syncs skill masters (`.owfa/command/*/` commands + `connectors/*/` connectors) → `.agents/skills/` copies; orphan copies are reported only (deletion belongs to the human) | copies |
 | `all` | validate + inject + registry + deploy in one step | all of the above |
 
-Package lifecycle (full wizard protocol and judgment rules: `.meta/command/plugin/SKILL.md`):
+Package lifecycle (full wizard protocol and judgment rules: `.owfa/command/plugin/SKILL.md`):
 
 | Subcommand | Purpose | Disk writes |
 |---|---|---|
@@ -33,19 +33,19 @@ Package lifecycle (full wizard protocol and judgment rules: `.meta/command/plugi
 | `pkg` | installed packages: members, versions, connectors | none |
 | `residual <pkg>` | anchor-surface reference scan (the default teardown gate) | none |
 
-The kernel journal (`.meta/kernel-journal.log`, rolling cap of 500 lines, git-tracked) records the mechanical chain — install / warn+ / clear / uninstall / sweep; mechanical facts only, semantic narrative stays in the instance wiki's log.
+The kernel journal (`.owfa/kernel-journal.log`, rolling cap of 500 lines, git-tracked) records the mechanical chain — install / warn+ / clear / uninstall / sweep; mechanical facts only, semantic narrative stays in the instance wiki's log.
 
 ## Typical scenarios
 
-- **PLUGIN.yaml changed** (inject / checks / usage / fields / version): `python .meta/scripts/wiki_plugin_kernel.py all` — the daily standard action; one command converges everything; if validate fails it blocks — fix and rerun
-- **Only refreshing injection blocks**: `inject` suffices, but note it modifies the `.meta/command/` masters; copies sync only via `deploy` — hence always use `all` in daily work
+- **PLUGIN.yaml changed** (inject / checks / usage / fields / version): `python .owfa/scripts/owfa_kernel.py all` — the daily standard action; one command converges everything; if validate fails it blocks — fix and rerun
+- **Only refreshing injection blocks**: `inject` suffices, but note it modifies the `.owfa/command/` masters; copies sync only via `deploy` — hence always use `all` in daily work
 - **Quick health check**: `validate` (structure) + `audit` (attached audit); a full audit (including semantic items) goes through the check command
 - **(Un)installing plugins**: the semantic flow (decisions, directory archiving, log line) goes through the plugin command; the mechanical steps inside it are exactly this CLI's `validate` / `all` / `audit`
-- **Connector skill changed** (`connectors/*/SKILL.md` master): run `deploy` (or `all`) to sync copies — connector skills never enter `.meta/command/` (the command family is pure wiki operation)
+- **Connector skill changed** (`connectors/*/SKILL.md` master): run `deploy` (or `all`) to sync copies — connector skills never enter `.owfa/command/` (the command family is pure wiki operation)
 
 ## Plugin shape
 
-- **One plugin, one directory** (`.meta/plugins/<id>/`): `PLUGIN.yaml` (the manifest, the machine-readable body) + `PLUGIN.md` (pure documentation: design summary (why / family position / key rulings and rejected alternatives) / Structure / Invariants / Changelog — **design rationale and per-plugin details belong here**; mechanics commonalities belong to this reference) + optional `scripts/check.py` (attached audit)
+- **One plugin, one directory** (`.owfa/plugins/<id>/`): `PLUGIN.yaml` (the manifest, the machine-readable body) + `PLUGIN.md` (pure documentation: design summary (why / family position / key rulings and rejected alternatives) / Structure / Invariants / Changelog — **design rationale and per-plugin details belong here**; mechanics commonalities belong to this reference) + optional `scripts/check.py` (attached audit)
 - **Manifest keys**: seven required keys `id / version / depends / updated / attachment / fields / inject`; optional `commands` (command names this plugin drives), `usage` (write-side contract list — the third projection source), `checks` (check-rule list — the check projection source), `bridge` (bridge declaration, see bridge rules), `inject_tier` (injection tier, see tier law below)
 - **attachment** = declares territory and borrow-read relationships (who owns which paths, who read-only consumes whose pages); **fields** = owned page fields (enter the registry, the global vocabulary); **inject** = the plugin's disclosure, one line (the full-disclosure home in the manifest either way; known to the agent the moment it enters the repository when tier is full, read on demand when tier is member)
 - **Attached-audit contract**: `scripts/check.py` defines `check(ctx)` returning `[{level, message}]`; read-only with zero side effects; fixes belong to commands/humans; an AST static check validates the contract's shape
@@ -61,7 +61,8 @@ The kernel journal (`.meta/kernel-journal.log`, rolling cap of 500 lines, git-tr
 
 - **`inject_tier: full | member`** (optional, default full): **full** projects into the AGENTS.md injection region; **member** exits it — exposure rides on the family root's roster line (every member named with id + one phrase), the skill catalog (trigger-surface awareness), and L-layer reads (the manifest `inject` field stays the full-disclosure home either way)
 - Validate requires a member to reach a **full-tier domain root** through depends (family membership, else it exits into invisibility)
-- The projected plugin blocks carry a **byte budget** (15 KiB, derived from the smallest mainstream whole-file AGENTS.md cap minus handwritten allowance): over-budget is a validate error — compress pointer lines or re-tier domain members; the A layer holds pointers and red lines only, never procedures or formats (content contract in `protocol/experiments.md`)
+- The projected plugin blocks carry a **byte budget** (16 KiB, derived from the smallest mainstream whole-file AGENTS.md cap minus handwritten allowance): over-budget is a validate error — compress pointer lines or re-tier domain members; the A layer holds pointers and red lines only, never procedures or formats (content contract in `protocol/experiments.md`)
+- Each full-tier `inject` line has a **pointer-density guideline** (256 B, `INJECT_LINE_GUIDE`, issue #49): a longer line is a validate warning, never an error — write path + read/write trigger + the one easy-to-break invariant + a pointer to PLUGIN.md; detail moves to PLUGIN.md / usage / skills
 
 ## Command-plugin binding
 

package/{.meta/command/plugin → .agents/skills/owfa-plugin}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: plugin
+name: owfa-plugin
 owner: framework
-description: "Package & plugin lifecycle management: plan (disclosure wizard), install (three channels + --without subsets), uninstall, list-remote, upgrade, pkg, residual. Mechanical steps all go through .meta/scripts/wiki_plugin_kernel.py; the agent runs the consent conversation and the one-shot commands. Triggers on: plugin, 插件, 装插件, 卸插件, 装包, install package, uninstall package."
+description: "Package & plugin lifecycle management: plan (disclosure wizard), install (three channels + --without subsets), uninstall, list-remote, upgrade, pkg, residual. Mechanical steps all go through .owfa/scripts/owfa_kernel.py; the agent runs the consent conversation and the one-shot commands. Triggers on: plugin, 插件, 装插件, 卸插件, 装包, install package, uninstall package."
 ---
 
-# plugin: package lifecycle
+# owfa-plugin: package lifecycle
 
-The framework's self-management command, package era (issue #20). Every mechanical step goes through the kernel script; the agent's job is **consent and choice** — never writing `.meta/` by hand.
+The framework's self-management command, package era (issue #20). Every mechanical step goes through the kernel script; the agent's job is **consent and choice** — never writing `.owfa/` by hand.
 
 ## Scope
 
@@ -17,10 +17,10 @@ Read: INDEX via the kernel, PKG.yaml, manifests
 
 When a user asks to install a package and has NOT already specified what to include:
 
-1. `python .meta/scripts/wiki_plugin_kernel.py plan <pkg>` — one-shot disclosure plan: trust line, package disclosure (network/privacy/credentials, package-authored), baseline (the family root, always installed), optional members with one-line summaries and what each selection pulls in, connectors
+1. `python .owfa/scripts/owfa_kernel.py plan <pkg>` — one-shot disclosure plan: trust line, package disclosure (network/privacy/credentials, package-authored), baseline (the family root, always installed), optional members with one-line summaries and what each selection pulls in, connectors
 2. Relay the plan **in the user's language** (render at the agent layer per wiki/language.md — canonical texts are English; the agent translates when relaying, never edits the source)
 3. Walk the steps: trust + disclosure → user acknowledges; optional members → user picks (each pick auto-pulls its dependency closure — show the resolved final set, users cannot compose an illegal subset); connectors → confirm (they ride the package)
-4. Execute: `python .meta/scripts/wiki_plugin_kernel.py install <pkg> --without <unwanted> [--yes]`
+4. Execute: `python .owfa/scripts/owfa_kernel.py install <pkg> --without <unwanted> [--yes]`
 5. Report the convergence output (validate/inject/registry/deploy) in one breath
 
 ## One-shot path (agent / pre-authorized)
@@ -28,8 +28,8 @@ When a user asks to install a package and has NOT already specified what to incl
 If consent already exists (user named exactly what they want, or pre-authorized), skip the conversation:
 
 ```
-python .meta/scripts/wiki_plugin_kernel.py plan <pkg> --json        # machine-readable plan (optional)
-python .meta/scripts/wiki_plugin_kernel.py install <pkg> [--without a,b] [--yes]
+python .owfa/scripts/owfa_kernel.py plan <pkg> --json        # machine-readable plan (optional)
+python .owfa/scripts/owfa_kernel.py install <pkg> [--without a,b] [--yes]
 ```
 
 Kernel commands never prompt — every invocation completes in one shot.
@@ -58,12 +58,12 @@ Every package transaction (install / uninstall / upgrade apply / migrate clear)
 
 Mechanical sync is only half an update. When a new version carries `migrations/`:
 
-1. The kernel stages declarations into `.meta/migrations/<pkg>/` (kernel zone — never inside the package dir), registers the warning ledger, and raises the **tri-face warning**: every kernel invocation prints the pending banner · `validate` stays red (mechanical blessing withheld) · a kernel-managed block lands in the AGENTS injection region so every session sees it
+1. The kernel stages declarations into `.owfa/migrations/<pkg>/` (kernel zone — never inside the package dir), registers the warning ledger, and raises the **tri-face warning**: every kernel invocation prints the pending banner · `validate` stays red (mechanical blessing withheld) · a kernel-managed block lands in the AGENTS injection region so every session sees it
 2. `kernel migrate <pkg>` prints the staged declarations (init or version-chain) — relay them in the user's language
 3. Perform the semantic transformation via the normal command surfaces (confirmation gates as always); **judgment split rule**: assertions that hold only during the transition belong in the author's verify script (dies with the migration); assertions that hold forever belong in `scripts/check.py` (same release)
 4. **Subset matching**: declarations and verifies address the **installed subset**, never the full roster — steps marked `(member: X)` run only when X is installed; verify scripts guard member-specific assertions with `ctx.installed` (the kernel passes it); the ledger records the staging-time subset
 5. `kernel migrate <pkg> --clear` runs the author verify (AST-gated: read-only, stdlib-adjacent, must define verify(ctx)) — clean clears the warning and **deletes the staged files (use-and-delete: they are useful precisely once; keeping them would blur into check's role)**
-6. The kernel journal (`.meta/kernel-journal.log`) records install/uninstall/upgrade/warn/clear with a rolling cap of 500 lines (oldest trimmed); it is git-tracked — mechanical facts only; semantic narrative stays in wiki/log
+6. The kernel journal (`.owfa/kernel-journal.log`) records install/uninstall/upgrade/warn/clear with a rolling cap of 500 lines (oldest trimmed); it is git-tracked — mechanical facts only; semantic narrative stays in wiki/log
 
 ## Boundaries
 

package/.agents/skills/{query → owfa-query}/SKILL.md

@@ -1,11 +1,10 @@
 ---
-name: query
+name: owfa-query
 owner: framework
-consumes: [log]
 description: "Retrieve from the wiki and answer synthetically: hot cache → index → grep → read pages, producing answers with wikilink citations. Triggers on: query, what do you know about, what is, explain, find in wiki, 检索."
 ---
 
-# query: retrieval
+# owfa-query: retrieval
 
 Read-mostly; the only write action is one log line (a read signal). Layered progression — the cheapest goes first.
 
@@ -35,14 +34,14 @@ Write: log (one line only, type "query")
 ## Wrap-up
 
 - Write one log line (a read signal — this is how read popularity becomes measurable): see the log block of the injection region for how to call it
-- A log line is a data-zone change: commit immediately per the commit discipline (`检索: <topic>`, see `.meta/protocol/actions.md`); do not batch up
+- A log line is a data-zone change: commit immediately per the commit discipline (`检索: <topic>`, see `.owfa/protocol/actions.md`); do not batch up
 
 ## Injected Section (plugin usage blocks)
 
-> This region is a wiki_plugin_kernel projection: consumes pulls merged with usage_routes source-side routing; disclosure order = owner first, routed blocks in the middle, pulled blocks last (rebuilt by inject / all); handwritten content does not belong here — to change the write-side contract, edit PLUGIN.yaml.
+> This region is a owfa-kernel projection: consumes pulls merged with usage_routes source-side routing; disclosure order = owner first, routed blocks in the middle, pulled blocks last (rebuilt by inject / all); handwritten content does not belong here — to change the write-side contract, edit PLUGIN.yaml.
 
 <!-- cmd-inject:start -->
 <!-- usage:log -->
-- Writing lines (mechanical, automatic): `python .meta/scripts/pipeline.py log <type> "<one sentence>" [--domain <domain>]` (type value set in the log block of the AGENTS injection region; domain tag = domain-plugin name such as bb/lark/vault, mandatory for in-domain transactions, omitted for framework and native transactions); rolling window and archiving are performed by the script
+- Writing lines (mechanical, automatic): `python .owfa/scripts/pipeline.py log <type> "<one sentence>" [--domain <domain>]` (type value set in the log block of the AGENTS injection region; domain tag = domain-plugin name such as bb/lark/vault, mandatory for in-domain transactions, omitted for framework and native transactions); rolling window and archiving are performed by the script
 <!-- /usage:log -->
 <!-- cmd-inject:end -->

package/.owfa/VERSION

@@ -0,0 +1 @@
+0.4.0

package/.owfa/command/owfa-check/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: owfa-check
+owner: framework
+description: "Audit the repository's health: hard-structure checks on the foundation and plugins + semantic checks on plugins and pages. Triggers on: check, 健康检查, 检查插件, lint."
+---
+
+# owfa-check: repository health audit
+
+This is an audit, not a guardrail. It outputs a graded report: error = structural breakage requiring action; warning = a suggested to-do. Check rules come from two places: the foundation part of this file (protocol level) + the injection region below (a mechanical projection by owfa-kernel from each plugin manifest's checks list; presence means registration).
+
+## Purpose
+
+Run one health audit over the entire instance (foundation + plugins + wiki pages).
+
+## Scope
+
+Read: everything (.owfa/, the AGENTS.md injection region, .agents/skills/, the wiki/, vault/ directory trees)
+Write: one line in wiki/log.md (type "check"); regenerable zones are rebuilt directly per the action discipline (scripts: injection region / registry / command copies; semantics: index / tags / hot eviction / log archiving / hash recomputation)
+
+## Steps
+
+1. **Foundation hard checks** (protocol level):
+   - **Static self-check script**: `python .owfa/scripts/owfa_kernel.py validate` (directory completeness, manifest seven fields + optional commands, id consistency, dependency existence, acyclicity, command binding owner×commands bidirectional consistency) — any error means FAIL
+   - **Idempotent rebuild**: `python .owfa/scripts/owfa_kernel.py all` (injection region / registry plugin section / command copies — mechanical and automatic; drift is fixed here, the script source is the rule list)
+   - `.owfa/protocol/registry.yaml` is in place with the protocol / reserved sections intact (the script never touches these two sections; a missing section is an error)
+   - **Value-set violation**: scan the frontmatter of all wiki/ pages; a type / status value outside the registry value set → error
+   - Every `.owfa/command/` SKILL.md has frontmatter (name / description / owner; optional consumes — an ordered list of plugins whose write-side contracts are consumed; referenced plugins must be present with a usage list; mandatory for owner-driven commands)
+2. **Plugin checks**: first run the attached audit `python .owfa/scripts/owfa_kernel.py audit` (mechanical items: each plugin's scripts/check.py executed on audit discovery, read-only reporting; errors count toward FAIL); then execute the items marked "semantic" in the injection-region blocks below
+3. **Semantic checks**: read plugin and command files, looking for dangling references (a command referring to nonexistent structure), ghost fields (page fields with no owning plugin and not registry-reserved), and injection-region blocks inconsistent with the PLUGIN.md Checks section
+4. Summary output: PASS / WARN / FAIL counts + graded details + vault backlog count (informational)
+5. **Fixes are executed by grade per the action discipline** (`.owfa/protocol/actions.md`): mechanical-automatic items are done directly — `pipeline.py index` / `tags` (index rebuild), `owfa_kernel.py all` (registry / injection region / copies), hash recomputation (raw_sha256 of changed frontmatter); hot / log overflows are converged by their own write-pipeline commands; mechanical-confirmation items present a list and ask once; semantic items are reported only; historical entries are never automatically changed
+6. Prepend one line to wiki/log.md (type "check", via `pipeline.py log check "<one line>"`); if anything changed (fixes / a log line), commit per the commit discipline (`检查: <conclusion>`, see `.owfa/protocol/actions.md`)
+
+## Tools
+
+grep / file reading suffice; no second scan when one read is enough (call frugality).
+
+## Parameters
+
+- None: full-repository audit
+- Plugin id: check that plugin only
+
+## Injected Section (plugin check blocks)
+
+> This region is a owfa-kernel projection from each plugin manifest's checks list (rebuilt by `inject` / `all`; presence means registration); handwritten content does not belong here — to change check rules, edit PLUGIN.yaml.
+
+<!-- check-inject:start -->
+
+<!-- check-inject:end -->

package/{.meta/command/docs → .owfa/command/owfa-docs}/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: docs
+name: owfa-docs
 owner: framework
 description: "Docs thin-router: points to the documentation map and the behavior/feedback protocol — no norms live in this skill. Fire when the user reports dissatisfaction with agent behavior (possible plugin/kernel cause), asks where something is documented, or how to file feedback. Triggers on: docs, 查文档, 文档在哪, 框架问题, 行为自检, agent-behavior, 怎么提issue."
 ---
 
-# docs: thin router to the documentation layer
+# owfa-docs: thin router to the documentation layer
 
 S-layer pointer only — the norms live in the documents (L layer). Re-read what you cite; never quote from memory.
 
@@ -13,12 +13,12 @@ S-layer pointer only — the norms live in the documents (L layer). Re-read what
 When the user reports dissatisfaction with your behavior, do **not** launch an analysis on your own:
 
 - **Not a plugin/kernel matter** (pure conversation, execution slip)? Ignore the rest of this skill — respond to the user directly, fix in-session.
-- **Possibly a plugin or kernel problem?** First ask the user whether to run a behavior self-audit (**recommended** — it produces the evidence base for a real fix). Only on consent, follow the protocol: [`.meta/docs/agent-behavior.md`](../../docs/agent-behavior.md) — feedback handling → routing → the seven-step standard.
+- **Possibly a plugin or kernel problem?** First ask the user whether to run a behavior self-audit (**recommended** — it produces the evidence base for a real fix). Only on consent, follow the protocol: [`.owfa/docs/agent-behavior.md`](../../docs/agent-behavior.md) — feedback handling → routing → the seven-step standard.
 
 ## 2. "Where is X documented?" / "how does X work?"
 
-Read [`.meta/docs/map.md`](../../docs/map.md) — the routing table (what to read when), framework docs and package-repo docs both.
+Read [`.owfa/docs/map.md`](../../docs/map.md) — the routing table (what to read when), framework docs and package-repo docs both.
 
 ## 3. Filing feedback / issues
 
-The routing table lives in [`.meta/docs/agent-behavior.md`](../../docs/agent-behavior.md) §Routing: framework → owfa; package members → the matching `pkg-*` repo; new-plugin proposals → incubation on owfa.
+The routing table lives in [`.owfa/docs/agent-behavior.md`](../../docs/agent-behavior.md) §Routing: framework → owfa; package members → the matching `pkg-*` repo; new-plugin proposals → incubation on owfa.

package/{.meta/command/wiki_plugin_kernel → .owfa/command/owfa-kernel}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: wiki_plugin_kernel
+name: owfa-kernel
 owner: framework
-description: "Kernel and mechanics reference: the projector's subcommands (7 convergence — ls/validate/audit/inject/registry/deploy/all — plus 8 package-lifecycle: plan/install/uninstall/list-remote/migrate/upgrade/pkg/residual) + a full account of the plugin mechanics — manifest / dependencies / the three projections / command binding / bridge rules / layering principles (a bb-domain worked example). Triggers on: 插件内核, wiki_plugin_kernel, kernel, 注入块更新, 投影重建, 插件机制, 更新注入."
+description: "Kernel and mechanics reference: the projector's subcommands (7 convergence — ls/validate/audit/inject/registry/deploy/all — plus 8 package-lifecycle: plan/install/uninstall/list-remote/migrate/upgrade/pkg/residual) + a full account of the plugin mechanics — manifest / dependencies / the three projections / command binding / bridge rules / layering principles (a bb-domain worked example). Triggers on: 插件内核, owfa-kernel（旧 owfa-kernel）, kernel, 注入块更新, 投影重建, 插件机制, 更新注入."
 ---
 
-# wiki_plugin_kernel: kernel and mechanics reference
+# owfa-kernel: kernel and mechanics reference
 
-`python .meta/scripts/wiki_plugin_kernel.py <subcommand>` — the framework side's only projector: PLUGIN.yaml is the body; the AGENTS.md injection region, the check check blocks, the command usage blocks, the registry plugin section, and the command and connector skill copies are all its projections. Idempotent, runnable at any time; drift is fixed on the run. This skill also serves as the **mechanics master outline**: a deployed instance carrying only the AGENTS.md injection region + skill copies is self-sufficient; this file is the authoritative home of the mechanics on the deployment side.
+`python .owfa/scripts/owfa_kernel.py <subcommand>` — the framework side's only projector: PLUGIN.yaml is the body; the AGENTS.md injection region, the check check blocks, the command usage blocks, the registry plugin section, and the command and connector skill copies are all its projections. Idempotent, runnable at any time; drift is fixed on the run. This skill also serves as the **mechanics master outline**: a deployed instance carrying only the AGENTS.md injection region + skill copies is self-sufficient; this file is the authoritative home of the mechanics on the deployment side.
 
 ## Subcommands
 
@@ -17,10 +17,10 @@ description: "Kernel and mechanics reference: the projector's subcommands (7 con
 | `audit` | attached audit: executes each plugin's `scripts/check.py` on discovery, read-only report (may take a plugin id to check just one) | none |
 | `inject` | rebuilds the three projections: the AGENTS injection region + the check check blocks + the command usage blocks | AGENTS.md, command SKILL.md files containing injection regions |
 | `registry` | rebuilds the registry.yaml plugin section (from each manifest's `fields`) | registry.yaml |
-| `deploy` | syncs skill masters (`.meta/command/*/` commands + `connectors/*/` connectors) → `.agents/skills/` copies; orphan copies are reported only (deletion belongs to the human) | copies |
+| `deploy` | syncs skill masters (`.owfa/command/*/` commands + `connectors/*/` connectors) → `.agents/skills/` copies; orphan copies are reported only (deletion belongs to the human) | copies |
 | `all` | validate + inject + registry + deploy in one step | all of the above |
 
-Package lifecycle (full wizard protocol and judgment rules: `.meta/command/plugin/SKILL.md`):
+Package lifecycle (full wizard protocol and judgment rules: `.owfa/command/plugin/SKILL.md`):
 
 | Subcommand | Purpose | Disk writes |
 |---|---|---|
@@ -33,19 +33,19 @@ Package lifecycle (full wizard protocol and judgment rules: `.meta/command/plugi
 | `pkg` | installed packages: members, versions, connectors | none |
 | `residual <pkg>` | anchor-surface reference scan (the default teardown gate) | none |
 
-The kernel journal (`.meta/kernel-journal.log`, rolling cap of 500 lines, git-tracked) records the mechanical chain — install / warn+ / clear / uninstall / sweep; mechanical facts only, semantic narrative stays in the instance wiki's log.
+The kernel journal (`.owfa/kernel-journal.log`, rolling cap of 500 lines, git-tracked) records the mechanical chain — install / warn+ / clear / uninstall / sweep; mechanical facts only, semantic narrative stays in the instance wiki's log.
 
 ## Typical scenarios
 
-- **PLUGIN.yaml changed** (inject / checks / usage / fields / version): `python .meta/scripts/wiki_plugin_kernel.py all` — the daily standard action; one command converges everything; if validate fails it blocks — fix and rerun
-- **Only refreshing injection blocks**: `inject` suffices, but note it modifies the `.meta/command/` masters; copies sync only via `deploy` — hence always use `all` in daily work
+- **PLUGIN.yaml changed** (inject / checks / usage / fields / version): `python .owfa/scripts/owfa_kernel.py all` — the daily standard action; one command converges everything; if validate fails it blocks — fix and rerun
+- **Only refreshing injection blocks**: `inject` suffices, but note it modifies the `.owfa/command/` masters; copies sync only via `deploy` — hence always use `all` in daily work
 - **Quick health check**: `validate` (structure) + `audit` (attached audit); a full audit (including semantic items) goes through the check command
 - **(Un)installing plugins**: the semantic flow (decisions, directory archiving, log line) goes through the plugin command; the mechanical steps inside it are exactly this CLI's `validate` / `all` / `audit`
-- **Connector skill changed** (`connectors/*/SKILL.md` master): run `deploy` (or `all`) to sync copies — connector skills never enter `.meta/command/` (the command family is pure wiki operation)
+- **Connector skill changed** (`connectors/*/SKILL.md` master): run `deploy` (or `all`) to sync copies — connector skills never enter `.owfa/command/` (the command family is pure wiki operation)
 
 ## Plugin shape
 
-- **One plugin, one directory** (`.meta/plugins/<id>/`): `PLUGIN.yaml` (the manifest, the machine-readable body) + `PLUGIN.md` (pure documentation: design summary (why / family position / key rulings and rejected alternatives) / Structure / Invariants / Changelog — **design rationale and per-plugin details belong here**; mechanics commonalities belong to this reference) + optional `scripts/check.py` (attached audit)
+- **One plugin, one directory** (`.owfa/plugins/<id>/`): `PLUGIN.yaml` (the manifest, the machine-readable body) + `PLUGIN.md` (pure documentation: design summary (why / family position / key rulings and rejected alternatives) / Structure / Invariants / Changelog — **design rationale and per-plugin details belong here**; mechanics commonalities belong to this reference) + optional `scripts/check.py` (attached audit)
 - **Manifest keys**: seven required keys `id / version / depends / updated / attachment / fields / inject`; optional `commands` (command names this plugin drives), `usage` (write-side contract list — the third projection source), `checks` (check-rule list — the check projection source), `bridge` (bridge declaration, see bridge rules), `inject_tier` (injection tier, see tier law below)
 - **attachment** = declares territory and borrow-read relationships (who owns which paths, who read-only consumes whose pages); **fields** = owned page fields (enter the registry, the global vocabulary); **inject** = the plugin's disclosure, one line (the full-disclosure home in the manifest either way; known to the agent the moment it enters the repository when tier is full, read on demand when tier is member)
 - **Attached-audit contract**: `scripts/check.py` defines `check(ctx)` returning `[{level, message}]`; read-only with zero side effects; fixes belong to commands/humans; an AST static check validates the contract's shape
@@ -61,7 +61,8 @@ The kernel journal (`.meta/kernel-journal.log`, rolling cap of 500 lines, git-tr
 
 - **`inject_tier: full | member`** (optional, default full): **full** projects into the AGENTS.md injection region; **member** exits it — exposure rides on the family root's roster line (every member named with id + one phrase), the skill catalog (trigger-surface awareness), and L-layer reads (the manifest `inject` field stays the full-disclosure home either way)
 - Validate requires a member to reach a **full-tier domain root** through depends (family membership, else it exits into invisibility)
-- The projected plugin blocks carry a **byte budget** (15 KiB, derived from the smallest mainstream whole-file AGENTS.md cap minus handwritten allowance): over-budget is a validate error — compress pointer lines or re-tier domain members; the A layer holds pointers and red lines only, never procedures or formats (content contract in `protocol/experiments.md`)
+- The projected plugin blocks carry a **byte budget** (16 KiB, derived from the smallest mainstream whole-file AGENTS.md cap minus handwritten allowance): over-budget is a validate error — compress pointer lines or re-tier domain members; the A layer holds pointers and red lines only, never procedures or formats (content contract in `protocol/experiments.md`)
+- Each full-tier `inject` line has a **pointer-density guideline** (256 B, `INJECT_LINE_GUIDE`, issue #49): a longer line is a validate warning, never an error — write path + read/write trigger + the one easy-to-break invariant + a pointer to PLUGIN.md; detail moves to PLUGIN.md / usage / skills
 
 ## Command-plugin binding
 

package/{.agents/skills/plugin → .owfa/command/owfa-plugin}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: plugin
+name: owfa-plugin
 owner: framework
-description: "Package & plugin lifecycle management: plan (disclosure wizard), install (three channels + --without subsets), uninstall, list-remote, upgrade, pkg, residual. Mechanical steps all go through .meta/scripts/wiki_plugin_kernel.py; the agent runs the consent conversation and the one-shot commands. Triggers on: plugin, 插件, 装插件, 卸插件, 装包, install package, uninstall package."
+description: "Package & plugin lifecycle management: plan (disclosure wizard), install (three channels + --without subsets), uninstall, list-remote, upgrade, pkg, residual. Mechanical steps all go through .owfa/scripts/owfa_kernel.py; the agent runs the consent conversation and the one-shot commands. Triggers on: plugin, 插件, 装插件, 卸插件, 装包, install package, uninstall package."
 ---
 
-# plugin: package lifecycle
+# owfa-plugin: package lifecycle
 
-The framework's self-management command, package era (issue #20). Every mechanical step goes through the kernel script; the agent's job is **consent and choice** — never writing `.meta/` by hand.
+The framework's self-management command, package era (issue #20). Every mechanical step goes through the kernel script; the agent's job is **consent and choice** — never writing `.owfa/` by hand.
 
 ## Scope
 
@@ -17,10 +17,10 @@ Read: INDEX via the kernel, PKG.yaml, manifests
 
 When a user asks to install a package and has NOT already specified what to include:
 
-1. `python .meta/scripts/wiki_plugin_kernel.py plan <pkg>` — one-shot disclosure plan: trust line, package disclosure (network/privacy/credentials, package-authored), baseline (the family root, always installed), optional members with one-line summaries and what each selection pulls in, connectors
+1. `python .owfa/scripts/owfa_kernel.py plan <pkg>` — one-shot disclosure plan: trust line, package disclosure (network/privacy/credentials, package-authored), baseline (the family root, always installed), optional members with one-line summaries and what each selection pulls in, connectors
 2. Relay the plan **in the user's language** (render at the agent layer per wiki/language.md — canonical texts are English; the agent translates when relaying, never edits the source)
 3. Walk the steps: trust + disclosure → user acknowledges; optional members → user picks (each pick auto-pulls its dependency closure — show the resolved final set, users cannot compose an illegal subset); connectors → confirm (they ride the package)
-4. Execute: `python .meta/scripts/wiki_plugin_kernel.py install <pkg> --without <unwanted> [--yes]`
+4. Execute: `python .owfa/scripts/owfa_kernel.py install <pkg> --without <unwanted> [--yes]`
 5. Report the convergence output (validate/inject/registry/deploy) in one breath
 
 ## One-shot path (agent / pre-authorized)
@@ -28,8 +28,8 @@ When a user asks to install a package and has NOT already specified what to incl
 If consent already exists (user named exactly what they want, or pre-authorized), skip the conversation:
 
 ```
-python .meta/scripts/wiki_plugin_kernel.py plan <pkg> --json        # machine-readable plan (optional)
-python .meta/scripts/wiki_plugin_kernel.py install <pkg> [--without a,b] [--yes]
+python .owfa/scripts/owfa_kernel.py plan <pkg> --json        # machine-readable plan (optional)
+python .owfa/scripts/owfa_kernel.py install <pkg> [--without a,b] [--yes]
 ```
 
 Kernel commands never prompt — every invocation completes in one shot.
@@ -58,12 +58,12 @@ Every package transaction (install / uninstall / upgrade apply / migrate clear)
 
 Mechanical sync is only half an update. When a new version carries `migrations/`:
 
-1. The kernel stages declarations into `.meta/migrations/<pkg>/` (kernel zone — never inside the package dir), registers the warning ledger, and raises the **tri-face warning**: every kernel invocation prints the pending banner · `validate` stays red (mechanical blessing withheld) · a kernel-managed block lands in the AGENTS injection region so every session sees it
+1. The kernel stages declarations into `.owfa/migrations/<pkg>/` (kernel zone — never inside the package dir), registers the warning ledger, and raises the **tri-face warning**: every kernel invocation prints the pending banner · `validate` stays red (mechanical blessing withheld) · a kernel-managed block lands in the AGENTS injection region so every session sees it
 2. `kernel migrate <pkg>` prints the staged declarations (init or version-chain) — relay them in the user's language
 3. Perform the semantic transformation via the normal command surfaces (confirmation gates as always); **judgment split rule**: assertions that hold only during the transition belong in the author's verify script (dies with the migration); assertions that hold forever belong in `scripts/check.py` (same release)
 4. **Subset matching**: declarations and verifies address the **installed subset**, never the full roster — steps marked `(member: X)` run only when X is installed; verify scripts guard member-specific assertions with `ctx.installed` (the kernel passes it); the ledger records the staging-time subset
 5. `kernel migrate <pkg> --clear` runs the author verify (AST-gated: read-only, stdlib-adjacent, must define verify(ctx)) — clean clears the warning and **deletes the staged files (use-and-delete: they are useful precisely once; keeping them would blur into check's role)**
-6. The kernel journal (`.meta/kernel-journal.log`) records install/uninstall/upgrade/warn/clear with a rolling cap of 500 lines (oldest trimmed); it is git-tracked — mechanical facts only; semantic narrative stays in wiki/log
+6. The kernel journal (`.owfa/kernel-journal.log`) records install/uninstall/upgrade/warn/clear with a rolling cap of 500 lines (oldest trimmed); it is git-tracked — mechanical facts only; semantic narrative stays in wiki/log
 
 ## Boundaries
 

package/{.meta/command/query → .owfa/command/owfa-query}/SKILL.md

@@ -1,11 +1,10 @@
 ---
-name: query
+name: owfa-query
 owner: framework
-consumes: [log]
 description: "Retrieve from the wiki and answer synthetically: hot cache → index → grep → read pages, producing answers with wikilink citations. Triggers on: query, what do you know about, what is, explain, find in wiki, 检索."
 ---
 
-# query: retrieval
+# owfa-query: retrieval
 
 Read-mostly; the only write action is one log line (a read signal). Layered progression — the cheapest goes first.
 
@@ -35,14 +34,14 @@ Write: log (one line only, type "query")
 ## Wrap-up
 
 - Write one log line (a read signal — this is how read popularity becomes measurable): see the log block of the injection region for how to call it
-- A log line is a data-zone change: commit immediately per the commit discipline (`检索: <topic>`, see `.meta/protocol/actions.md`); do not batch up
+- A log line is a data-zone change: commit immediately per the commit discipline (`检索: <topic>`, see `.owfa/protocol/actions.md`); do not batch up
 
 ## Injected Section (plugin usage blocks)
 
-> This region is a wiki_plugin_kernel projection: consumes pulls merged with usage_routes source-side routing; disclosure order = owner first, routed blocks in the middle, pulled blocks last (rebuilt by inject / all); handwritten content does not belong here — to change the write-side contract, edit PLUGIN.yaml.
+> This region is a owfa-kernel projection: consumes pulls merged with usage_routes source-side routing; disclosure order = owner first, routed blocks in the middle, pulled blocks last (rebuilt by inject / all); handwritten content does not belong here — to change the write-side contract, edit PLUGIN.yaml.
 
 <!-- cmd-inject:start -->
 <!-- usage:log -->
-- Writing lines (mechanical, automatic): `python .meta/scripts/pipeline.py log <type> "<one sentence>" [--domain <domain>]` (type value set in the log block of the AGENTS injection region; domain tag = domain-plugin name such as bb/lark/vault, mandatory for in-domain transactions, omitted for framework and native transactions); rolling window and archiving are performed by the script
+- Writing lines (mechanical, automatic): `python .owfa/scripts/pipeline.py log <type> "<one sentence>" [--domain <domain>]` (type value set in the log block of the AGENTS injection region; domain tag = domain-plugin name such as bb/lark/vault, mandatory for in-domain transactions, omitted for framework and native transactions); rolling window and archiving are performed by the script
 <!-- /usage:log -->
 <!-- cmd-inject:end -->

package/{.meta → .owfa}/docs/agent-behavior.md

@@ -17,8 +17,9 @@ This face was previously undeclared (an e-class vacuum live sample, #33's improv
 
 | Feedback | Destination | Test |
 |---|---|---|
-| kernel / mechanics / projections / core plugins / framework docs | owfa | framework contract face |
-| package member plugins (the bb family, the lark family, …) | the matching `pkg-*` repo | plugin id ∈ `PKG.members`; repo address in the registry INDEX |
+| kernel / mechanics / projections / framework docs | owfa | framework contract face |
+| core-suite plugins (the former framework plugins, now owfa-personal members) | the **owfa-personal** repo (since the v0.4 split) | plugin id ∈ owfa-personal `PKG.members` |
+| package member plugins (the bb family, the lark family, …) | the matching `owfa-*` repo | plugin id ∈ `PKG.members`; repo address in the registry INDEX |
 | behavior deviations (the #34 face) | wherever the plugin lives | behavior contracts live in PLUGIN.md |
 | new plugin proposals | owfa (incubation; moves with the package when it lands) | no owning repo yet |
 | unclear | file on owfa; maintainers transfer | fallback (#20 precedent) |

package/{.meta → .owfa}/docs/agents-example.md

@@ -11,7 +11,7 @@ rewritten freely — the agent never edits outside the injection region.>
 ## Layout
 
 <vault root>: `vault/` real assets · `wiki/` the md world
-· `.meta/` + `.agents/skills/` the framework body (packages under `.meta/plugins/domains/`).
+· `.owfa/` + `.agents/skills/` the framework body (packages under `.owfa/plugins/domains/`).
 
 ## Git
 

package/{.meta → .owfa}/docs/conversion.md

@@ -5,8 +5,8 @@
 ## Eight steps
 
 1. **Baseline commit** at the instance root — the rollback anchor
-2. **Survey**: `ls .meta/plugins` (a flat list = legacy), `ls .meta/command`, `ls .agents/skills` — note any *non-framework* skills you keep (the drill kept `dsh-token`)
-3. **Swap the framework trees**: delete `.meta/{plugins,command,scripts,protocol,docs}` and the framework entries of `.agents/skills/` (keep your own tool skills); copy in the template's `.meta/{plugins,command,scripts,protocol,docs,VERSION}` and `.agents/skills/*`. Data zones (`wiki/`, `vault/`, domain data directories), `connectors/`, `AGENTS.md`, `.gitignore` are never touched
+2. **Survey**: `ls .owfa/plugins` (a flat list = legacy), `ls .owfa/command`, `ls .agents/skills` — note any *non-framework* skills you keep (the drill kept `dsh-token`)
+3. **Swap the framework trees**: delete `.owfa/{plugins,command,scripts,protocol,docs}` and the framework entries of `.agents/skills/` (keep your own tool skills); copy in the template's `.owfa/{plugins,command,scripts,protocol,docs,VERSION}` and `.agents/skills/*`. Data zones (`wiki/`, `vault/`, domain data directories), `connectors/`, `AGENTS.md`, `.gitignore` are never touched
 4. **Converge**: `kernel all` — core 21 green; the AGENTS injection region rebuilds wholesale (the old flat blocks are replaced)
 5. **Install packages**: `kernel list-remote`, then `kernel install <pkg> --yes` per package. Connectors already present are **kept existing** (running venvs survive; connector code updates arrive via uninstall+install of the owning package)
 6. **Clear the inits**: `kernel migrate <pkg>` prints each declaration; a real instance usually already satisfies the verify criteria (identity / profile / declaration pages exist on real assets) → `kernel migrate <pkg> --clear`