gh-inari 0.9.0 → 0.10.2

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "inari",
-  "version": "0.9.0",
+  "version": "0.10.2",
   "description": "Governed GitHub Issue/PR/template workflows via the inari CLI. Prefer inari over raw gh for operations it owns; use inari skill for operational playbooks.",
   "skills": "skills/inari"
 }

package/README.md

@@ -90,8 +90,10 @@ recovery command. The current capability identifiers are
 `canonical-invocation`, `machine-readable-version`, `capability-diagnostics`,
 and `extension-bootstrap`.
 
-The `inari`, `gh-inari`, and `gh inari` invocation forms are behaviorally
-identical:
+The `inari` executable is canonical. The direct package executable
+`gh-inari` and the `gh inari` extension form are compatibility paths with the
+same governed command semantics; prefer `inari` for agent and human-facing
+commands:
 
 ```bash
 inari issue schema feature --json
@@ -260,6 +262,22 @@ templates:
 
 Template and section bindings are deterministic. Stale, unknown, or ambiguous template/section references fail closed. `linkedIssue: true` means that the field contains a GitHub closing reference: `close`, `closes`, `closed`, `fix`, `fixes`, `fixed`, `resolve`, `resolves`, or `resolved`, followed by `#ISSUE-NUMBER` or `OWNER/REPOSITORY#ISSUE-NUMBER`, with an optional colon and case-insensitive keyword. This validates syntax only; GitHub applies automatic linking/closure only under its own contextual rules, including the target default branch.
 
+When `issue create` or `pr create` omits `--template`, the shared resolver uses
+the repository's optional `.github/inari/template-resolution.yml` authority:
+
+```yaml
+version: 1
+defaults:
+  issue: feature
+  pr: default
+```
+
+The precedence is explicit selector, configured default, sole candidate,
+interactive TTY selection, then bounded failure. Non-interactive execution never
+guesses among multiple candidates. An invalid or unavailable configured default
+also fails closed. Candidate identifiers and an explicit `--template` recovery
+action are included in structured ambiguity diagnostics.
+
 Issue Form top-level `title` is a fixed native prefix for create validation, but it does not satisfy the caller's required title metadata by itself. An explicit caller title is used as supplied without inferred prefix concatenation or automatic generation. Top-level `labels` are repository-governed defaults and are always retained; caller-supplied labels are appended in order with duplicates removed. Top-level `assignees`, `projects`, and `type`, and upload fields remain unsupported and fail closed rather than being approximated.
 
 ## Scope

package/dist/cli-core.d.ts

@@ -0,0 +1,24 @@
+import { GitHubAdapter } from "./github/index.js";
+import type { TemplateResolverDependencies } from "./template-resolver.js";
+interface PackageMetadata {
+    readonly name: string;
+    readonly version: string;
+    readonly description: string;
+}
+interface DiagnosticCommandResult {
+    readonly status: number | null;
+    readonly stdout: string;
+    readonly stderr: string;
+    readonly error?: string;
+}
+export interface CliDependencies {
+    readonly repositoryRoot?: string;
+    readonly createAdapter?: (options: ConstructorParameters<typeof GitHubAdapter>[0]) => GitHubAdapter;
+    readonly packageMetadata?: PackageMetadata;
+    readonly runDiagnosticCommand?: (args: readonly string[]) => DiagnosticCommandResult;
+    readonly runGhFallback?: (argv: readonly string[]) => number;
+    readonly templateResolver?: TemplateResolverDependencies;
+}
+/** The installed gh-inari executable entrypoint. */
+export declare function runCli(argv: string[], dependencies?: CliDependencies): Promise<number>;
+export {};