For AI agents: the complete documentation index is available at https://scriptedalchemy.github.io/agent-bundle/llms.txt, the full documentation bundle is available at https://scriptedalchemy.github.io/agent-bundle/llms-full.txt, and this page is available as Markdown at https://scriptedalchemy.github.io/agent-bundle/reference/index.md.
Skip to main content
agent-bundle
  • English

      • Reference

      Use the Guide to build a plugin and this section to check exact fields, flags, defaults and boundaries. The target and capability map is the short route to all five built-in outputs and the functionality they can project.

      PageAnswers
      Target and capability mapWhich surface to author; native target versus compatible reader versus development/display support.
      CLICommands, arguments, options, defaults and exit codes, including inspection, hooks, MCP, installation and local App hosting.
      Configurationagent-bundle.config.ts fields, types and validation rules.
      Targets and artifactsAll five built-in projection layouts, composition constraints, distribution forms and executable ownership.
      Artifact manifestThe canonical application, route, executable, launch, distribution and compiler record shapes.
      Host capability matrixPinned versions, native documents, installation, path tokens, MCP behavior, lineage, plugin components and recorded compatible clients. Generated from adapter capability data.
      Event and hook matrixCanonical event families, native events, payload-field provenance, tool selectors and deferred native events. Generated from the same records.
      Notice delivery matrixRecipient axes, supported channels, sensitivity constraints and unavailable-delivery reasons. Generated from the same records.
      Diagnostics referenceDiagnostic codes, severity, trigger and recovery. Generated from the repository contract.
      Development-server HTTPInvocation, trace, raw-log and hook-receipt routes for advanced integrations.
      Runtime environmentNode floors, path tokens, environment layering, observed context and writable state.
      SecurityCredential, network, sandbox, consent and trust boundaries.
      LimitationsWhat is unsupported, deliberately constrained, or not established by available proof.
      Type APIGenerated symbols for the public package exports.
      TroubleshootingMissing routes/types, target mismatches, App lifecycle, package roots and qualification problems.

      The generated matrices are not another manually curated compatibility list. Their dated source links explain the recorded behavior. supported, degraded, unavailable and prohibited are feature judgments; an unperformed account-dependent runtime test is a separate verification limit. Consult the actual component and client/version rather than assuming one host-level badge covers every operation.

      For authoring patterns, use Reuse the framework: one tool with CLI and App surfaces, canonical schemas, semantic/plain hooks, request dependencies, state, payloads and installation. Custom server factories and raw native documents remain advanced integration paths, not the minimum code required for a plugin.

      Reading the diagnostics

      A structured diagnostic identifies a code, severity, message and, when available, source path and recovery. Read the current command's final outcome as well: a parser usage error, a failing or inconclusive eval, and an invalid inspection model are different failure paths.

      Only an error diagnostic gates the diagnostic-based checks. Options such as --strict can promote applicable host-tool warnings to errors, so do not discard a nonzero result merely because an earlier unpromoted warning was informational to your workflow. Exact command behavior is in CLI exit codes.

      FamilyArea
      AB30xxSkill parsing and rendered content.
      AB40xx–AB47xxIdentity, target composition, hooks, MCP, assets, package output and bundler policy.
      AB48xx–AB49xxConventional routes, contracts, layouts, providers, state and generated command surfaces.
      AB5000General command/adapter boundary failures.
      AB60xxArtifact, native document, referenced-file and compiler-evidence validation.
      AB7xxxPackage/install checks, project preparation, rebuilds and Doctor.
      AB8xxxDevelopment server and Workbench boundaries.
      AB9xxxEvaluations and persisted runs.

      These families are navigation, not a replacement for the full generated diagnostic reference. Correct the owning declaration or input; do not change generated manifest fields, invent missing runtime evidence, or widen native permissions to suppress a failure.