@plurnk/plurnk-meta 1.0.8 → 1.1.0

package/DIVERGENCES.md

@@ -19,5 +19,9 @@ Doctrine (owner, 2026-07-13): industry standard unless informed, explicit except
 | 13 | API stability posture | Pre-external-adopter ecosystems churn routinely; stability is DECLARED when outsiders arrive, not performed before | Lockstep 1.0.x numbering with routine fail-forward breaks; majors reserved for a deliberate stability declaration | **CONVERGED 2026-07-13 (#402, owner-instigated)** — the earlier "plugin break = platform MAJOR" rule was performative maturity, retired. |
 | 14 | Reasoning default | Reasoning-capable models default reasoning-on | `REASONING=adaptive` shipped floor | **CONVERGED 2026-07-13** (owner ruling). |
 | 15 | Git in a sandboxed agent | Environment isolation (container/microVM → real git in the box) or no-shell/in-process (isomorphic-git, e.g. WebContainers where the git binary is absent) | Capability-level sandbox → `EXEC[git]` is **isomorphic-git** (in-process, no subprocess); full git via the `EXEC:git …` sh fallthrough, gated on the deployment granting a shell; the `EXEC[gh]` tag/package purged; core repo-management moved onto iso-git | **EXCEPTION — owner-ruled 2026-07-16 (#460).** plurnk sandboxes at the capability level (tag policy, on-host, no per-op container), placing it in the no-shell/in-process class: a raw-git CLI tag is a *false sandbox* (escapes via `git config alias '!sh'`, hooks, `-c core.pager`, `filter-branch --tree-filter`), so in-process iso-git is the forced correct answer. Extends the tag-bar (execs#21 / #350): a capability tag is earned only by a genuine in-process capability the sh fallthrough can't provide (sqlite, wasm, iso-git); CLI-wrapping tags (git, gh, go, cargo) never earn one — they ARE the sh fallthrough. Scope: dev-infra git (lane worktrees, the pre-push gate) stays real-git-CLI on the trusted box — iso-git has no worktree support. |
+| 16 | Management / control plane | AG-UI models agent runs only; servers expose management (list/create/rename/fork threads, constraints, config) via a SEPARATE REST/RPC API alongside the run stream | Management verbs ride the AG-UI run envelope — `forwardedProps.plurnk.action` in, `CUSTOM plurnk.action.result` out; one endpoint, one connection, one auth boundary | **EXCEPTION — owner-ruled 2026-07-18 (#475).** One-wire, no side-channel. Convergence has no target (AG-UI has no management-plane concept), so a separate API is MORE bespoke, not less; the row ratifies the exclusive-portal consolidation that DELETED the WS/`/plurnk/rpc` side-channel. Zero conformance cost — rides the sanctioned `forwardedProps` + `CUSTOM` extension points, invisible to generic clients (no standard event translated away), serves the dumb-client one-socket posture. **Convergence trigger:** if AG-UI adds a native management/control-plane concept, this flips to a convergence item. |
+
+| 17 | Internal resource addressing | Agent frameworks address internal state via opaque IDs, file paths, or per-server MCP resource URIs; no prevailing principal model | Actor addressing: one knowledge scheme (`worker://`) with the principal in the URI authority (empty=commons, `~`=self, name=ancestry-read, `plurnk`=kernel); `prompt:///`/`log:///` self-only; open-ended capability schemes | **EXCEPTION — owner-ruled 2026-07-19 (#527).** Ownership rode pathnames and leaked ids (#526); the authority slot is the URL-native principal carrier the model already reads fluently. Trust keys on owner (write-scoping), never on scheme. Retired the `known`/`unknown` epistemology experiment (owner-concluded) and `plurnk://`/`exec://` with it. |
+| 18 | Enterprise/private split | Closed-core or full-SaaS: enterprise features live in private forks/services that reimplement the open engine | Thin private overlay over the public engine — mechanism public, decision and values private; the endpoint composes `@plurnk/plurnk-aliases`/`instantiateProvider`, owns only money/pricing/flex-decision/corpus/tuning-values | **EXCEPTION — owner-ruled 2026-07-19 (#533).** A parallel private engine is a drift tax (endpoint#19: two weeks of stale grammar from a privately-pinned copy). Push everything that isn't genuinely enterprise-secret into the public family, where lockstep, sweeps, and gates reach it by construction. |
 
 Maintenance: new divergences get a row before they ship; a PROPOSED ruling converts on owner sign-off (recorded on #400).

package/PLURNK_PERSONALITY.md

@@ -1,4 +1,4 @@
-- You decompose non-trivial prompts into taxonomized, tagged, and topical unknown:/// entries to resolve before acting.
+- You decompose non-trivial prompts into taxonomized, tagged, and topical worker:/// entries to resolve before acting.
 - You are concerned with user alignment, documentation alignment, specification alignment, and coverage alignment.
 - You don't code in response to inquiries and exploratory, open questions. You patiently educate, inquire, and align.
 - You ignore emotional subtext, sarcasm, and tone. You never apologize, but you are quick to affirm if you were incorrect.
@@ -9,9 +9,9 @@
 - You trust internal contracts, only building robust guards against bugs on external surfaces.
 - You disregard ambient updates on the state of your environment unless they pertain to your current focus.
 - Your commits add yourself, `Plurnk <plurnk@pm.me>` to the trailer. Branch freely, then merge if solo and PR if in a team.
-- **Knowledgebase:** Curate a taxonomized, tagged, and topical mind map of everything known:/// about the project.
+- **Knowledgebase:** Curate a taxonomized, tagged, and topical worker:/// mind map of everything known about the project.
 - **Plan:** Write a markdown checklist `- [x] Step 1\n- [ ] Step 2\n` in PLAN to list your prerogatives and priorities.
-- **Project:** Maintain a worker://self/project.md of project conventions, patterns, practices, and preferences.
+- **Project:** Maintain a worker://~/project.md of project conventions, patterns, practices, and preferences.
 - **Log:** Distill everything that's not relevant to your current concern and pack it where you can find it later.
 - **Context:** Your Active Context is your workbench. FOLD, KILL, and distill to the knowledgebase to keep it relevant.
 - **Errors:** READ the row the error points at. You can OPEN the "model" log item to find your mistake.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@plurnk/plurnk-meta",
-    "version": "1.0.8",
+    "version": "1.1.0",
     "description": "The plurnk metaproject layer, published: plugin-membership primitives (the ONE trust rule, scope-agnostic symlink-aware enumeration, deployment-root resolution), the family teaching corpus (personality, requirements, scheme docs), and the home for family tooling.",
     "license": "MIT",
     "type": "module",
@@ -34,7 +34,8 @@
         "test": "npm run test:lint && npm run test:unit",
         "build:dist": "tsc -p tsconfig.build.json",
         "build": "npm run build:dist",
-        "prepack": "npm run build"
+        "prepack": "npm run build",
+        "prepublishOnly": "npm outdated && npm audit --audit-level=moderate && npm test"
     },
     "publishConfig": {
         "access": "public"