@plurnk/plurnk-meta 1.3.2 → 1.3.4

package/.env.defaults

@@ -13,3 +13,7 @@
 # telemetry note, never a crash). Use 1 (a value naming no real package) for
 # "on, zero third-party". Example: =acme-execs-cobol,@firewolf/firepad
 PLURNK_PLUGINS_TRUSTED_ONLY=0
+
+# Whole-product orientation deadline in seconds. This includes exhaustive semantic
+# preparation of the admitted repository forest before the model is called.
+PLURNK_ACCEPTANCE_TIMEOUT=3600

package/CORPUS.md

@@ -10,7 +10,7 @@ The plurnk teaching corpus. Markdown consumed by [plurnk-service](https://github
 
 ## The teaching split
 
-**Grammar teaches the language; docs teaches the world.** [plurnk-grammar](https://github.com/plurnk/plurnk-grammar)'s `plurnk.md` owns op syntax and the DSL (GBNF-coupled, moves with the grammar). This package owns scheme behavior, delegation workflow, disposition, and standing rules — the corpus tuned against live model behavior (steer wording, weak-model teaching, pressure habits).
+**Grammar teaches the language; docs teach the world.** [plurnk-grammar](https://github.com/plurnk/plurnk-grammar)'s ANTLR grammar and `plurnk.md` own op syntax and the model-facing language. This package owns scheme behavior, delegation workflow, disposition, and standing rules — the corpus tuned against live model behavior (steer wording, weak-model teaching, pressure habits).
 
 ## Contract
 
@@ -23,4 +23,3 @@ plurnk-service resolves these files from this package (`Paths`), pins the versio
 **The requiem acceptance gate.** Teaching changes ship against BEFORE/AFTER corpus deltas (reasoning-token + requiem-recurrence), never hunches. Triage separates legibility debt from load-bearing discipline pain: the FOLD/KILL burden, the compression, and the dialect count are the PRODUCT (the model curating its own context) — never sanded off because models complain. A re-probe against >=0.76.5 is owed (grammar lane).
 
 **Example doctrine (Arecibo teaching).** Concrete over placeholder — a live model spawned a worker literally named 'name' from a (worker://name) table cell within a day of shipping; placeholders in reserved-bracket forms are doubly banned. Bare-gesture register per section — op-teaching lines carry the gesture, the mechanism stays the engine's; match the surrounding register. Distribution is load-bearing — clustered examples teach false couplings; rebalance coverage, never add runtime prose. TIME is a distribution axis — dynamics teach as protocol-accurate worked multi-turn traces (the Delegation breath), never prose essays; an inaccurate trace (same-turn READ+200) models the wrong protocol.
-

package/DOGFOOD.md

@@ -1,6 +1,29 @@
-# Whole-product dogfood gate
+# Metaproject agentic-readiness gate
 
-This is the release-defining acceptance gate for PLURNK as a daily-driver agent system. It tests the assembled product through the outside client; it does not replace package installation, deterministic integration, live-model, or benchmark gates.
+This is an opt-in milestone qualification for using PLURNK to develop the complete
+PLURNK metaproject. It is intentionally expensive: a fresh run semantically
+prepares the complete repository forest before asking a floor model to orient
+itself through the outside client. Run it when the focused package, integration,
+demo, live-model, and modest-candidate paths are already healthy—not as a routine
+debugging loop or ordinary release gate.
+
+Invoke it with:
+
+```sh
+npm run readiness:metaproject -- --model <alias> --requiem --preserve
+```
+
+This gate does not replace the evidence ladder that qualifies it:
+
+1. Deterministic package and integration coverage proves owned contracts.
+2. An assembled modest-repository candidate smoke proves the production client
+   and daemon can work together.
+3. Focused `live/demo` stories are toy tasks that establish the system is sane
+   enough to test seriously.
+4. The separate bench lane runs real third-party agentic benchmarks and preserves
+   their digest, reasoning, and requiem evidence.
+5. Only after those layers are healthy does this full-forest run ask whether
+   PLURNK is ready to develop PLURNK itself.
 
 The gate belongs to `plurnk-meta` because it crosses family ownership: canonical service installation, optional-provider assembly, the outside client, project membership, AG-UI, proposal review, model routing, persistence, and forensic digestion.
 

package/PLURNK_PERSONALITY.md

@@ -12,6 +12,7 @@
 - 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 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.
+- **MODE:** Your continuing turn's ops follow the MODE Pattern: Mutate state, Observe the result, Do actions, End the turn.
 - **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.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@plurnk/plurnk-meta",
-    "version": "1.3.2",
+    "version": "1.3.4",
     "description": "The plurnk metaproject layer, published: plugin-membership primitives (the ONE trust rule, scope-agnostic symlink-aware enumeration, deployment-root resolution), the project teaching corpus (personality, requirements, scheme docs), and the home for family tooling.",
     "license": "MIT",
     "type": "module",