@mestreyoda/fabrica 0.2.11 → 0.2.13

package/ARCHITECTURE.md

@@ -63,17 +63,23 @@ Important invariants:
 
 ## Installation model
 
-The supported local installation is path-based:
+Fabrica is distributed as a self-contained OpenClaw plugin package.
+
+The supported operator path is:
 
 ```bash
-openclaw plugins install -l /path/to/fabrica
+openclaw plugins install @mestreyoda/fabrica
 ```
 
-That means:
+The installed extension must be loadable in isolation. Fabrica may depend on
+OpenClaw only through the plugin host ABI and runtime objects passed by the
+host. It must not require manual symlinks, local `npm install`, or host-global
+module resolution to load.
 
-- the repository stays editable in place
-- the installed plugin points back to this directory
-- the loaded runtime should match the local build output in `dist/`
+External credentials and routes such as GitHub auth, Telegram chat IDs, and
+webhook secrets are operational configuration, not installation dependencies.
+Fabrica's `doctor` and `setup` flows guide and validate that operational
+configuration where applicable.
 
 ## Operational notes
 

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## 0.2.13 - 2026-03-31
+
+- Disabled automatic pretty logging on TTY so the plugin no longer depends on `pino-pretty` during load.
+- Added a safe one-shot fallback to structured logs when pretty transport resolution or initialization fails.
+- Added logger transport regression coverage and promoted it into the hot-path test lane.
+
+## 0.2.12 - 2026-03-31
+
+- Made the published plugin self-contained by replacing remaining runtime helper imports from `openclaw/plugin-sdk`.
+- Added release gates for runtime-boundary and isolated installability verification, with fail-closed behavior, timeouts, and cleanup.
+- Documented the real install contract and workspace-scoped operational setup flow in the package README and architecture notes.
+- Aligned local deploy to the same contract by removing the extension `node_modules` symlink fallback.
+
 ## 0.2.11 - 2026-03-31
 
 - Unified reviewer completion around the canonical `Review result: APPROVE|REJECT` contract.

package/README.md

@@ -64,6 +64,9 @@ The heartbeat ticks every 60 seconds. On each tick, Fabrica alternates between a
 openclaw plugins install @mestreyoda/fabrica
 ```
 
+That install should be enough for OpenClaw to load Fabrica immediately, without
+manual remediation.
+
 ### Via GitHub clone
 
 ```bash
@@ -74,35 +77,53 @@ openclaw plugins install -l ~/fabrica
 After installation, verify the plugin loaded correctly:
 
 ```bash
-openclaw plugins list
-openclaw fabrica doctor
+openclaw plugins inspect fabrica
 ```
 
+## Loadability vs operational readiness
+
+- **Loadable:** the plugin installs and OpenClaw can load it immediately.
+- **Operational:** Fabrica has the GitHub, Telegram, and optional webhook
+  configuration needed for your workflow.
+
+`openclaw plugins inspect fabrica` is the loadability check after install.
+`openclaw fabrica doctor` runs once the plugin is loaded and checks the
+operational/workspace state, then tells you what is still missing.
+
 ## Quick start
 
-**1. Enable the plugin** in `~/.openclaw/openclaw.json`:
+**1. Install Fabrica**:
 
-```json
-{
-  "plugins": {
-    "entries": {
-      "fabrica": {
-        "enabled": true
-      }
-    }
-  }
-}
+```bash
+openclaw plugins install @mestreyoda/fabrica
+```
+
+The plugin should load immediately after install, without manual remediation.
+
+**2. Confirm loadability**:
+
+```bash
+openclaw plugins inspect fabrica
+```
+
+**3. Configure operational state for a workspace**:
+
+```bash
+openclaw fabrica doctor workspace --workspace /path/to/workspace
+openclaw fabrica setup --workspace /path/to/workspace --new-agent fabrica
 ```
 
-For polling-first GitHub usage via authenticated `gh`, no extra plugin config is required. Fabrica's plugin config is only for control-plane settings such as heartbeat cadence, Telegram routing, notifications, and provider/webhook auth. Worker models, levels, and workflow routing live in the workspace files and can be generated or updated with `openclaw fabrica setup`.
+Use `openclaw fabrica setup --agent <id>` if you already have an agent. GitHub,
+Telegram, and webhook behavior are separate operational concerns, not
+installation dependencies.
 
-**2. Restart the gateway**:
+**4. Restart the gateway**:
 
 ```bash
 systemctl --user restart openclaw-gateway.service
 ```
 
-**3. Trigger a new project programmatically**:
+**5. Trigger a new project programmatically**:
 
 ```bash
 cd ~/fabrica  # GitHub clone install only
@@ -114,13 +135,13 @@ npx tsx scripts/genesis-trigger.ts "A CLI tool that counts words in a file" \
 
 Remove `--dry-run` to execute for real.
 
-**4. Watch the pipeline run**:
+**6. Watch the pipeline run**:
 
 ```bash
 tail -f ~/.openclaw/workspace/logs/genesis.log
 ```
 
-**5. Check metrics**:
+**7. Check metrics**:
 
 ```bash
 openclaw fabrica metrics