@nebutra/forge-runtime
v0.1.3
Published
Nebutra Forge capability registry, invoke pipeline, pure tools, and human page models
Readme
@nebutra/forge-runtime
Status: WIP — registry + dual-surface invoke ship; product host apps/forge is live (remaining gaps in package.json nebutra.gaps).
Hard-correct gate (docs/plans/tools/_hard-correct-decisions.md):
- No lab/shell tools in the product registry
- CSS minify = CSSO, format = Prettier, HTML minify = html-minifier-terser, SVG = SVGO, UA = ua-parser-js
- Still deferred: kinship, phone-lookup, router-translate (W6)
- Host wallet: production default CreditLedger; md-to-pdf fails closed without Chromium
Capability registry and invoke pipeline for Nebutra Forge (forge.nebutra.com).
- F0 batch-1 tools (word count, base64, URL codec, JSON format, SHA-256, UUID, unix timestamp, case convert)
ForgeRegistry— list / search / categories / get by id or sluginvokeTool— validate input → execute → meter metadatabuildToolPageModel/buildCategoryHub— human tool-station page data (framework-agnostic)
Usage
import { ForgeRegistry, invokeTool, buildToolPageModel } from "@nebutra/forge-runtime";
const registry = ForgeRegistry.openDefault();
const result = await invokeTool(registry, {
toolId: "text/word-count",
input: { text: "你好 world" },
});
const page = buildToolPageModel(registry, "word-count");
// page.path === "/t/word-count"
// page.api.exampleCurl — Agent surfaceDesign
- Parent:
docs/plans/2026-07-23-nebutra-router-forge-design.md - Catalog:
docs/plans/2026-07-23-nebutra-forge-f0-catalog.md - Impl plan PR-E:
docs/plans/2026-07-23-nebutra-router-forge-implementation-plan.md
