/**
 * PackagePlugin — the autonomous half of the publish lane (spec §3.2).
 *
 * Everything before the button: run the eval gates at publish strictness, write
 * a README if the plugin has none, produce the marketplace index entry, and hand
 * back the instructions for the step the model must not take. The tool touches no
 * remote and cannot publish; `/plugin publish` (a human command) is where the
 * artifact actually leaves the machine.
 *
 * It is autonomous because none of it is irreversible — it writes two files into
 * a directory the plugin already owns — and because the value of the lane is that
 * the human's remaining decision is *just* the approval, with the mechanics
 * already done and the checks already run. It is in
 * {@link PLUGIN_SYSTEM_TOOL_NAMES} all the same: an authored subagent that could
 * package is one step from a subagent that could publish.
 */
import { type ToolDefinition } from "../extensions/types.js";
export declare function createPackagePluginToolDefinition(): ToolDefinition;
//# sourceMappingURL=package-plugin.d.ts.map