@h-rig/contracts 0.0.6-alpha.157 → 0.0.6-alpha.158

package/dist/src/session-asset-materializer.d.ts

@@ -0,0 +1,35 @@
+/**
+ * Pure session-asset-materializer contract.
+ *
+ * Neutral home for the "materialize plugin-contributed session assets into the
+ * workspace" seam so the plugin-host assembler (@rig/core/plugin-host-context)
+ * can trigger Pi skill + package materialization without importing
+ * @rig/provider-plugin (a floor->plugin cycle). The provider plugin owns the
+ * concrete impl (it knows the `.pi/skills` + `.pi/settings.json` layout) and
+ * registers it under {@link SESSION_ASSET_MATERIALIZER}; the assembler resolves
+ * it by id off the project plugin host and calls it. When no provider plugin is
+ * loaded the capability is simply absent and materialization is skipped — the
+ * same non-fatal default the inline implementation had.
+ *
+ * Carries no behaviour and imports only sibling contract types.
+ */
+import type { CapabilityId } from "./capability-id";
+import type { RigConfig } from "./config";
+/** Capability id the provider plugin registers its session-asset materializer under. */
+export declare const SESSION_ASSET_MATERIALIZER_CAPABILITY_ID = "provider.session-asset-materializer";
+/**
+ * Materializes the plugin-contributed session assets (Pi skills declared via
+ * `contributes.skills`, and the config-declared Pi extension packages in
+ * `runtime.pi.packages`) into the project workspace. Idempotent and non-fatal:
+ * implementations log-and-continue on individual write failures so a
+ * materialization error can never deadlock harness boot.
+ */
+export interface SessionAssetMaterializerService {
+    materializeSessionAssets(projectRoot: string, config: RigConfig): Promise<void>;
+}
+/**
+ * Typed capability id the provider plugin provides and the plugin-host assembler
+ * requires. Phantom-typed with `SessionAssetMaterializerService` so `resolve(host)`
+ * returns the service with no cast leaking to callers.
+ */
+export declare const SESSION_ASSET_MATERIALIZER: CapabilityId<SessionAssetMaterializerService>;

package/dist/src/session-asset-materializer.js

@@ -0,0 +1,13 @@
+// @bun
+// packages/contracts/src/capability-id.ts
+function makeCapabilityId(id) {
+  return id;
+}
+
+// packages/contracts/src/session-asset-materializer.ts
+var SESSION_ASSET_MATERIALIZER_CAPABILITY_ID = "provider.session-asset-materializer";
+var SESSION_ASSET_MATERIALIZER = makeCapabilityId(SESSION_ASSET_MATERIALIZER_CAPABILITY_ID);
+export {
+  SESSION_ASSET_MATERIALIZER_CAPABILITY_ID,
+  SESSION_ASSET_MATERIALIZER
+};

package/dist/src/setup.d.ts

@@ -0,0 +1,47 @@
+/**
+ * cap:project-setup — cross-plugin seam.
+ *
+ * `@rig/cli-surface-plugin` (the `rig setup`/onboarding surface) runs project
+ * setup WITHOUT importing `@rig/init-plugin`: it requires this capability by id
+ * off the host. `@rig/init-plugin` OWNS the impl (`runSetup`) and registers it
+ * under this id. This file holds ONLY the pure seam vocabulary — no IO, no
+ * function-laden deps (those are the impl's concern, not the cross-plugin seam).
+ */
+import type { CapabilityId } from "./capability-id";
+/** Capability id the init/setup plugin registers its setup runner under. */
+export declare const PROJECT_SETUP_CAPABILITY_ID = "cap:project-setup";
+/**
+ * Where runs execute for this project. `kind` is the placement discriminator
+ * (e.g. "local" | "remote"); kept as a plain string so contracts stays free of
+ * the placement-domain enum.
+ */
+export type ProjectSetupPlacement = {
+    readonly alias: string;
+    readonly kind: string;
+    readonly host?: string;
+    readonly port?: number;
+    readonly token?: string | null;
+};
+/** Pure input to a project-setup pass. */
+export type ProjectSetupInput = {
+    readonly projectRoot: string;
+    readonly slug: string;
+    readonly placement: ProjectSetupPlacement;
+    readonly rewriteConfig?: boolean;
+    readonly ensurePi?: boolean;
+    readonly ensureLabels?: boolean;
+    readonly githubToken?: string | null;
+    readonly importGhToken?: boolean;
+};
+/** Pure summary of a project-setup pass. */
+export type ProjectSetupResult = {
+    readonly repoSlug: string;
+    readonly placement: string;
+    readonly configWritten: boolean;
+};
+/** The cohesive project-setup operation the CLI surface depends on. Async (does IO). */
+export interface ProjectSetupService {
+    runSetup(input: ProjectSetupInput): Promise<ProjectSetupResult>;
+}
+/** Typed capability id; string value is {@link PROJECT_SETUP_CAPABILITY_ID}. */
+export declare const PROJECT_SETUP: CapabilityId<ProjectSetupService>;

package/dist/src/setup.js

@@ -0,0 +1,13 @@
+// @bun
+// packages/contracts/src/capability-id.ts
+function makeCapabilityId(id) {
+  return id;
+}
+
+// packages/contracts/src/setup.ts
+var PROJECT_SETUP_CAPABILITY_ID = "cap:project-setup";
+var PROJECT_SETUP = makeCapabilityId(PROJECT_SETUP_CAPABILITY_ID);
+export {
+  PROJECT_SETUP_CAPABILITY_ID,
+  PROJECT_SETUP
+};