laxy-verify 1.1.21 → 1.1.23

package/README.md

@@ -1,263 +1,276 @@
-# laxy-verify
-
-A frontend verification CLI that catches build breaks, regressions, and client-visible issues before you ship.
-
-`laxy-verify` runs production build checks, Lighthouse, tiered verify E2E, and plan-gated verification for Free, Pro, and Pro+ accounts.
-It is built around three simple questions:
-
-- Free: "Any critical issues right now?"
-- Pro: "Ready to show a client?"
-- Pro+: "Ready for production?"
-
-```bash
-npx laxy-verify --init --run
-npx laxy-verify .
-npx laxy-verify . --plan-override pro
-npx laxy-verify login
-npx laxy-verify whoami
-npx laxy-verify --help
-```
-
-What you get from one run:
-
-- a verification grade: `Gold`, `Silver`, `Bronze`, or `Unverified`
-- a decision-oriented verdict such as `client-ready`, `release-ready`, `hold`, or `investigate`
-- `.laxy-result.json` for automation
-- `laxy-verify-report.md` on paid plans for human review and AI handoff
-
-## Quick Start
-
-### 1. Run it on a frontend app
-
-```bash
-cd your-project
-npx laxy-verify .
-```
-
-This runs the default verification flow in the current app directory.
-
-### 2. Generate config and CI workflow
-
-```bash
-npx laxy-verify --init
-```
-
-This creates:
-
-- `.laxy.yml`
-- `.github/workflows/laxy-verify.yml`
-
-### 3. Commit the workflow
-
-Once committed, each PR gets a verification run, grade output, and optional GitHub reporting.
-
-### 4. Unlock paid plan features
-
-```bash
-npx laxy-verify login
-npx laxy-verify whoami
-```
-
-For CI, set `LAXY_TOKEN` instead of using interactive login.
-
-```yaml
-env:
-  LAXY_TOKEN: ${{ secrets.LAXY_TOKEN }}
-```
-
-## What It Checks
-
-- production build success
-- Lighthouse thresholds
-- verify E2E scenarios for real user flows
-- Pro+ viewport and visual regression evidence
-- plan-aware verdicts for local runs and CI
-
-## Verification Tiers
-
-| Plan | Question it answers |
-|------|---------------------|
-| Free | Any critical issues right now? |
-| Pro | Ready to show a client? |
-| Pro+ | Ready for production? |
-
-## Grades
-
-| Grade | Meaning |
-|-------|---------|
-| Gold | Build passed + E2E passed + Lighthouse passed + Pro+ viewport evidence passed |
-| Silver | Build passed + E2E passed |
-| Bronze | Build passed |
-| Unverified | Build failed |
-
-## Plan Differences
-
-| Feature | Free | Pro | Pro+ |
-|---------|------|-----|------|
-| Build verification | Yes | Yes | Yes |
-| Lighthouse | 1 run | 3 runs | 3 runs |
-| Verify E2E | Smoke checks | Client-facing flow checks | Client-facing flow checks + release evidence |
-| Detailed report view | No | Yes | Yes |
-| `laxy-verify-report.md` export | No | Yes | Yes |
-| Multi-viewport verification | No | No | Yes |
-| Visual diff | No | No | Yes |
-| Failure analysis signals | No | No | Yes |
-
-Free tells you whether the app is basically standing.
-Pro tells you whether the app is strong enough to call client-ready.
-Pro+ adds the extra evidence needed for a real release-ready call.
-
-## Sample Output
-
-```text
-Plan: Pro+
-Grade: Gold
-Verdict: release-ready
-
-Passed:
-- production build
-- Lighthouse thresholds
-- core E2E flows
-- desktop, tablet, and mobile viewport checks
-
-Artifacts:
-- .laxy-result.json
-- laxy-verify-report.md
-```
-
-## Configuration
-
-All fields are optional in `.laxy.yml`.
-
-```yaml
-framework: "auto"
-build_command: ""
-dev_command: ""
-package_manager: "auto"
-port: 3000
-build_timeout: 300
-dev_timeout: 60
-lighthouse_runs: 1
-
-thresholds:
-  performance: 70
-  accessibility: 85
-  seo: 80
-  best_practices: 80
-
-fail_on: "bronze"
-```
-
-Typical cases:
-
-- raise `fail_on` to `silver` or `gold` in CI when you want stricter gates
-- set `framework`, `build_command`, or `dev_command` if auto-detection is not enough
-- increase `lighthouse_runs` when you want more stable performance evidence
-
-## CLI Options
-
-```text
-npx laxy-verify [project-dir]
-
-Options:
-  --format console|json
-  --ci
-  --config <path>
-  --fail-on unverified|bronze|silver|gold
-  --skip-lighthouse
-  --plan-override free|pro|pro_plus
-  --badge
-  --init
-  --multi-viewport
-  --help
-
-Subcommands:
-  login [email]
-  logout
-  whoami
-```
-
-`--plan-override` is for downgrade testing only.
-Example: if your account is Pro+, you can run `--plan-override pro` or `--plan-override free` to verify the lower-tier behavior without changing your subscription.
-It will reject upgrades above your real entitlement.
-
-## Result Files
-
-Each run writes `.laxy-result.json`.
-
-Paid plans also write a readable markdown summary to `laxy-verify-report.md`.
-
-- `Pro`: client-ready delivery report
-- `Pro+`: release-readiness report with viewport and visual evidence
-
-Exit behavior follows the verification verdict, not just the legacy grade.
-
-- `build-failed` -> exit 1
-- `hold` -> exit 1
-- `Pro+ investigate` -> exit 1
-- plain lower-tier pass states can still exit 0
-
-```json
-{
-  "grade": "Gold",
-  "timestamp": "2026-04-09T09:00:00Z",
-  "build": { "success": true, "durationMs": 12000, "errors": [] },
-  "e2e": { "passed": 5, "failed": 0, "total": 5, "results": [] },
-  "lighthouse": { "performance": 82, "accessibility": 94, "seo": 90, "bestPractices": 92, "runs": 3 },
-  "multiViewport": {
-    "allPassed": true,
-    "summary": "Desktop, tablet, and mobile checks passed."
-  },
-  "visualDiff": {
-    "verdict": "pass",
-    "differencePercentage": 0
-  },
-  "verification": {
-    "tier": "pro_plus",
-    "report": { "verdict": "release-ready" }
-  },
-  "exitCode": 0,
-  "_plan": "pro_plus"
-}
-```
-
-### `laxy-verify-report.md`
-
-For Pro and Pro+ runs, the markdown report is designed to be easy to read and easy to paste into an AI coding tool.
-
-It includes:
-
-- the main decision in plain English
-- what passed
-- blockers and warnings
-- exact verification evidence
-- failed E2E scenarios
-- a `Copy For AI` section you can paste directly into Codex, Cursor, Claude, or ChatGPT
-
-## Environment Notes
-
-- Best on current LTS Node releases. `Node 20.18+` is recommended.
-- Monorepos should point `laxy-verify` at the actual app directory.
-- `playwright` is optional. The CLI can run without it.
-- Pro+ viewport and visual checks increase runtime.
-
-## Regression Fixtures
-
-The repo also includes dedicated regression fixtures under `.qa-regression-fixtures/`.
-They intentionally break build, navigation, coverage, performance, viewport behavior, and visual stability so the verifier can be tested against known failure modes.
-
-## Limitations
-
-- Monorepos require targeting the app subdirectory explicitly.
-- Dev-server-based Lighthouse can differ from production hosting.
-- Pro+ visual diff and viewport checks increase runtime.
-- Local verification is most stable on current LTS Node releases.
-
-## Links
-
-- GitHub: https://github.com/psungmin24/Laxy/tree/main/laxy-verify
-- Issues: https://github.com/psungmin24/Laxy/issues
-
-## License
-
-MIT
+# laxy-verify
+
+`laxy-verify` is a deployment blocker gate for frontend apps.
+
+Its job is simple:
+
+- catch the broken build before merge
+- catch the broken user flow before QA or client review
+- catch the obvious mobile or viewport break before release
+
+It runs your production build, Lighthouse, and user-visible verification flows in one command, then leaves one decision and one evidence trail for local use or CI.
+
+## Why use this instead of stitching tools together?
+
+Most teams already have some mix of:
+
+- `npm run build`
+- Lighthouse
+- Playwright or smoke checks
+- CI status rules
+
+The gap is not "can these tools exist together?" The gap is "who turns that pile of output into a safe merge or release decision?"
+
+`laxy-verify` gives you:
+
+- one command instead of a custom build plus audit plus smoke-check script stack
+- one result file instead of scattered logs
+- one blocker-first decision instead of "build passed, but do we actually trust this release?"
+- a faster setup path with `--init` for config plus GitHub Actions
+
+This is most useful if you ship frontend apps and want a practical gate before:
+
+- merge
+- client review
+- QA handoff
+- production release
+
+## The failures it is meant to catch
+
+Use `laxy-verify` when you want to catch things like:
+
+- the production build passes locally but fails in CI
+- the app opens, but a key button or form flow is broken
+- desktop looks fine, but a mobile CTA is pushed out of view
+- Lighthouse looks acceptable, but the user-visible path is still not safe to ship
+- a PR needs a clear hold reason instead of a vague "something failed"
+
+## What it actually checks
+
+A standard run includes:
+
+- production build success
+- Lighthouse thresholds (3 runs for stable evidence)
+- E2E scenarios for user-visible flows
+- multi-viewport checks (desktop, tablet, mobile)
+- blocker-aware reporting and release decisions
+
+With a logged-in account, additional checks run:
+
+- security audit
+- visual diff evidence
+- stability pass (second E2E run)
+
+## What you get from one run
+
+- a release decision such as `quick-pass`, `client-ready`, `release-ready`, `hold`, or `investigate`
+- a verification grade: `Gold`, `Silver`, `Bronze`, or `Unverified`
+- `.laxy-result.json` for CI and automation
+- `laxy-verify-report.md` for human review and AI handoff
+
+Grades still exist, but they are not the main point. The main point is whether the run found blockers you should stop on.
+
+## Quick start
+
+Run it on a frontend app:
+
+```bash
+cd your-project
+npx laxy-verify .
+```
+
+Generate config plus CI workflow:
+
+```bash
+npx laxy-verify --init
+```
+
+That creates:
+
+- `.laxy.yml`
+- `.github/workflows/laxy-verify.yml`
+
+Log in to unlock paid plan features:
+
+```bash
+npx laxy-verify login
+npx laxy-verify whoami
+```
+
+For CI, set `LAXY_TOKEN` instead of interactive login:
+
+```yaml
+env:
+  LAXY_TOKEN: ${{ secrets.LAXY_TOKEN }}
+```
+
+## Example workflow
+
+1. Run `npx laxy-verify .` locally before opening or merging a PR.
+2. Fix broken builds, broken flows, and visible regressions.
+3. Commit `.laxy.yml`.
+4. Run `npx laxy-verify --init`.
+5. Let the GitHub Action apply the same gate on every PR.
+
+## Example output
+
+```text
+Decision: release-ready
+Grade: Gold
+
+Passed:
+- production build
+- Lighthouse thresholds
+- core user flows
+- desktop, tablet, and mobile viewport checks
+
+Artifacts:
+- .laxy-result.json
+- laxy-verify-report.md
+```
+
+## The decision it helps you make
+
+`laxy-verify` answers a delivery decision, not just a score:
+
+- Would this break for real users right now?
+- What would block a client demo or QA handoff?
+- Is there enough evidence to merge or release with confidence?
+
+Log in to unlock deeper checks (security audit, visual diff, stability pass).
+
+## Grades
+
+| Grade | Meaning |
+|---|---|
+| Gold | Build passed, E2E passed, Lighthouse passed, and release-level evidence passed |
+| Silver | Build passed and E2E passed |
+| Bronze | Build passed |
+| Unverified | Build failed |
+
+Default Lighthouse thresholds:
+
+- Performance `>= 70`
+- Accessibility `>= 85`
+- SEO `>= 80`
+- Best Practices `>= 80`
+
+## Config
+
+All fields in `.laxy.yml` are optional.
+
+```yaml
+framework: auto
+build_command: ""
+dev_command: ""
+package_manager: auto
+port: 3000
+build_timeout: 300
+dev_timeout: 60
+lighthouse_runs: 1
+fail_on: bronze
+
+thresholds:
+  performance: 70
+  accessibility: 85
+  seo: 80
+  best_practices: 80
+
+crawl: false
+max_crawl_depth: 3
+max_crawl_pages: 10
+browsers:
+  - chromium
+```
+
+Useful adjustments:
+
+- raise `fail_on` in CI when you want stricter gates
+- set `build_command` or `dev_command` if auto-detection is not enough
+- increase `lighthouse_runs` for more stable performance evidence
+- point the CLI at the actual app directory in a monorepo
+
+## CLI
+
+```text
+npx laxy-verify [project-dir]
+
+Options:
+  --format console|json
+  --ci
+  --config <path>
+  --fail-on unverified|bronze|silver|gold
+  --skip-lighthouse
+  --plan-override free|pro|pro_plus
+  --badge
+  --init
+  --multi-viewport
+  --help
+
+Subcommands:
+  login [email]
+  logout
+  whoami
+```
+
+`--plan-override` is for downgrade testing only. It can simulate lower tiers, but it will not let you exceed your real entitlement.
+
+## Result files
+
+Every run writes `.laxy-result.json`.
+
+When the run finds something worth reviewing, it also writes `laxy-verify-report.md`.
+
+Typical use:
+
+- `.laxy-result.json` for CI parsing and machine decisions
+- `laxy-verify-report.md` for human review, PR discussion, or AI-assisted fixes
+
+The markdown report is designed to be readable and easy to paste into coding tools.
+
+It includes:
+
+- the main stop-or-ship decision in plain English
+- what passed
+- blockers and warnings
+- exact verification evidence
+- failed scenarios
+- a `Copy For AI` section
+
+## What this is good at
+
+Use `laxy-verify` when you want:
+
+- a merge or release gate for frontend apps
+- one repeatable command for build plus audit plus visible-flow verification
+- a decision that non-authors can understand
+- JSON output for automation without building your own wrapper
+
+## What this is not
+
+`laxy-verify` is not trying to replace:
+
+- your full Playwright suite
+- deep visual QA by designers
+- production observability
+- manual exploratory testing
+
+It is a pre-merge and pre-release verification layer, not your entire quality system.
+
+## Limitations
+
+- monorepos should target the real app subdirectory
+- dev-server-based Lighthouse is not identical to production hosting
+- visual diff and viewport checks increase runtime
+- best stability is on current LTS Node releases
+
+## Requirements
+
+- Node `>=20.18.0 <25`
+- a frontend app with a runnable build flow
+- optional: `playwright` if your project already uses it
+
+## Links
+
+- GitHub: https://github.com/SUNgm24/Laxy/tree/main/laxy-verify
+- Issues: https://github.com/SUNgm24/Laxy/issues

package/dist/cli.js

@@ -162,7 +162,7 @@ function summarizeViewportIssues(scores, thresholds) {
 function consoleOutput(result) {
     const gradeLabel = result.grade;
     const checkEmoji = result.grade !== "Unverified" ? " OK" : "";
-    console.log(`\n  Laxy Verify ${gradeLabel}${checkEmoji}`);
+    console.log(`\n  Laxy Verify: blocker check ${gradeLabel}${checkEmoji}`);
     console.log(`  Build: ${result.build.success ? `OK (${result.build.durationMs}ms)` : "FAILED"}`);
     if (result.build.errors.length > 0) {
         console.log("  Errors:");
@@ -216,10 +216,10 @@ function consoleOutput(result) {
         // failure_analysis: Pro+에서 서버가 활성화하면 warnings 전체 설명 + evidence 전체 표시
         const verboseFailure = isPro && (result._verbose_failure ?? isPro);
         const failureAnalysis = isProPlus && (result._failure_analysis ?? isProPlus);
-        console.log(`  Verification tier: ${view.tier}`);
-        console.log(`  Question: ${view.question}`);
-        console.log(`  Verdict: ${view.verdict} (${view.confidence})`);
-        console.log(`  Summary: ${view.summary}`);
+        console.log(`  Verification depth: ${view.tier}`);
+        console.log(`  Decision question: ${view.question}`);
+        console.log(`  Decision: ${view.verdict} (${view.confidence})`);
+        console.log(`  Why it stopped here: ${view.summary}`);
         // Pro/Pro+: 체크 통과 목록 요약
         if (isPro && view.passes.length > 0) {
             const passedChecks = view.passes.filter((p) => p.passed).map((p) => p.label);
@@ -231,7 +231,7 @@ function consoleOutput(result) {
         }
         // Blockers: 제목은 모든 티어, Fix 액션은 verbose_failure(Pro+) 이상에서 표시
         if (view.blockers.length > 0) {
-            console.log("  Blockers:");
+            console.log("  Deployment blockers:");
             for (const blocker of view.blockers) {
                 console.log(`    - ${blocker.title}`);
                 if (verboseFailure)
@@ -240,7 +240,7 @@ function consoleOutput(result) {
         }
         // Warnings: Pro/Pro+에서만 표시, Review 액션은 failure_analysis(Pro+)에서 표시
         if (isPro && view.warnings.length > 0) {
-            console.log("  Warnings:");
+            console.log("  Risks to review:");
             for (const warning of view.warnings) {
                 console.log(`    - ${warning.title}`);
                 if (failureAnalysis)
@@ -256,7 +256,7 @@ function consoleOutput(result) {
         const evidenceLimit = failureAnalysis ? view.failureEvidence.length : verboseFailure ? 3 : 2;
         const evidenceToShow = view.failureEvidence.slice(0, evidenceLimit);
         if (evidenceToShow.length > 0) {
-            console.log("  Evidence:");
+            console.log("  Evidence collected:");
             for (const item of evidenceToShow)
                 console.log(`    - ${item}`);
         }
@@ -272,24 +272,20 @@ function consoleOutput(result) {
         console.log(`  Report: ${path.basename(result.markdownReportPath)}`);
     }
     console.log(`  Exit code: ${result.exitCode}`);
-    if ((result.grade === "Silver" || result.grade === "Bronze") && (!result._plan || result._plan === "free")) {
-        console.log("\n  Unlock deeper verification and Gold-grade confidence with Pro or Pro+:");
-        console.log("  https://laxy-blue.vercel.app/pricing");
-    }
 }
 async function run() {
     const args = parseArgs();
     if (args.help) {
         console.log(`
   laxy-verify v${package_json_1.default.version}
-  Frontend quality gate: build + Lighthouse verification
+  Deployment blocker gate for frontend apps
 
   Usage:
     npx laxy-verify [project-dir] [options]
     npx laxy-verify <subcommand>
 
   Subcommands:
-    login [email]     Log in to unlock Pro/Pro+ features
+    login [email]     Log in to unlock deeper reports and release evidence
     logout            Remove saved credentials
     whoami            Show current login status
 
@@ -308,15 +304,15 @@ async function run() {
     --help            Show this help
 
   Exit codes:
-    0   Grade meets or exceeds fail_on threshold
-    1   Grade worse than fail_on, or build failed
+    0   Current verification gate passed
+    1   Verification found blockers, or build failed
     2   Configuration error
 
   Examples:
     npx laxy-verify --init --run        # Setup + first verification
     npx laxy-verify .                   # Run in current directory
     npx laxy-verify . --ci              # CI mode
-    npx laxy-verify . --fail-on silver  # Require Silver or better
+    npx laxy-verify . --fail-on silver  # Block Bronze or worse
 
   Docs: https://github.com/psungmin24/laxy-verify
 `);

package/dist/comment.js

@@ -40,7 +40,6 @@ async function postPRComment(result) {
     const ctx = (0, github_js_1.getGitHubContext)();
     if (!ctx || ctx.eventName !== "pull_request")
         return;
-    // Parse PR number from event
     let prNumber = 0;
     if (ctx.eventPath && fs.existsSync(ctx.eventPath)) {
         const event = JSON.parse(fs.readFileSync(ctx.eventPath, "utf-8"));
@@ -55,31 +54,38 @@ async function postPRComment(result) {
     if (lh) {
         lhTable = `| Performance | Accessibility | SEO | Best Practices |\n|---|---|---|---|\n| ${lh.performance} / ${t.performance} | ${lh.accessibility} / ${t.accessibility} | ${lh.seo} / ${t.seo} | ${lh.bestPractices} / ${t.bestPractices} |\n\n`;
     }
-    const emoji = grade === "Gold" ? "🥇" :
-        grade === "Silver" ? "🥈" :
-            grade === "Bronze" ? "🥉" : "⚪";
-    const body = `## ${emoji} Laxy Verify — **${grade}**
-
-${grade === "Unverified" ? "The build failed or verification could not be completed." : `Build passed verification with a **${grade}** grade.`}
-
-${lhTable}**Fail-on threshold**: ${result.config_fail_on ?? "bronze"}
-
----
-[🔍 Laxy Verify](https://github.com/psungmin24/laxy-verify) — Frontend quality gate`;
+    const passed = result.exitCode === 0;
+    const statusLabel = passed ? "[PASS]" : "[HOLD]";
+    const headline = passed ? "No deployment blockers found" : "Deployment blockers found";
+    const summary = passed
+        ? `This PR passed the current verification gate. Grade summary: **${grade}**.`
+        : grade === "Unverified"
+            ? "The production build failed or verification could not complete, so this PR should be held."
+            : `This PR did not clear the current verification gate. Grade summary: **${grade}**.`;
+    const body = `## ${statusLabel} Laxy Verify: ${headline}
+
+${summary}
+
+${lhTable}**Fail-on threshold**: ${result.config_fail_on ?? "bronze"}
+
+Grade remains available for automation, but this check should be read first as a merge and release blocker gate.
+
+---
+[Open laxy-verify docs](https://github.com/psungmin24/laxy-verify)`;
     const [owner, repo] = ctx.repository.split("/");
     const url = `https://api.github.com/repos/${owner}/${repo}/issues/${prNumber}/comments`;
     try {
         const res = await fetch(url, {
             method: "POST",
             headers: {
-                "Authorization": `Bearer ${ctx.token}`,
-                "Accept": "application/vnd.github.v3+json",
+                Authorization: `Bearer ${ctx.token}`,
+                Accept: "application/vnd.github.v3+json",
                 "Content-Type": "application/json",
             },
             body: JSON.stringify({ body }),
         });
         if (!res.ok) {
-            console.warn(`GitHub PR comment API returned ${res.status} — skipping comment`);
+            console.warn(`GitHub PR comment API returned ${res.status}; skipping comment.`);
             return;
         }
     }

package/dist/entitlement.js

@@ -14,12 +14,12 @@ exports.printPlanBanner = printPlanBanner;
 const auth_js_1 = require("./auth.js");
 const FREE_FEATURES = {
     plan: "free",
-    gold_grade: false,
-    lighthouse_runs_3: false,
-    verbose_failure: false,
-    multi_viewport: false,
-    failure_analysis: false,
-    fast_lane: false,
+    gold_grade: true,
+    lighthouse_runs_3: true,
+    verbose_failure: true,
+    multi_viewport: true,
+    failure_analysis: true,
+    fast_lane: true,
 };
 let cache = null;
 const CACHE_TTL_MS = 5 * 60 * 1000;
@@ -68,36 +68,7 @@ async function getEntitlements() {
 function applyPlanOverride(features, overridePlan) {
     if (!overridePlan)
         return features;
-    const actualPlan = normalizePlan(features.plan);
-    if (getPlanRank(overridePlan) > getPlanRank(actualPlan)) {
-        throw new Error(`Plan override "${overridePlan}" is higher than your active entitlement "${actualPlan}". Downgrade overrides are allowed, upgrades are not.`);
-    }
-    if (overridePlan === actualPlan) {
-        return { ...features, plan: overridePlan };
-    }
-    if (overridePlan === "free") {
-        return {
-            plan: "free",
-            gold_grade: false,
-            lighthouse_runs_3: false,
-            verbose_failure: false,
-            multi_viewport: false,
-            failure_analysis: false,
-            fast_lane: false,
-        };
-    }
-    if (overridePlan === "pro") {
-        return {
-            plan: "pro",
-            gold_grade: false,
-            lighthouse_runs_3: true,
-            verbose_failure: features.verbose_failure,
-            multi_viewport: false,
-            failure_analysis: false,
-            fast_lane: false,
-        };
-    }
-    return { ...features, plan: "pro_plus" };
+    return { ...features, plan: overridePlan };
 }
 function printPlanBanner(features) {
     const planLabels = {

package/dist/status.js

@@ -7,8 +7,10 @@ async function createStatusCheck(result) {
     if (!ctx)
         return;
     const [owner, repo] = ctx.repository.split("/");
-    const description = `Laxy Verify — ${result.grade}`;
     const state = result.exitCode === 0 ? "success" : "failure";
+    const description = state === "success"
+        ? "Laxy Verify: no deployment blockers found"
+        : "Laxy Verify: deployment blockers found";
     const targetUrl = `${process.env.GITHUB_SERVER_URL ?? "https://github.com"}/${ctx.repository}/actions/runs/${process.env.GITHUB_RUN_ID ?? ""}`;
     const url = `https://api.github.com/repos/${owner}/${repo}/statuses/${ctx.sha}`;
     try {
@@ -27,7 +29,7 @@ async function createStatusCheck(result) {
             }),
         });
         if (!res.ok) {
-            console.warn(`GitHub Status Check API returned ${res.status} — skipping status`);
+            console.warn(`GitHub Status Check API returned ${res.status}; skipping status update.`);
         }
     }
     catch (err) {

package/package.json

@@ -1,17 +1,17 @@
 {
   "name": "laxy-verify",
-  "version": "1.1.21",
+  "version": "1.1.23",
   "description": "Frontend verification CLI for build checks, Lighthouse, E2E, and release readiness",
   "license": "MIT",
   "type": "commonjs",
-  "homepage": "https://github.com/psungmin24/Laxy/tree/main/laxy-verify#readme",
+  "homepage": "https://github.com/SUNgm24/Laxy/tree/main/laxy-verify#readme",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/psungmin24/Laxy.git",
+    "url": "git+https://github.com/SUNgm24/Laxy.git",
     "directory": "laxy-verify"
   },
   "bugs": {
-    "url": "https://github.com/psungmin24/Laxy/issues"
+    "url": "https://github.com/SUNgm24/Laxy/issues"
   },
   "keywords": [
     "frontend",