@jini-ai/admin 0.1.0

package/dist/core/ports/redirects.d.ts

@@ -0,0 +1,139 @@
+/**
+ * @file `AdminRedirectsPort` — manual URL redirect rules layered in front of a host's own content
+ * resolution (a 404-fill pass by default, or an early override pass for retiring a live URL).
+ *
+ * ## `matchType: "regex"` is a real, typed, always-rejected request shape
+ *
+ * `RedirectMatchType` includes `"regex"` because the reference implementation's own API surface
+ * accepts it as a well-formed request value — but its write chokepoint hard-rejects it
+ * unconditionally in v1 (its own matcher source literally comments "never actually reachable — validatePattern always rejects it
+ * at write time"). This is not a permission gate or a feature flag despite how it may look from the
+ * type alone: every `createRedirect`/`updateRedirect`/`importRedirects` call carrying `"regex"`
+ * fails validation, full stop, on the reference implementation. A panel must not offer `regex` as a
+ * selectable match type unless it has independently confirmed the host it's talking to actually
+ * implements it — do not infer support from this type accepting the literal.
+ *
+ * This is the "loudly-rejected input stays and gets documented" half of the rule `forms.ts`'s file
+ * header states in full (its counterpart, a silently-ignored input, is why that port's update patch
+ * has no `slug` field at all) — kept here because the union is OPEN and a different host may
+ * legitimately implement `regex` even though the reference implementation refuses it.
+ *
+ * ## `tombstoneRedirect` is a soft delete
+ *
+ * Mirrors `AdminIntegrationsPort.deleteIntegrationSubscription`, not `AdminMediaPort.deleteMedia`:
+ * the rule's `status` flips to `"disabled"` and the row is retained (audit trail, still readable
+ * via `listRedirects`/`getRedirect`), never hard-purged. The method resolves to the updated record
+ * (200-style), not `void` — a panel can render the new state without a re-fetch.
+ *
+ * ## `source: "auto_slug_change"` is read-only provenance
+ *
+ * Rows carrying this source are minted internally by the host's own content pipeline when a piece
+ * of content's slug changes (never-break-links) — it is not a value a caller chooses. It appears
+ * on `AdminRedirect.source` for display, but `AdminRedirectCreateInput` (used by both
+ * `createRedirect` and each item of `importRedirects`) has no `source` field at all: there is
+ * nothing to set. Do not offer `auto_slug_change` as a choice in a create/import form.
+ *
+ * ## `importRedirects` never fails as a whole
+ *
+ * The reference implementation's route always answers 207 Multi-Status: each rule is validated and written
+ * independently through the same path `createRedirect` uses, so one bad item never aborts the
+ * batch or rolls back already-written ones. Check `AdminRedirectImportResult.failed` for per-item
+ * rejections — a resolved promise here does not mean every rule in the batch was created.
+ *
+ * ## Open vs. closed unions
+ *
+ * `RedirectStatusCode` is CLOSED (`301 | 302 | 307 | 308`) — this is the complete set the
+ * reference implementation's write chokepoint accepts, and it is a subset of a real HTTP standard,
+ * not the reference implementation's to extend (a 5th caller-supplied code would need a 5th value
+ * here to be meaningful, and the reference server would reject it anyway). `RedirectMatchType`,
+ * `RedirectSource`, and `RedirectStatus` are reference-implementation-specific vocabularies that
+ * another host's routing engine will diverge from — OPEN, via the `T | (string & {})` idiom
+ * `seo.ts`'s file header introduces for this port
+ * set.
+ */
+/** How a rule's pattern is matched against an incoming path — open, see file header
+ *  (`"regex"` is a real literal that is always rejected on the reference implementation). */
+export type RedirectMatchType = "exact" | "prefix" | "wildcard" | "regex" | (string & {});
+/** HTTP status a matched rule emits — closed, see file header. */
+export type RedirectStatusCode = 301 | 302 | 307 | 308;
+/** Provenance of a rule — open, see file header (`"auto_slug_change"` is read-only). */
+export type RedirectSource = "manual" | "auto_slug_change" | "import" | (string & {});
+/** Lifecycle of a rule — open, see file header. */
+export type RedirectStatus = "active" | "disabled" | (string & {});
+export interface AdminRedirect {
+    readonly id: string;
+    readonly matchType: RedirectMatchType;
+    readonly fromPattern: string;
+    /** A normalized site-relative path, or an absolute URL. */
+    readonly toTarget: string;
+    readonly statusCode: RedirectStatusCode;
+    readonly status: RedirectStatus;
+    /** When true, this rule is consulted before live content resolution (retires a live URL);
+     *  when false (the default), it only fills the not-found path. */
+    readonly override: boolean;
+    /** Explicit tie-breaker within an equal-specificity band — higher wins. */
+    readonly priority: number;
+    readonly source: RedirectSource;
+    /** The content item whose slug change minted this rule — set only for `source:
+     *  "auto_slug_change"` rows. */
+    readonly sourceEntryId: string | null;
+    readonly fromPathAtCapture: string | null;
+    readonly toPathAtCapture: string | null;
+    readonly createdByPrincipal: string;
+    readonly createdByPluginId: string | null;
+    readonly createdAt: string;
+    readonly updatedAt: string;
+    readonly version: number;
+}
+/** No `source` field — see file header, there is nothing for a caller to set. */
+export interface AdminRedirectCreateInput {
+    readonly matchType: RedirectMatchType;
+    readonly fromPattern: string;
+    readonly toTarget: string;
+    readonly statusCode: RedirectStatusCode;
+    readonly override?: boolean;
+    readonly priority?: number;
+}
+export interface AdminRedirectUpdatePatch {
+    readonly matchType?: RedirectMatchType;
+    readonly fromPattern?: string;
+    readonly toTarget?: string;
+    readonly statusCode?: RedirectStatusCode;
+    readonly status?: RedirectStatus;
+    readonly override?: boolean;
+    readonly priority?: number;
+}
+export interface AdminRedirectListFilter {
+    readonly status?: RedirectStatus;
+    readonly source?: RedirectSource;
+    readonly matchType?: RedirectMatchType;
+}
+export interface AdminRedirectHitStats {
+    readonly redirectId: string;
+    readonly hitCount: number;
+    readonly lastHitAt: string | null;
+}
+export interface AdminRedirectImportFailure {
+    readonly index: number;
+    readonly code: string;
+    readonly message: string;
+}
+export interface AdminRedirectImportResult {
+    readonly created: readonly AdminRedirect[];
+    readonly failed: readonly AdminRedirectImportFailure[];
+}
+export interface AdminRedirectsPort {
+    listRedirects(filter?: AdminRedirectListFilter): Promise<readonly AdminRedirect[]>;
+    getRedirect(id: string): Promise<AdminRedirect>;
+    createRedirect(input: AdminRedirectCreateInput): Promise<AdminRedirect>;
+    updateRedirect(id: string, patch: AdminRedirectUpdatePatch): Promise<AdminRedirect>;
+    /** Soft delete — returns the tombstoned record, not `void`. See file header. */
+    tombstoneRedirect(id: string): Promise<AdminRedirect>;
+    /** Resolves with `hitCount: 0`/`lastHitAt: null` when no hits have been recorded yet — distinct
+     *  from the redirect itself not existing, which is a not-found-class rejection instead. */
+    getRedirectHitStats(id: string): Promise<AdminRedirectHitStats>;
+    /** Always a partial-success batch — see file header. Each item shares `AdminRedirectCreateInput`'s
+     *  shape (provenance is stamped `"import"` automatically, not caller-supplied). */
+    importRedirects(rules: readonly AdminRedirectCreateInput[]): Promise<AdminRedirectImportResult>;
+}
+//# sourceMappingURL=redirects.d.ts.map

package/dist/core/ports/redirects.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"redirects.d.ts","sourceRoot":"","sources":["../../../src/core/ports/redirects.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoDG;AAEH;6FAC6F;AAC7F,MAAM,MAAM,iBAAiB,GAAG,OAAO,GAAG,QAAQ,GAAG,UAAU,GAAG,OAAO,GAAG,CAAC,MAAM,GAAG,EAAE,CAAC,CAAC;AAE1F,kEAAkE;AAClE,MAAM,MAAM,kBAAkB,GAAG,GAAG,GAAG,GAAG,GAAG,GAAG,GAAG,GAAG,CAAC;AAEvD,wFAAwF;AACxF,MAAM,MAAM,cAAc,GAAG,QAAQ,GAAG,kBAAkB,GAAG,QAAQ,GAAG,CAAC,MAAM,GAAG,EAAE,CAAC,CAAC;AAEtF,mDAAmD;AACnD,MAAM,MAAM,cAAc,GAAG,QAAQ,GAAG,UAAU,GAAG,CAAC,MAAM,GAAG,EAAE,CAAC,CAAC;AAEnE,MAAM,WAAW,aAAa;IAC5B,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,QAAQ,CAAC,SAAS,EAAE,iBAAiB,CAAC;IACtC,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;IAC7B,2DAA2D;IAC3D,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,UAAU,EAAE,kBAAkB,CAAC;IACxC,QAAQ,CAAC,MAAM,EAAE,cAAc,CAAC;IAChC;sEACkE;IAClE,QAAQ,CAAC,QAAQ,EAAE,OAAO,CAAC;IAC3B,2EAA2E;IAC3E,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,MAAM,EAAE,cAAc,CAAC;IAChC;oCACgC;IAChC,QAAQ,CAAC,aAAa,EAAE,MAAM,GAAG,IAAI,CAAC;IACtC,QAAQ,CAAC,iBAAiB,EAAE,MAAM,GAAG,IAAI,CAAC;IAC1C,QAAQ,CAAC,eAAe,EAAE,MAAM,GAAG,IAAI,CAAC;IACxC,QAAQ,CAAC,kBAAkB,EAAE,MAAM,CAAC;IACpC,QAAQ,CAAC,iBAAiB,EAAE,MAAM,GAAG,IAAI,CAAC;IAC1C,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;CAC1B;AAED,iFAAiF;AACjF,MAAM,WAAW,wBAAwB;IACvC,QAAQ,CAAC,SAAS,EAAE,iBAAiB,CAAC;IACtC,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,UAAU,EAAE,kBAAkB,CAAC;IACxC,QAAQ,CAAC,QAAQ,CAAC,EAAE,OAAO,CAAC;IAC5B,QAAQ,CAAC,QAAQ,CAAC,EAAE,MAAM,CAAC;CAC5B;AAED,MAAM,WAAW,wBAAwB;IACvC,QAAQ,CAAC,SAAS,CAAC,EAAE,iBAAiB,CAAC;IACvC,QAAQ,CAAC,WAAW,CAAC,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,QAAQ,CAAC,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,UAAU,CAAC,EAAE,kBAAkB,CAAC;IACzC,QAAQ,CAAC,MAAM,CAAC,EAAE,cAAc,CAAC;IACjC,QAAQ,CAAC,QAAQ,CAAC,EAAE,OAAO,CAAC;IAC5B,QAAQ,CAAC,QAAQ,CAAC,EAAE,MAAM,CAAC;CAC5B;AAED,MAAM,WAAW,uBAAuB;IACtC,QAAQ,CAAC,MAAM,CAAC,EAAE,cAAc,CAAC;IACjC,QAAQ,CAAC,MAAM,CAAC,EAAE,cAAc,CAAC;IACjC,QAAQ,CAAC,SAAS,CAAC,EAAE,iBAAiB,CAAC;CACxC;AAED,MAAM,WAAW,qBAAqB;IACpC,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;IAC5B,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,SAAS,EAAE,MAAM,GAAG,IAAI,CAAC;CACnC;AAED,MAAM,WAAW,0BAA0B;IACzC,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;CAC1B;AAED,MAAM,WAAW,yBAAyB;IACxC,QAAQ,CAAC,OAAO,EAAE,SAAS,aAAa,EAAE,CAAC;IAC3C,QAAQ,CAAC,MAAM,EAAE,SAAS,0BAA0B,EAAE,CAAC;CACxD;AAED,MAAM,WAAW,kBAAkB;IACjC,aAAa,CAAC,MAAM,CAAC,EAAE,uBAAuB,GAAG,OAAO,CAAC,SAAS,aAAa,EAAE,CAAC,CAAC;IACnF,WAAW,CAAC,EAAE,EAAE,MAAM,GAAG,OAAO,CAAC,aAAa,CAAC,CAAC;IAChD,cAAc,CAAC,KAAK,EAAE,wBAAwB,GAAG,OAAO,CAAC,aAAa,CAAC,CAAC;IACxE,cAAc,CAAC,EAAE,EAAE,MAAM,EAAE,KAAK,EAAE,wBAAwB,GAAG,OAAO,CAAC,aAAa,CAAC,CAAC;IACpF,gFAAgF;IAChF,iBAAiB,CAAC,EAAE,EAAE,MAAM,GAAG,OAAO,CAAC,aAAa,CAAC,CAAC;IACtD;+FAC2F;IAC3F,mBAAmB,CAAC,EAAE,EAAE,MAAM,GAAG,OAAO,CAAC,qBAAqB,CAAC,CAAC;IAChE;uFACmF;IACnF,eAAe,CAAC,KAAK,EAAE,SAAS,wBAAwB,EAAE,GAAG,OAAO,CAAC,yBAAyB,CAAC,CAAC;CACjG"}

package/dist/core/ports/redirects.js

@@ -0,0 +1,55 @@
+/**
+ * @file `AdminRedirectsPort` — manual URL redirect rules layered in front of a host's own content
+ * resolution (a 404-fill pass by default, or an early override pass for retiring a live URL).
+ *
+ * ## `matchType: "regex"` is a real, typed, always-rejected request shape
+ *
+ * `RedirectMatchType` includes `"regex"` because the reference implementation's own API surface
+ * accepts it as a well-formed request value — but its write chokepoint hard-rejects it
+ * unconditionally in v1 (its own matcher source literally comments "never actually reachable — validatePattern always rejects it
+ * at write time"). This is not a permission gate or a feature flag despite how it may look from the
+ * type alone: every `createRedirect`/`updateRedirect`/`importRedirects` call carrying `"regex"`
+ * fails validation, full stop, on the reference implementation. A panel must not offer `regex` as a
+ * selectable match type unless it has independently confirmed the host it's talking to actually
+ * implements it — do not infer support from this type accepting the literal.
+ *
+ * This is the "loudly-rejected input stays and gets documented" half of the rule `forms.ts`'s file
+ * header states in full (its counterpart, a silently-ignored input, is why that port's update patch
+ * has no `slug` field at all) — kept here because the union is OPEN and a different host may
+ * legitimately implement `regex` even though the reference implementation refuses it.
+ *
+ * ## `tombstoneRedirect` is a soft delete
+ *
+ * Mirrors `AdminIntegrationsPort.deleteIntegrationSubscription`, not `AdminMediaPort.deleteMedia`:
+ * the rule's `status` flips to `"disabled"` and the row is retained (audit trail, still readable
+ * via `listRedirects`/`getRedirect`), never hard-purged. The method resolves to the updated record
+ * (200-style), not `void` — a panel can render the new state without a re-fetch.
+ *
+ * ## `source: "auto_slug_change"` is read-only provenance
+ *
+ * Rows carrying this source are minted internally by the host's own content pipeline when a piece
+ * of content's slug changes (never-break-links) — it is not a value a caller chooses. It appears
+ * on `AdminRedirect.source` for display, but `AdminRedirectCreateInput` (used by both
+ * `createRedirect` and each item of `importRedirects`) has no `source` field at all: there is
+ * nothing to set. Do not offer `auto_slug_change` as a choice in a create/import form.
+ *
+ * ## `importRedirects` never fails as a whole
+ *
+ * The reference implementation's route always answers 207 Multi-Status: each rule is validated and written
+ * independently through the same path `createRedirect` uses, so one bad item never aborts the
+ * batch or rolls back already-written ones. Check `AdminRedirectImportResult.failed` for per-item
+ * rejections — a resolved promise here does not mean every rule in the batch was created.
+ *
+ * ## Open vs. closed unions
+ *
+ * `RedirectStatusCode` is CLOSED (`301 | 302 | 307 | 308`) — this is the complete set the
+ * reference implementation's write chokepoint accepts, and it is a subset of a real HTTP standard,
+ * not the reference implementation's to extend (a 5th caller-supplied code would need a 5th value
+ * here to be meaningful, and the reference server would reject it anyway). `RedirectMatchType`,
+ * `RedirectSource`, and `RedirectStatus` are reference-implementation-specific vocabularies that
+ * another host's routing engine will diverge from — OPEN, via the `T | (string & {})` idiom
+ * `seo.ts`'s file header introduces for this port
+ * set.
+ */
+export {};
+//# sourceMappingURL=redirects.js.map

package/dist/core/ports/redirects.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"redirects.js","sourceRoot":"","sources":["../../../src/core/ports/redirects.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoDG"}

package/dist/core/ports/seo.d.ts

@@ -0,0 +1,147 @@
+/**
+ * @file `AdminSeoPort` — per-entry SEO meta overrides layered over workspace-level defaults, plus
+ * the resolved output an editor/analyzer/renderer all consume, and a sitemap regeneration trigger.
+ *
+ * `entryId` throughout this port is an opaque host content-item id — this port does not know or
+ * care whether it names a post, a page, or anything else; the host resolves it against whatever
+ * object of its own owns SEO meta. No content-type vocabulary lives here.
+ *
+ * ## `putSeoEntry` resolves to the full effective meta, not an echo of your patch
+ *
+ * The reference implementation's route writes the raw override patch, then re-reads and returns
+ * the fully resolved `AdminSeoMeta` (override ▸ site default ▸ derived-from-content, per field) rather than
+ * the patch itself or the raw override bag. Concretely: patching only `title` can still change
+ * `openGraph.title` in the response, because an unset `ogTitle` override falls back to the
+ * (now-different) resolved `title`. Do not diff the response against the patch you sent to detect
+ * "what changed" — every field in the response reflects the full resolution, not just your edit.
+ *
+ * ## `regenerateSeoSitemap` is a fire-and-accept trigger, not a trackable job
+ *
+ * The reference implementation's route answers `202 Accepted` synchronously and hands back nothing but an
+ * acknowledgement — no job id, no status endpoint, no completion event on this contract. Mirrors
+ * `analytics.ts`'s stance on staying exactly as thin as the reference implementation: a host that
+ * needs progress/queueing semantics around regeneration needs a different, dedicated contract, not
+ * options bolted onto this method over time.
+ *
+ * ## Open vs. closed unions in this port (and the idiom used across this slice)
+ *
+ * `SeoOpenGraphType`/`SeoTwitterCardKind` are literal web standards (OpenGraph's `og:type`,
+ * Twitter/X's card kinds) — CLOSED, because there is no host-specific value space to widen; every
+ * implementer speaks the same vocabulary. `SeoIssueSeverity` is the reference implementation's own
+ * analysis-engine taxonomy (today just `error`/`warning`/`info`), not a standard, and a host's analyzer may grade
+ * findings more finely — OPEN, via the `T | (string & {})` widening idiom (preserves autocomplete
+ * on the known values while still accepting an arbitrary host-defined string). No widening idiom
+ * was established elsewhere in this port set before this slice; this file introduces it, and
+ * `redirects.ts`/`menus.ts`/`forms.ts` follow the same idiom for their own reference-implementation-
+ * specific unions rather than inventing their own.
+ */
+/** OpenGraph object type (`og:type`) — closed, see file header. */
+export type SeoOpenGraphType = "website" | "article" | "profile";
+/** Twitter/X card kind — closed, see file header. */
+export type SeoTwitterCardKind = "summary" | "summary_large_image";
+/** Severity of one `AdminSeoIssue` — open, see file header. */
+export type SeoIssueSeverity = "error" | "warning" | "info" | (string & {});
+/**
+ * The author-authored override bag for one entry. Every field is OPTIONAL — omitting a field
+ * means "derive from site defaults / the content itself," not "clear it"; `putSeoEntry` merge-
+ * patches this bag onto whatever was previously stored; there is no way to unset a single
+ * previously-set field back to "derive" short of the host's own reset affordance (the reference
+ * implementation has none either).
+ */
+export interface AdminSeoOverrides {
+    readonly title?: string;
+    readonly description?: string;
+    /** Accepted cross-domain as-is; a host may reject unsafe schemes (`javascript:`, `data:`, ...)
+     *  server-side rather than this port validating client-side. */
+    readonly canonical?: string;
+    readonly noindex?: boolean;
+    readonly nofollow?: boolean;
+    /** schema.org `@type` override (else derived from content type). */
+    readonly schemaType?: string;
+    readonly ogTitle?: string;
+    readonly ogDescription?: string;
+    /** A media ref or absolute URL; resolved to a renderable URL in `AdminSeoMeta.openGraph.image`. */
+    readonly ogImage?: string;
+    readonly ogType?: SeoOpenGraphType;
+    readonly twitterCard?: SeoTwitterCardKind;
+    readonly twitterTitle?: string;
+    readonly twitterDescription?: string;
+    readonly twitterImage?: string;
+}
+export interface AdminSeoOpenGraph {
+    readonly title: string;
+    readonly description?: string;
+    readonly type: SeoOpenGraphType;
+    readonly url: string;
+    /** Already resolved to a renderable URL — never a media ref. */
+    readonly image?: string;
+    readonly siteName?: string;
+}
+export interface AdminSeoTwitterCard {
+    readonly card: SeoTwitterCardKind;
+    readonly title: string;
+    readonly description?: string;
+    readonly image?: string;
+    readonly site?: string;
+}
+export interface AdminSeoRobotsDirective {
+    readonly noindex: boolean;
+    readonly nofollow: boolean;
+}
+/** The fully-resolved effective meta for one entry — what `getSeoEntry`/`putSeoEntry` return and
+ *  what `AdminSeoAnalysis.resolved` embeds. Never partial: every override/default/derivation
+ *  decision is already made. */
+export interface AdminSeoMeta {
+    readonly title: string;
+    readonly description?: string;
+    readonly canonical: string;
+    readonly robots: AdminSeoRobotsDirective;
+    readonly openGraph: AdminSeoOpenGraph;
+    readonly twitter: AdminSeoTwitterCard;
+    /** schema.org JSON-LD graph objects (`@context`/`@type`/...). Opaque to this port beyond being
+     *  plain JSON objects. */
+    readonly jsonLd: readonly Record<string, unknown>[];
+}
+export interface AdminSeoIssue {
+    readonly code: string;
+    readonly severity: SeoIssueSeverity;
+    readonly message: string;
+    /** One of `AdminSeoMeta`'s top-level field names, when the issue is about a specific resolved
+     *  field (e.g. `"title"`, `"description"`). Absent for a whole-entry issue. */
+    readonly field?: string;
+}
+export interface AdminSeoAnalysis {
+    readonly entryId: string;
+    readonly score: number;
+    readonly issues: readonly AdminSeoIssue[];
+    readonly resolved: AdminSeoMeta;
+}
+export interface AdminSeoRobotsRule {
+    readonly userAgent: string;
+    readonly allow?: readonly string[];
+    readonly disallow?: readonly string[];
+}
+/** Workspace-level SEO defaults every entry's resolution falls back to. */
+export interface AdminSeoSettings {
+    /** e.g. `"%s — My Site"`; `%s` is substituted with the per-entry title. */
+    readonly titleTemplate: string;
+    readonly defaultDescription?: string;
+    readonly defaultOgImage?: string;
+    readonly twitterSite?: string;
+    readonly defaultRobots: AdminSeoRobotsDirective;
+    readonly sitemapEnabled: boolean;
+    readonly robotsRules: readonly AdminSeoRobotsRule[];
+}
+export interface AdminSeoPort {
+    getSeoEntry(entryId: string): Promise<AdminSeoMeta>;
+    /** Merge-patches the override bag and returns the newly-resolved meta — see file header. */
+    putSeoEntry(entryId: string, patch: AdminSeoOverrides): Promise<AdminSeoMeta>;
+    analyzeSeoEntry(entryId: string): Promise<AdminSeoAnalysis>;
+    getSeoSettings(): Promise<AdminSeoSettings>;
+    putSeoSettings(patch: Partial<AdminSeoSettings>): Promise<AdminSeoSettings>;
+    /** Fire-and-accept trigger, not a trackable job — see file header. */
+    regenerateSeoSitemap(): Promise<{
+        accepted: boolean;
+    }>;
+}
+//# sourceMappingURL=seo.d.ts.map

package/dist/core/ports/seo.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"seo.d.ts","sourceRoot":"","sources":["../../../src/core/ports/seo.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoCG;AAEH,mEAAmE;AACnE,MAAM,MAAM,gBAAgB,GAAG,SAAS,GAAG,SAAS,GAAG,SAAS,CAAC;AAEjE,qDAAqD;AACrD,MAAM,MAAM,kBAAkB,GAAG,SAAS,GAAG,qBAAqB,CAAC;AAEnE,+DAA+D;AAC/D,MAAM,MAAM,gBAAgB,GAAG,OAAO,GAAG,SAAS,GAAG,MAAM,GAAG,CAAC,MAAM,GAAG,EAAE,CAAC,CAAC;AAE5E;;;;;;GAMG;AACH,MAAM,WAAW,iBAAiB;IAChC,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAC;IACxB,QAAQ,CAAC,WAAW,CAAC,EAAE,MAAM,CAAC;IAC9B;oEACgE;IAChE,QAAQ,CAAC,SAAS,CAAC,EAAE,MAAM,CAAC;IAC5B,QAAQ,CAAC,OAAO,CAAC,EAAE,OAAO,CAAC;IAC3B,QAAQ,CAAC,QAAQ,CAAC,EAAE,OAAO,CAAC;IAC5B,oEAAoE;IACpE,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,OAAO,CAAC,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,aAAa,CAAC,EAAE,MAAM,CAAC;IAChC,mGAAmG;IACnG,QAAQ,CAAC,OAAO,CAAC,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,MAAM,CAAC,EAAE,gBAAgB,CAAC;IACnC,QAAQ,CAAC,WAAW,CAAC,EAAE,kBAAkB,CAAC;IAC1C,QAAQ,CAAC,YAAY,CAAC,EAAE,MAAM,CAAC;IAC/B,QAAQ,CAAC,kBAAkB,CAAC,EAAE,MAAM,CAAC;IACrC,QAAQ,CAAC,YAAY,CAAC,EAAE,MAAM,CAAC;CAChC;AAED,MAAM,WAAW,iBAAiB;IAChC,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,WAAW,CAAC,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,IAAI,EAAE,gBAAgB,CAAC;IAChC,QAAQ,CAAC,GAAG,EAAE,MAAM,CAAC;IACrB,gEAAgE;IAChE,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAC;IACxB,QAAQ,CAAC,QAAQ,CAAC,EAAE,MAAM,CAAC;CAC5B;AAED,MAAM,WAAW,mBAAmB;IAClC,QAAQ,CAAC,IAAI,EAAE,kBAAkB,CAAC;IAClC,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,WAAW,CAAC,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAC;IACxB,QAAQ,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC;CACxB;AAED,MAAM,WAAW,uBAAuB;IACtC,QAAQ,CAAC,OAAO,EAAE,OAAO,CAAC;IAC1B,QAAQ,CAAC,QAAQ,EAAE,OAAO,CAAC;CAC5B;AAED;;gCAEgC;AAChC,MAAM,WAAW,YAAY;IAC3B,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,WAAW,CAAC,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,MAAM,EAAE,uBAAuB,CAAC;IACzC,QAAQ,CAAC,SAAS,EAAE,iBAAiB,CAAC;IACtC,QAAQ,CAAC,OAAO,EAAE,mBAAmB,CAAC;IACtC;8BAC0B;IAC1B,QAAQ,CAAC,MAAM,EAAE,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,CAAC;CACrD;AAED,MAAM,WAAW,aAAa;IAC5B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,QAAQ,EAAE,gBAAgB,CAAC;IACpC,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB;mFAC+E;IAC/E,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAC;CACzB;AAED,MAAM,WAAW,gBAAgB;IAC/B,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,MAAM,EAAE,SAAS,aAAa,EAAE,CAAC;IAC1C,QAAQ,CAAC,QAAQ,EAAE,YAAY,CAAC;CACjC;AAED,MAAM,WAAW,kBAAkB;IACjC,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,KAAK,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IACnC,QAAQ,CAAC,QAAQ,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;CACvC;AAED,2EAA2E;AAC3E,MAAM,WAAW,gBAAgB;IAC/B,2EAA2E;IAC3E,QAAQ,CAAC,aAAa,EAAE,MAAM,CAAC;IAC/B,QAAQ,CAAC,kBAAkB,CAAC,EAAE,MAAM,CAAC;IACrC,QAAQ,CAAC,cAAc,CAAC,EAAE,MAAM,CAAC;IACjC,QAAQ,CAAC,WAAW,CAAC,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,aAAa,EAAE,uBAAuB,CAAC;IAChD,QAAQ,CAAC,cAAc,EAAE,OAAO,CAAC;IACjC,QAAQ,CAAC,WAAW,EAAE,SAAS,kBAAkB,EAAE,CAAC;CACrD;AAED,MAAM,WAAW,YAAY;IAC3B,WAAW,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,YAAY,CAAC,CAAC;IACpD,4FAA4F;IAC5F,WAAW,CAAC,OAAO,EAAE,MAAM,EAAE,KAAK,EAAE,iBAAiB,GAAG,OAAO,CAAC,YAAY,CAAC,CAAC;IAC9E,eAAe,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,gBAAgB,CAAC,CAAC;IAC5D,cAAc,IAAI,OAAO,CAAC,gBAAgB,CAAC,CAAC;IAC5C,cAAc,CAAC,KAAK,EAAE,OAAO,CAAC,gBAAgB,CAAC,GAAG,OAAO,CAAC,gBAAgB,CAAC,CAAC;IAC5E,sEAAsE;IACtE,oBAAoB,IAAI,OAAO,CAAC;QAAE,QAAQ,EAAE,OAAO,CAAA;KAAE,CAAC,CAAC;CACxD"}

package/dist/core/ports/seo.js

@@ -0,0 +1,39 @@
+/**
+ * @file `AdminSeoPort` — per-entry SEO meta overrides layered over workspace-level defaults, plus
+ * the resolved output an editor/analyzer/renderer all consume, and a sitemap regeneration trigger.
+ *
+ * `entryId` throughout this port is an opaque host content-item id — this port does not know or
+ * care whether it names a post, a page, or anything else; the host resolves it against whatever
+ * object of its own owns SEO meta. No content-type vocabulary lives here.
+ *
+ * ## `putSeoEntry` resolves to the full effective meta, not an echo of your patch
+ *
+ * The reference implementation's route writes the raw override patch, then re-reads and returns
+ * the fully resolved `AdminSeoMeta` (override ▸ site default ▸ derived-from-content, per field) rather than
+ * the patch itself or the raw override bag. Concretely: patching only `title` can still change
+ * `openGraph.title` in the response, because an unset `ogTitle` override falls back to the
+ * (now-different) resolved `title`. Do not diff the response against the patch you sent to detect
+ * "what changed" — every field in the response reflects the full resolution, not just your edit.
+ *
+ * ## `regenerateSeoSitemap` is a fire-and-accept trigger, not a trackable job
+ *
+ * The reference implementation's route answers `202 Accepted` synchronously and hands back nothing but an
+ * acknowledgement — no job id, no status endpoint, no completion event on this contract. Mirrors
+ * `analytics.ts`'s stance on staying exactly as thin as the reference implementation: a host that
+ * needs progress/queueing semantics around regeneration needs a different, dedicated contract, not
+ * options bolted onto this method over time.
+ *
+ * ## Open vs. closed unions in this port (and the idiom used across this slice)
+ *
+ * `SeoOpenGraphType`/`SeoTwitterCardKind` are literal web standards (OpenGraph's `og:type`,
+ * Twitter/X's card kinds) — CLOSED, because there is no host-specific value space to widen; every
+ * implementer speaks the same vocabulary. `SeoIssueSeverity` is the reference implementation's own
+ * analysis-engine taxonomy (today just `error`/`warning`/`info`), not a standard, and a host's analyzer may grade
+ * findings more finely — OPEN, via the `T | (string & {})` widening idiom (preserves autocomplete
+ * on the known values while still accepting an arbitrary host-defined string). No widening idiom
+ * was established elsewhere in this port set before this slice; this file introduces it, and
+ * `redirects.ts`/`menus.ts`/`forms.ts` follow the same idiom for their own reference-implementation-
+ * specific unions rather than inventing their own.
+ */
+export {};
+//# sourceMappingURL=seo.js.map

package/dist/core/ports/seo.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"seo.js","sourceRoot":"","sources":["../../../src/core/ports/seo.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoCG"}

package/dist/core/ports/settings.d.ts

@@ -0,0 +1,87 @@
+/**
+ * @file `AdminSettingsPort` — a layered settings ledger: global defaults, workspace overrides, and
+ * per-user overrides on top of those, resolved to one effective value per key.
+ *
+ * ## Why three layers, and why `getSettingsEffective` returns the resolved view, not the raw layers
+ *
+ * A setting's effective value is whichever of `user` (most specific), `workspace`, or `global`
+ * (least specific) has a value set, falling back to a compiled-in default when none do — that
+ * resolution is exactly what `getSettingsEffective` returns per key via `SettingResolvedValue`'s
+ * `sourceLayer`. There is deliberately no "list raw values across every layer" or "list every
+ * registered definition" method on this contract: the reference implementation does not
+ * have those routes server-side either (only the 5 operations below shipped), so a panel that needs
+ * to distinguish "the user override" from "everything else" composes two `getSettingsEffective`
+ * calls — one with `principalId` set, one without — and diffs them. That is an application-level
+ * technique, not something this port needs to special-case.
+ *
+ * ## `namespace` scopes every call
+ *
+ * Settings are grouped into namespaces (a plugin's own settings, a core feature's settings, ...);
+ * every method here operates within exactly one namespace at a time, never across all of them.
+ */
+export type SettingScope = "global" | "workspace" | "user";
+/** One key's fully-resolved effective value, as returned by `getSettingsEffective`. */
+export interface SettingResolvedValue {
+    readonly key: string;
+    readonly value: unknown;
+    /** Which layer actually supplied `value` — `"default"` means no layer had an override and this
+     *  is the compiled-in fallback. */
+    readonly sourceLayer: "user" | "workspace" | "global" | "default";
+    /** Version of the setting's definition (validation rules, default) this value was resolved
+     *  against — a host may use this to detect a stale client against a since-changed definition. */
+    readonly defVersion: number;
+}
+/** The single value written or cleared, as returned by `setSetting`/`clearSetting`. */
+export interface SettingValueResponse {
+    readonly key: string;
+    readonly scope: SettingScope;
+    readonly value: unknown;
+    /** Monotonic per-key revision counter — a host may use this for optimistic-concurrency or
+     *  audit-ordering purposes. */
+    readonly revisionSeq: number;
+}
+/** The outcome of clearing an entire namespace at one scope, as returned by
+ *  `resetSettingsNamespace`. */
+export interface SettingResetResponse {
+    readonly namespace: string;
+    readonly clearedCount: number;
+    readonly revisionSeqs: readonly number[];
+}
+export interface AdminSettingsPort {
+    /**
+     * Resolved effective values for every key in `namespace`. Pass `principalId` to resolve as that
+     * principal would see it (i.e. including their `user`-scope overrides); omit it to resolve
+     * without any user layer — see the file header for the diff technique this enables.
+     */
+    getSettingsEffective(input: {
+        namespace: string;
+    }, options?: {
+        principalId?: string;
+    }): Promise<readonly SettingResolvedValue[]>;
+    /** Writes one key at one scope. `options.principalId` is required when `input.scope === "user"`
+     *  (there is no "current user" implied server-side) and ignored otherwise. */
+    setSetting(input: {
+        namespace: string;
+        key: string;
+        scope: SettingScope;
+        value: unknown;
+    }, options?: {
+        principalId?: string;
+    }): Promise<SettingValueResponse>;
+    /** Removes one key's override at one scope, letting resolution fall through to the next layer
+     *  down. Same `principalId` contract as `setSetting`. */
+    clearSetting(input: {
+        namespace: string;
+        key: string;
+        scope: SettingScope;
+    }, options?: {
+        principalId?: string;
+    }): Promise<SettingValueResponse>;
+    /** Clears every key in `namespace` at one scope in one call — the bulk counterpart to repeated
+     *  `clearSetting` calls, and typically cheaper for a host to implement atomically. */
+    resetSettingsNamespace(input: {
+        namespace: string;
+        scope: SettingScope;
+    }): Promise<SettingResetResponse>;
+}
+//# sourceMappingURL=settings.d.ts.map

package/dist/core/ports/settings.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"settings.d.ts","sourceRoot":"","sources":["../../../src/core/ports/settings.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG;AAEH,MAAM,MAAM,YAAY,GAAG,QAAQ,GAAG,WAAW,GAAG,MAAM,CAAC;AAE3D,uFAAuF;AACvF,MAAM,WAAW,oBAAoB;IACnC,QAAQ,CAAC,GAAG,EAAE,MAAM,CAAC;IACrB,QAAQ,CAAC,KAAK,EAAE,OAAO,CAAC;IACxB;uCACmC;IACnC,QAAQ,CAAC,WAAW,EAAE,MAAM,GAAG,WAAW,GAAG,QAAQ,GAAG,SAAS,CAAC;IAClE;qGACiG;IACjG,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;CAC7B;AAED,uFAAuF;AACvF,MAAM,WAAW,oBAAoB;IACnC,QAAQ,CAAC,GAAG,EAAE,MAAM,CAAC;IACrB,QAAQ,CAAC,KAAK,EAAE,YAAY,CAAC;IAC7B,QAAQ,CAAC,KAAK,EAAE,OAAO,CAAC;IACxB;mCAC+B;IAC/B,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;CAC9B;AAED;gCACgC;AAChC,MAAM,WAAW,oBAAoB;IACnC,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,YAAY,EAAE,SAAS,MAAM,EAAE,CAAC;CAC1C;AAED,MAAM,WAAW,iBAAiB;IAChC;;;;OAIG;IACH,oBAAoB,CAClB,KAAK,EAAE;QAAE,SAAS,EAAE,MAAM,CAAA;KAAE,EAC5B,OAAO,CAAC,EAAE;QAAE,WAAW,CAAC,EAAE,MAAM,CAAA;KAAE,GACjC,OAAO,CAAC,SAAS,oBAAoB,EAAE,CAAC,CAAC;IAC5C;kFAC8E;IAC9E,UAAU,CACR,KAAK,EAAE;QAAE,SAAS,EAAE,MAAM,CAAC;QAAC,GAAG,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,YAAY,CAAC;QAAC,KAAK,EAAE,OAAO,CAAA;KAAE,EAC9E,OAAO,CAAC,EAAE;QAAE,WAAW,CAAC,EAAE,MAAM,CAAA;KAAE,GACjC,OAAO,CAAC,oBAAoB,CAAC,CAAC;IACjC;6DACyD;IACzD,YAAY,CACV,KAAK,EAAE;QAAE,SAAS,EAAE,MAAM,CAAC;QAAC,GAAG,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,YAAY,CAAA;KAAE,EAC9D,OAAO,CAAC,EAAE;QAAE,WAAW,CAAC,EAAE,MAAM,CAAA;KAAE,GACjC,OAAO,CAAC,oBAAoB,CAAC,CAAC;IACjC;0FACsF;IACtF,sBAAsB,CAAC,KAAK,EAAE;QAAE,SAAS,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,YAAY,CAAA;KAAE,GAAG,OAAO,CAAC,oBAAoB,CAAC,CAAC;CAC1G"}

package/dist/core/ports/settings.js

@@ -0,0 +1,23 @@
+/**
+ * @file `AdminSettingsPort` — a layered settings ledger: global defaults, workspace overrides, and
+ * per-user overrides on top of those, resolved to one effective value per key.
+ *
+ * ## Why three layers, and why `getSettingsEffective` returns the resolved view, not the raw layers
+ *
+ * A setting's effective value is whichever of `user` (most specific), `workspace`, or `global`
+ * (least specific) has a value set, falling back to a compiled-in default when none do — that
+ * resolution is exactly what `getSettingsEffective` returns per key via `SettingResolvedValue`'s
+ * `sourceLayer`. There is deliberately no "list raw values across every layer" or "list every
+ * registered definition" method on this contract: the reference implementation does not
+ * have those routes server-side either (only the 5 operations below shipped), so a panel that needs
+ * to distinguish "the user override" from "everything else" composes two `getSettingsEffective`
+ * calls — one with `principalId` set, one without — and diffs them. That is an application-level
+ * technique, not something this port needs to special-case.
+ *
+ * ## `namespace` scopes every call
+ *
+ * Settings are grouped into namespaces (a plugin's own settings, a core feature's settings, ...);
+ * every method here operates within exactly one namespace at a time, never across all of them.
+ */
+export {};
+//# sourceMappingURL=settings.js.map

package/dist/core/ports/settings.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"settings.js","sourceRoot":"","sources":["../../../src/core/ports/settings.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG"}

package/dist/core/ports/workspace.d.ts

@@ -0,0 +1,44 @@
+/**
+ * @file `AdminWorkspacePort` — the tenant/site the admin is currently operating on.
+ *
+ * ## This port models tenancy generically; the reference implementation's own client does not
+ *
+ * The reference implementation's API client hard-codes a single workspace id constant and bakes
+ * that constant into every route it builds (`/workspaces/${WORKSPACE_ID}/...`) — it is a
+ * single-workspace-per-instance product today, and its client reflects that. This port deliberately does
+ * not carry a workspace id as a parameter on any method here: each method operates on "the
+ * workspace the current client/transport is scoped to". A genuinely multi-workspace host resolves
+ * *which* workspace that is at the transport/route-group-factory layer (a later, per-host slice —
+ * e.g. constructing one client per workspace, or a factory parameterized by workspace id), not by
+ * threading an id through every call on this port. Baking a `workspaceId` parameter into every
+ * method here would be designing for a host shape (multi-workspace-per-client) that does not yet
+ * exist anywhere in the corpus this port was derived from.
+ *
+ * ## `deleteWorkspace` exists on the contract; the reference implementation always refuses it
+ *
+ * The reference implementation's `DELETE /workspaces/:id` route is real and reachable, but its
+ * write-path unconditionally rejects with a `LAST_WORKSPACE`-class conflict when deleting would
+ * leave zero workspaces — which, in a single-workspace-per-instance deployment, is every call. The
+ * method stays on this port because the guard is a product policy of *today's* reference
+ * deployment, not a
+ * statement that workspace deletion is meaningless in general; a host that supports genuinely
+ * disposable workspaces needs this method to work. A panel built against this port should not
+ * assume `deleteWorkspace` succeeds just because the call is well-formed and authorized.
+ */
+/** The workspace (tenant/site) itself. */
+export interface AdminWorkspace {
+    readonly id: string;
+    readonly name: string;
+    readonly slug: string;
+    readonly createdAt: string;
+}
+export interface AdminWorkspacePort {
+    getWorkspace(): Promise<AdminWorkspace>;
+    updateWorkspace(patch: {
+        name?: string;
+        slug?: string;
+    }): Promise<AdminWorkspace>;
+    /** May unconditionally reject — see the file header. */
+    deleteWorkspace(): Promise<void>;
+}
+//# sourceMappingURL=workspace.d.ts.map

package/dist/core/ports/workspace.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"workspace.d.ts","sourceRoot":"","sources":["../../../src/core/ports/workspace.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AAEH,0CAA0C;AAC1C,MAAM,WAAW,cAAc;IAC7B,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;CAC5B;AAED,MAAM,WAAW,kBAAkB;IACjC,YAAY,IAAI,OAAO,CAAC,cAAc,CAAC,CAAC;IACxC,eAAe,CAAC,KAAK,EAAE;QAAE,IAAI,CAAC,EAAE,MAAM,CAAC;QAAC,IAAI,CAAC,EAAE,MAAM,CAAA;KAAE,GAAG,OAAO,CAAC,cAAc,CAAC,CAAC;IAClF,wDAAwD;IACxD,eAAe,IAAI,OAAO,CAAC,IAAI,CAAC,CAAC;CAClC"}

package/dist/core/ports/workspace.js

@@ -0,0 +1,29 @@
+/**
+ * @file `AdminWorkspacePort` — the tenant/site the admin is currently operating on.
+ *
+ * ## This port models tenancy generically; the reference implementation's own client does not
+ *
+ * The reference implementation's API client hard-codes a single workspace id constant and bakes
+ * that constant into every route it builds (`/workspaces/${WORKSPACE_ID}/...`) — it is a
+ * single-workspace-per-instance product today, and its client reflects that. This port deliberately does
+ * not carry a workspace id as a parameter on any method here: each method operates on "the
+ * workspace the current client/transport is scoped to". A genuinely multi-workspace host resolves
+ * *which* workspace that is at the transport/route-group-factory layer (a later, per-host slice —
+ * e.g. constructing one client per workspace, or a factory parameterized by workspace id), not by
+ * threading an id through every call on this port. Baking a `workspaceId` parameter into every
+ * method here would be designing for a host shape (multi-workspace-per-client) that does not yet
+ * exist anywhere in the corpus this port was derived from.
+ *
+ * ## `deleteWorkspace` exists on the contract; the reference implementation always refuses it
+ *
+ * The reference implementation's `DELETE /workspaces/:id` route is real and reachable, but its
+ * write-path unconditionally rejects with a `LAST_WORKSPACE`-class conflict when deleting would
+ * leave zero workspaces — which, in a single-workspace-per-instance deployment, is every call. The
+ * method stays on this port because the guard is a product policy of *today's* reference
+ * deployment, not a
+ * statement that workspace deletion is meaningless in general; a host that supports genuinely
+ * disposable workspaces needs this method to work. A panel built against this port should not
+ * assume `deleteWorkspace` succeeds just because the call is well-formed and authorized.
+ */
+export {};
+//# sourceMappingURL=workspace.js.map

package/dist/core/ports/workspace.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"workspace.js","sourceRoot":"","sources":["../../../src/core/ports/workspace.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG"}