@piwitests/server 0.18.1 → 0.19.0

package/.output/server/chunks/build/{help-content-DmFnuhNu.mjs → help-content-C876a9WD.mjs}

@@ -8,17 +8,17 @@ const HELP_TOPICS = {
   "home.trend-bars": {
     title: "Run history bars",
     text: "One bar per full run (up to 20), oldest left → newest right. Green = pass, red = fail, amber = passed with flaky tests, gray = skipped/unknown. Click a bar to open that run.",
-    doc: "ui-overview#home-page"
+    doc: "ui-overview#home"
   },
   "home.tendency": {
     title: "Tendency",
     text: "Derived from the last 5 full runs. Failing = latest run failed; flaky = pass/fail mixed or flaky tests seen in the window; passing = all recent runs green.",
-    doc: "ui-overview#home-page"
+    doc: "ui-overview#home"
   },
   "home.project-health": {
     title: "Project health",
     text: "Every project at a glance — run history bars and a tendency badge so you can immediately see which project needs attention. Only full runs count.",
-    doc: "ui-overview#home-page"
+    doc: "ui-overview#home"
   },
   "home.get-started": {
     title: "Get started",
@@ -54,7 +54,7 @@ const HELP_TOPICS = {
   "analytics.cluster-landscape": {
     title: "Failure clusters",
     text: "Open failure clusters across all projects — the biggest and oldest unresolved root causes. Clusters outlive run retention, so this works on long horizons.",
-    doc: "failure-clustering"
+    doc: "ai-diagnosis#failure-clustering"
   },
   "analytics.regression-velocity": {
     title: "Regression velocity",
@@ -77,7 +77,13 @@ const HELP_TOPICS = {
   "projects.table": {
     title: "Projects",
     text: "Every project that has reported results, with its latest run, pass rate and activity. Click a row to drill in.",
-    doc: "ui-overview#projects-page"
+    doc: "ui-overview#projects"
+  },
+  "project.import": {
+    title: "Importing past runs",
+    text: "Upload the archives Playwright writes to blob-report/ to backfill runs from before you adopted Piwi. One archive becomes one run, complete with traces and screenshots, and re-uploading the same archive changes nothing. Imports are silent by design — no notifications, AI diagnosis or regression signals, so a backfill never pages the team about months-old failures.",
+    doc: "importing-runs",
+    envVars: ["PIWI_IMPORT_MAX_BYTES"]
   },
   // ── Project detail ────────────────────────────────────────────────────
   "project.run-scope": {
@@ -95,6 +101,11 @@ const HELP_TOPICS = {
     text: "Tests that fail intermittently across runs. Impact estimates wasted CI time; the score (0–100) rates severity and root cause explains why.",
     doc: "flaky-tests#flaky-test-detection"
   },
+  "project.quarantine": {
+    title: "Quarantine",
+    text: "A quarantined test still runs and still reports — it is only excluded from the CI gate’s verdict. Passing runs accumulate as a streak, so a test that recovers is flagged ready to release instead of staying quarantined forever.",
+    doc: "flaky-tests#quarantine-with-a-way-out"
+  },
   "project.performance": {
     title: "Performance",
     text: "Duration trends for the suite — average and P90 (the slowest 10% threshold). Use it to catch tests getting steadily slower.",
@@ -109,7 +120,7 @@ const HELP_TOPICS = {
   "project.slowest-tests": {
     title: "Slowest tests",
     text: "The tests taking the most time, ranked. Optimizing the top entries shortens your overall run the fastest.",
-    doc: "ui-overview#performance-page"
+    doc: "flaky-tests#performance"
   },
   "project.run-compare": {
     title: "Run comparison",
@@ -217,6 +228,13 @@ const HELP_TOPICS = {
     text: "The source around the failing line and the callers above it — captured from the failure’s call stack — so you can read where it broke, and the code that led there, without opening your editor. When the execution has a trace, this deepens into the complete call stack with the real source of every frame, read from the trace’s embedded files.",
     doc: "ui-overview#trace-powered-deep-views"
   },
+  "export.offline": {
+    // Deliberately avoids the word "Export": the hint sits beside a button with
+    // that label, and a substring role query would match both.
+    title: "Reading this offline",
+    text: "Takes this investigation out of the dashboard as a file that needs no network and no Piwi server. HTML is one self-contained page with screenshots and video embedded; ZIP adds the raw artifacts — trace archives, full-size video, logs — plus a machine-readable data.json; PDF is the HTML printed from your browser. Evidence past the size budget is listed in the report as omitted rather than dropped quietly.",
+    envVars: ["PIWI_EXPORT_MAX_INLINE_BYTES", "PIWI_EXPORT_MAX_BYTES", "PIWI_EXPORT_MAX_CASES"]
+  },
   "case.artifacts": {
     title: "Artifacts",
     text: "Traces, attachments, console output and network requests captured for this execution — the raw material behind the result.",
@@ -297,6 +315,11 @@ const HELP_TOPICS = {
   "cluster.triage": {
     text: "Track a cluster’s state: set its status, add triage notes, or extract a subset of failures into a separate cluster."
   },
+  "cluster.resolution": {
+    title: "Resolution",
+    text: "Recorded when a full run turns this cluster green: when the fix landed, how long the cluster stayed open, and whether the change matched the diagnosed files. If the failure comes back, the cluster is marked as regressed rather than quietly reopened.",
+    doc: "ai-diagnosis#did-the-fix-work"
+  },
   "cluster.evidence": {
     title: "Test evidence",
     text: "The concrete artifacts behind this cluster — screenshots, signals and traces from affected tests — gathered for review and AI diagnosis.",
@@ -477,6 +500,12 @@ const HELP_TOPICS = {
     text: "Thresholds for flagging oversized per-test timeouts and stale test.slow() marks. Opportunities are recomputed at read time, so changes apply to existing runs immediately.",
     doc: "flaky-tests#performance"
   },
+  "settings.pr-feedback": {
+    title: "Pull-request feedback",
+    text: "When a run finishes on a branch with an open pull request, Piwi can post a summary comment — new failures separated from pre-existing ones, with suggested locators — and set a commit status. Needs PIWI_SITE_URL and an SCM token with write access.",
+    doc: "ci#pull-request-feedback",
+    envVars: ["PIWI_SITE_URL"]
+  },
   "settings.auto-diagnose": {
     title: "Auto-diagnose",
     text: "When a run finishes, up to 3 new failure clusters are diagnosed automatically — each diagnosis is one research call (when a research model is configured) plus one diagnosis call — and new clusters get human-readable titles in one batched call. Requires the diagnosis model to be configured.",
@@ -527,7 +556,7 @@ const HELP_TOPICS = {
   "account.connected-accounts": {
     title: "Connected accounts",
     text: "Sign in with an OAuth provider (Google or GitHub). Providers are configured by an operator through environment variables; one provider can be linked per account.",
-    doc: "authentication#oauth-sign-in",
+    doc: "authentication#oauth-google-github",
     envVars: [
       "PIWI_OAUTH_GOOGLE_CLIENT_ID",
       "PIWI_OAUTH_GOOGLE_CLIENT_SECRET",
@@ -606,4 +635,4 @@ function helpEnvVars(key) {
 }
 
 export { HELP_TOPICS as H, helpEnvVars as h };
-//# sourceMappingURL=help-content-DmFnuhNu.mjs.map
+//# sourceMappingURL=help-content-C876a9WD.mjs.map

package/.output/server/chunks/build/help-content-C876a9WD.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"help-content-C876a9WD.mjs","sources":["../../../../node_modules/.cache/nuxt/.nuxt/dist/server/_nuxt/help-content-C876a9WD.js"],"names":[],"mappings":"","x_google_ignoreList":[0]}