review-plugin-submissionlisted

# Review plugin submission ## Contract | Field | Bound contract | |---|---| | Trigger | Final marketplace-readiness review of an agent plugin. | | Authority | No file, VCS, credential, paid, published, deployed, or remote mutation. | | Side effect | Chat output only; no file writes, no credential use, no remote calls beyond reads needed for the audit. | | Done | Sectioned pass/fail report and submission recommendation returned in chat. | ## Inputs - plugin_root (required): Absolute path to the plugin directory to audit. - gate_rules_path (optional): Absolute path to a gate rules file that defines the named gates, each gate's pass condition, and the exact failure message for its fail path. When it is omitted, the audit runs the built-in default gates defined in step 1. ## Procedure 1. Read the gate rules file at `gate_rules_path`. When it is omitted, audit with the built-in default gates instead: manifest-present (step 2), manifest-complete (step 3), and file-valid (step 4a); these defaults define no allowlist entries. Parse every named gate (check, rule, or criterion block). Record each gate's pass condition and the exact failure message for its fail path. Also parse the rules file's allowlist section when present: each entry is a path prefix, and a file is allowlisted when its path relative to `plugin_root` starts with that prefix. 2. Reject with a failure report if `plugin_root/plugin.json` does not exist. 3. Reject with a failure report if `plugin_root/plugin.json` l