@sanity/ailf-studio 0.1.26 → 0.2.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Sanity.io
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/dist/index.d.ts

@@ -7,22 +7,24 @@ import { DocumentRef } from './document-ref.js';
  * actions/GraduateToNativeAction.tsx
  *
  * Sanity Studio document action that "graduates" a mirrored task to
- * a native task by removing the `origin` field.
+ * a native (Studio-owned) task by changing the `ownership` field from
+ * "repo" to "studio".
  *
- * This is a one-way, irreversible operation. Once graduated:
+ * This is a one-way operation. Once graduated:
  * - The task becomes fully editable in Studio
- * - Future pipeline mirror syncs will NOT overwrite it (the mirror
- *   uses createOrReplace with the same _id, but since origin is gone,
- *   the document-level readOnly check returns false and the task
- *   behaves like any other native task)
+ * - Future pipeline mirror syncs will skip this document (the mirror
+ *   step checks `ownership` and skips documents with `ownership: "studio"`)
+ * - The `origin` field is preserved as provenance — you can always
+ *   see where the task originally came from
  * - The task's _id is unchanged — it keeps the mirror prefix
  *   (ailf.task.mirror.*) but that's just an ID string, not a
  *   behavioral marker
  *
- * The action only appears on ailf.task documents that have an `origin`
- * field (i.e., mirrored tasks). Native tasks never see it.
+ * The action only appears on ailf.task documents that have
+ * `ownership: "repo"` (i.e., active mirrors). Native tasks and
+ * already-graduated tasks never see it.
  *
- * @see docs/exec-plans/tasks-as-content/phase-5-content-lake-mirroring.md
+ * @see docs/exec-plans/task-lifecycle/phase-1-ownership.md
  */
 
 declare const GraduateToNativeAction: DocumentActionComponent;
@@ -75,15 +77,29 @@ declare function ReleasePicker(props: StringInputProps): react_jsx_runtime.JSX.E
 /**
  * components/MirrorBanner.tsx
  *
- * Informational banner shown at the top of mirrored task documents.
- * Communicates that the task is managed in an external repo and links
- * to the source file on GitHub.
+ * Informational banner shown at the top of task documents that have
+ * origin provenance (both active mirrors and graduated tasks).
  *
- * Paired with `SyncStatusBadge` to show both the source and freshness
- * of the mirror.
+ * For active mirrors (`ownership: "repo"`): communicates that the task
+ * is managed in an external repo and links to the source file on GitHub.
  *
- * @see docs/exec-plans/tasks-as-content/phase-5-content-lake-mirroring.md
+ * For graduated tasks (`ownership: "studio"` with origin): shows
+ * provenance info about where the task originally came from.
+ *
+ * Paired with `SyncStatusBadge` to show sync freshness for active mirrors.
+ *
+ * @see docs/exec-plans/task-lifecycle/phase-1-ownership.md
  */
+interface GitAuthorInfo {
+    gitName?: string;
+    gitEmail?: string;
+    githubUsername?: string;
+}
+interface GraduatedByInfo {
+    sanityId?: string;
+    name?: string;
+    email?: string;
+}
 interface MirrorBannerProps {
     origin: {
         repo?: string;
@@ -93,9 +109,15 @@ interface MirrorBannerProps {
         branch?: string;
         commitSha?: string;
         lastSyncedAt?: string;
+        author?: GitAuthorInfo;
+        lastEditor?: GitAuthorInfo;
+        graduatedAt?: string;
+        graduatedBy?: GraduatedByInfo;
     };
+    /** Task ownership — "repo" for active mirrors, "studio" for graduated */
+    ownership?: string;
 }
-declare function MirrorBanner({ origin }: MirrorBannerProps): react_jsx_runtime.JSX.Element;
+declare function MirrorBanner({ origin, ownership }: MirrorBannerProps): react_jsx_runtime.JSX.Element;
 
 /**
  * components/SyncStatusBadge.tsx
@@ -227,6 +249,18 @@ declare const GLOSSARY: {
     readonly change: "Whether the change is meaningful: improved, regressed, or unchanged (within the noise threshold).";
     readonly lowScoringJudgments: "The grading model's explanations for tests that scored below 70/100.";
     readonly judgmentReason: "The grading model's natural language explanation of what went wrong.";
+    readonly healthStrong: "Feature areas scoring 80 or above. The docs are working well for these features — AI agents produce correct, complete implementations.";
+    readonly healthAttention: "Feature areas scoring 70–79. These are okay but could be improved — there may be gaps in specific dimensions like doc coverage or code correctness.";
+    readonly healthWeak: "Feature areas scoring below 70. The docs are not providing enough support for AI agents to implement these features correctly.";
+    readonly negativeDocLiftMetric: "Number of areas where the documentation actually hurts AI performance — the model scores higher without docs than with them. This usually means the docs contain outdated patterns or incorrect examples.";
+    readonly weakAreas: "Feature areas where the overall score is below 70. These need the most attention — low scores mean AI agents consistently struggle to implement these features.";
+    readonly docsHurt: "Areas where the floor score (no docs) is higher than the ceiling score (with docs). The documentation is actively misleading the model. These docs need to be rewritten or removed.";
+    readonly retrievalIssues: "Areas where AI agents can find less than 70% of the available doc quality. The docs exist and are good, but agents can't discover them through search. Consider improving page titles, metadata, or search engine indexing.";
+    readonly dimWeaknesses: "Individual grading dimensions scoring below 50 within an area. These are the specific skills where AI agents fail most — task completion (can it build the feature?), code correctness (is the code right?), or doc coverage (did it use the docs?).";
+    readonly efficiencyAnomalies: "Areas where agent efficiency exceeds 100% — meaning agents perform better with self-found docs than with gold-standard docs injected directly. This can indicate doc quality issues (injected docs confuse the model) or agent memorization.";
+    readonly docLiftWins: "Areas where documentation boosts AI performance by 5 or more points. Higher doc lift means the docs are providing crucial information that the model doesn't already know.";
+    readonly retrievalExcellence: "Areas where AI agents successfully find and use at least 85% of the available doc quality through web search. Good retrieval means your docs are well-indexed and easy for agents to discover.";
+    readonly strengths: "What's working well: high-scoring areas, dimensions where the docs are strong, and areas where AI agents successfully find and use the documentation.";
     readonly recommendations: "Prioritized remediation plan from gap analysis. Each recommendation identifies a documentation problem, the affected feature area, and the estimated score lift from fixing it.";
     readonly totalPotentialLift: "Aggregate potential score lift if all identified gaps were fixed. This is a conservative estimate — each gap targets the median of non-bottlenecked dimensions, not 100.";
     readonly failureMode: "The type of documentation problem: missing-docs (functionality not covered), incorrect-docs (factual errors), outdated-docs (stale API/patterns), or poor-structure (hard to find/understand).";
@@ -468,6 +502,8 @@ declare const taskSchema: {
         description: string;
         id: string;
         origin: string;
+        ownership: string;
+        status: string;
     }, Record<string, unknown>> | undefined;
 };