@event4u/agent-config 8.1.0 → 8.3.0

package/docs/mcp-server.md

@@ -1,6 +1,6 @@
 # MCP Server
 
-> Status: **experimental** — Phase 1 + 2 + 3 shipped. No `tools/*` primitive yet (Phase 4, deferred behind a design call). Promotion to **beta** is gated on the six criteria in [`docs/contracts/mcp-beta-criteria.md`](contracts/mcp-beta-criteria.md); current gate status: `./agent-config doctor --check mcp-beta-readiness` (Phase 3 of `road-to-surface-discipline.md`).
+> Status: **experimental** — read-only prompts + resources plus a growing `tools/*` surface (stub-by-default: every catalogued tool name resolves, unimplemented ones return a structured `not_implemented` envelope). Tool coverage and the write/exec unlock path are governed by [`agents/settings/contexts/mcp-coverage-strategy.md`](../agents/settings/contexts/mcp-coverage-strategy.md). Promotion to **beta** is gated on the six criteria in [`docs/contracts/mcp-beta-criteria.md`](contracts/mcp-beta-criteria.md); current gate status: `./agent-config doctor --check mcp-beta-readiness`.
 
 `agent-config` ships a built-in [Model Context Protocol](https://modelcontextprotocol.io)
 server that exposes the package's read-only governance surface to MCP-aware
@@ -20,22 +20,30 @@ coexist:
   [`docs/contracts/mcp-cloud-scope.md`](contracts/mcp-cloud-scope.md).
   Wire-parity-checked against the local stdio kernel on every release.
 
-The MCP server **never executes engine code, never writes files, never spawns
-shells**. It is a read-only instructional surface — see
-[`docs/contracts/mcp-phase-1-scope.md`](contracts/mcp-phase-1-scope.md).
+Every implemented tool is either read-only or writes only inside the
+consumer's project tree via a path-guard (`_validateInTreePath`) —
+[`docs/contracts/mcp-phase-1-scope.md`](contracts/mcp-phase-1-scope.md)
+is the scope contract; exec-tier tools (shell-spawning) and network-tier
+tools (billable) are gated behind
+[`agents/settings/contexts/mcp-coverage-strategy.md`](../agents/settings/contexts/mcp-coverage-strategy.md).
 
 ## What the server exposes
 
-| Primitive | URIs | Source | Count (this package) |
-|---|---|---|---|
-| `prompts/list` + `prompts/get` | `skill.<name>`, `command.<name>` | `dist/agent-src/skills/`, `dist/agent-src/commands/` | 174 skills + 104 commands |
-| `resources/list` + `resources/read` | `rule://<stem>` | `dist/agent-src/rules/` | 60 rules |
-| ↳ | `guideline://<relpath>` | `docs/guidelines/` | 69 guidelines |
-| ↳ | `context://<relpath>` | `dist/agent-src/contexts/` | 31 contexts |
+| Primitive | URIs | Source |
+|---|---|---|
+| `prompts/list` + `prompts/get` | `skill.<name>`, `command.<name>` | `dist/agent-src/skills/`, `dist/agent-src/commands/` |
+| `resources/list` + `resources/read` | `rule://<stem>` | `dist/agent-src/rules/` |
+| ↳ | `guideline://<relpath>` | `docs/guidelines/` |
+| ↳ | `context://<relpath>` | `dist/agent-src/contexts/` |
+| `tools/list` + `tools/call` | see [`agents/settings/contexts/mcp-tool-tier-map.md`](../agents/settings/contexts/mcp-tool-tier-map.md) for the full candidate surface | `src/scripts/mcp_server/consumer_tool_catalog.json` |
 
 All resources are served with `mimeType: text/markdown`. Pagination is
 cursor-based (default page size: 100). Hot-reload triggers automatically on
 file mtime changes — edit a rule, reissue `resources/list`, see the update.
+Exact prompt/resource/tool counts drift with every content change — the smoke
+test below reports the live numbers rather than a number pinned in prose.
+_Last verified boot (`task mcp:glama-test`, 2026-07-07): 430 prompts / 232
+resources / 27 tools (18 implemented, 9 stubs — post write/exec cut)._
 
 ## Setup — one-line install
 
@@ -60,10 +68,9 @@ task mcp:run            # maintainer / dev repo
 ./agent-config mcp:run  # consumer projects
 ```
 
-Both forms launch the TypeScript MCP server over stdio via `tsx`. Use these for
-
-(Claude Desktop, Cursor, Zed, Continue) launch the server themselves via
-the config snippets below.
+Both forms launch the TypeScript MCP server over stdio via `tsx`. Use these
+for a manual smoke test — MCP clients (Claude Desktop, Cursor, Zed, Continue)
+launch the server themselves via the config snippets below.
 
 ## Client configuration
 
@@ -140,8 +147,9 @@ boots cleanly:
 
 ```bash
 ./agent-config mcp:run < /dev/null
-# Expect stderr: "mcp-server: loaded N prompts (0 warnings)" and
-#                "mcp-server: loaded 160 resources (0 warnings)"
+# Expect stderr: "mcp-server: loaded N prompts (0 warnings)",
+#                "mcp-server: loaded N resources (0 warnings)", and
+#                "mcp-server: registered N tools (N implemented, N stubs): [...]"
 ```
 
 ## Troubleshooting
@@ -155,9 +163,13 @@ boots cleanly:
 ## Scope
 
 - **In scope:** read-only prompts + resources, pagination, hot-reload, stdio
-  transport, free-tier client compatibility.
-- **Out of scope (Phase 4+):** `tools/*` primitive, SSE / HTTP transport,
-  cloud distribution, signed payloads. Tracked in
-  [`agents/roadmaps/road-to-mcp-server.md`](../agents/roadmaps/road-to-mcp-server.md).
+  transport, free-tier client compatibility, a growing read-only and
+  in-tree-write `tools/*` surface (see
+  [`agents/settings/contexts/mcp-tool-tier-map.md`](../agents/settings/contexts/mcp-tool-tier-map.md)).
+- **Out of scope:** SSE / native HTTP transport for this server (the
+  Cloudflare Worker above is the HTTP bridge instead), shell-exec and
+  network-tier tools until the safety envelope in
+  [`agents/settings/contexts/mcp-coverage-strategy.md`](../agents/settings/contexts/mcp-coverage-strategy.md)
+  ships, signed payloads.
 
 ← [Architecture](architecture.md) · [MCP config generation (consumer side)](mcp.md)

package/docs/proof.md

@@ -27,7 +27,7 @@ evidence pointer, or `task check-claims` fails the build.
 | Claim | Kind | Evidence | Resolves |
 |---|---|---|---|
 | On a weak host (claude-haiku-4-5) the package produces a significant, placebo-controlled discipline lift on scope/downstream traps; on a strong host the same measurement is a published null — the package transplants discipline a weak model lacks, not model intelligence. | quant | `docs/benchmark.md#weak-host-specific` | ✅ |
-| The lift-carrying essential cut (kernel + downstream-changes) keeps a significant weak-host discipline lift at a fraction of the full load's tokens, and the lift is FAMILY-SCOPED — full-corpus P1 gate (n=90 pairs): scope/downstream family 0.533→1.000 (7/7 discordant favour essential), other families flat at ceiling, corpus-wide 1.71x tokens; the full load's residual over essential is not significant (p=0.37, n=24). Non-claim on the flip side — the balanced router profile (kernel + tier-1 by size) was removed after measuring a NULL lift (p=0.81, n=24, claude-haiku-4-5, 2026-07-07), and no full-tier recommendation exists anywhere until its own evidence gate passes. | quant | `docs/benchmark.md#Full-corpus P1 gate` | ✅ |
+| The lift-carrying essential cut (kernel + downstream-changes) keeps a significant weak-host discipline lift at a fraction of the full load's tokens, and the lift is FAMILY- and HOST-SCOPED — measured on three hosts: claude-haiku-4-5 (weak) shows the family-scoped lift (trapE 0.533→1.000, 7/7 discordant, corpus cost 1.71x); claude-sonnet-4-6 (strong) is a ceiling null; gpt-5-mini (non-Claude weak, codex prompt-prepend surface) FAILED replication with headroom (corpus Δ=+0.024 p=0.70, capability trend n.s. — no harm claimed, injection-surface confound documented). Therefore discipline_profile: auto enables the lift only where measured (vendor-granular unknown_defaults). Non-claims — the balanced router profile was removed after a NULL measurement (p=0.81, n=24); no full-tier recommendation exists; no cross-vendor lift is claimed. | quant | `docs/benchmark.md#REPLICATION FAILED` | ✅ |
 | The whole layer is compiled into host agents with zero runtime daemon. | qual | `docs/contracts/no-runtime-boundary.md#file-first, no-runtime suite` | ✅ |
 | Removes only its own keys from a shared host config (matched by JSON-pointer + SHA-256), never a neighbour tool's entries. | qual | `docs/contracts/install-layout.md#JSON-pointer` | ✅ |
 

package/docs/setup/mcp-cloud-endpoints.md

@@ -19,8 +19,15 @@ resources. `tools/list` returns two **deprecated stubs**
 successors; `tools/call` against either returns `isError=true`. No
 script execution, no FS access, no shell.
 
-Full power — the ~112 Python scripts (linters, audits, `task ci`,
-work-engine hooks) — requires the local install. See
+Full power — the implemented tool surface (18 tools as of the 2026-07-07
+write/exec cut: memory, roadmap, capabilities, doctor/conformance,
+telemetry, council-estimate, and the vitest `run_tests` pilot) — requires
+the **local kernel server** (`agent-config mcp:run` on a repo checkout).
+`implemented_on` stays `["stdio"]` for every execution tool, permanently:
+the Worker has no kernel runtime endpoint — it serves a release-pinned
+content snapshot from R2, so there is no process that could run the
+handlers, and the A0-cloud contract's no-execution boundary is a design
+invariant, not a backlog item. See
 [`../contracts/mcp-cloud-scope.md`](../contracts/mcp-cloud-scope.md)
 for the execution-safety boundary and the Phase-7-DEFERRED gate that
 governs any future tool restoration.

package/docs/setup/per-ide/claude-code.md

@@ -32,14 +32,20 @@ Either form populates:
 ## Plugin marketplace (Claude Code 2026+)
 
 Claude Code 2026 supports plugin marketplaces via
-`.claude-plugin/marketplace.json`. The package ships one — once
-listed at the Anthropic marketplace (Phase 7 / S34) you can also:
+`.claude-plugin/marketplace.json`. The package ships one, so as an
+**additional, optional** surface you can also install the plugin:
 
 ```bash
-claude plugin install event4u/agent-config
+claude plugin marketplace add event4u-app/agent-config
+claude plugin install agent-config@event4u-agent-config
 ```
 
-Today the npm/curl entrypoints above are the supported install path.
+The npm/curl entrypoints above are a full install on their own — the
+file projection carries the complete skill/command set; the plugin adds
+the namespaced `agent-config:*` surface on top. When the plugin is
+installed, `agent-config upgrade` refreshes it automatically (Claude
+Code otherwise pins it to the install-time git SHA); `agent-config
+doctor --check claude-plugin` reports a stale snapshot.
 
 ## CLAUDE.md
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@event4u/agent-config",
-    "version": "8.1.0",
+    "version": "8.3.0",
     "description": "Universal AI Agent OS — audited skills, governance rules, commands, and templates for AI coding tools (Claude Code, Cursor, Windsurf, Copilot).",
     "license": "MIT",
     "private": false,
@@ -39,6 +39,7 @@
         "docs/",
         "src/scripts/",
         "src/templates/",
+        "tests/fixtures/hooks/",
         "AGENTS.md",
         "CHANGELOG.md",
         "CONTRIBUTING.md",
@@ -55,7 +56,7 @@
     },
     "scripts": {
         "build:cli": "tsc -p tsconfig.json && chmod +x dist/cli/agent-config.js",
-        "build:install-bundle": "esbuild src/scripts/install.ts --bundle --platform=node --format=esm --target=node20 --define:__AGENT_CONFIG_BUNDLE__=true --outfile=dist/install/install.mjs",
+        "build:install-bundle": "esbuild src/scripts/install.ts --bundle --platform=node --format=esm --target=node20 --define:__AGENT_CONFIG_BUNDLE__=true --outfile=dist/install/install.mjs --banner:js=\"import { createRequire as __acCreateRequire } from 'node:module'; const require = globalThis.require ?? __acCreateRequire(import.meta.url);\"",
         "build:ui": "vite build",
         "build:discovery": "./scripts-run src/scripts/build_discovery_manifest --write --strict",
         "build:mcp-manifest": "./scripts-run src/scripts/build_mcp_registry_manifest --write --strict",
@@ -82,7 +83,6 @@
         "eslint": "^9.39.4",
         "happy-dom": "^20.9.0",
         "js-tiktoken": "^1.0.21",
-        "tsx": "^4.22.3",
         "typescript": "^5.9.3",
         "vite": "^5.4.21",
         "vitest": "^2.1.9"
@@ -97,6 +97,7 @@
         "js-yaml": "^4.1.0",
         "open": "^10.2.0",
         "preact": "^10.29.0",
+        "tsx": "^4.22.3",
         "yaml": "^2.9.0",
         "zod": "^3.25.0",
         "zod-to-json-schema": "^3.25.0"

package/src/config/agent-settings.template.yml

@@ -85,17 +85,19 @@ projection:
 #             package's residual over it is not significant (p=0.37).
 # full      = every rule tier (~11.7x tokens). EXPERIMENTAL opt-in only:
 #             residual lift over essential not established.
-# auto      = resolve per session against host-capabilities.yml — model on
-#             the measured NULL-lift list -> off, otherwise -> essential.
+# auto      = resolve per session against host-capabilities.yml — measured
+#             NULL-lift model -> off; unmeasured Claude-family -> essential;
+#             unmeasured non-Claude -> off (P2 verdict, vendor-granular).
 #
 # This key WINS over the legacy `rule_loading_tier` below (mapping when
 # absent: minimal->off, balanced->essential, full->full, custom->custom).
-# The installer fills the placeholder per preset with the value that
-# preserves each preset's prior behaviour (minimal->off,
-# balanced->essential, full->full) — same resolution as the legacy
-# mapping, no behaviour change. The flip of the shipped default to
-# `auto` is evidence-gated (P2 non-Claude replication, see
-# agents/roadmaps/road-to-discipline-profile-tiering.md).
+# The installer fills the placeholder per preset: minimal->off,
+# balanced->auto, full->full. `auto` is evidence-gated per the P2 verdict
+# (council 2026-07-07): the P2 non-Claude replication FAILED (gpt-5-mini,
+# n=90, docs/benchmark.md), so `auto` enables the lift only where measured
+# — unmeasured Claude-family hosts -> essential (the measured-lift class);
+# measured-null hosts and unmeasured non-Claude hosts -> off
+# (vendor-granular unknown_defaults in src/config/host-capabilities.yml).
 discipline_profile: __DISCIPLINE_PROFILE__
 
 # --- Cost profile (legacy knob — superseded by discipline_profile above) ---
@@ -392,8 +394,9 @@ roadmap:
   #   per_step       = after every completed step (legacy verbose; highest token cost)
   # Trade-off: end_of_roadmap saves tokens and time but lets errors compound
   # across phases. Pick per_phase if the work is risky or unfamiliar.
-  # Iron Law `verify-before-complete` still applies — fresh quality output
-  # is mandatory before any "roadmap complete" claim regardless of cadence.
+  # `quality.local_auto_run: false` (the default) suppresses local
+  # pipeline runs at EVERY cadence — remote CI is the gate; this knob
+  # only matters when `local_auto_run` is `true`.
   quality_cadence: end_of_roadmap
 
   # Dashboard regen cadence inside autonomous runs (process-step /
@@ -444,20 +447,31 @@ roadmap:
 # (`task ci`, `make test`, `npm run check`, PHPStan, ECS, Rector,
 # test suites) and whether it waits on remote CI after pushing.
 # Iron Law `verify-before-complete` still applies — when these
-# toggles suppress automatic runs, the agent MUST surface that and
-# ask before claiming completion rather than silently skipping
-# verification.
+# toggles suppress automatic runs, the agent MUST surface the gap
+# in the completion message ("quality gates delegated to remote CI")
+# instead of claiming the tools passed. It never silently claims
+# verification it did not run.
 quality:
   # Run local quality / CI tasks and tests autonomously (true, false)
-  # true  = agent runs the quality pipeline whenever work is ready
-  #         for verification, without asking (default)
-  # false = agent asks before running quality tools / tests locally
+  # false = default. The agent NEVER runs quality tools or full test
+  #         suites proactively — and does not ask whether to run them.
+  #         Toolchains differ per language/project and are often
+  #         unknown to the agent; discovery + execution costs time and
+  #         tokens. The user runs quality tools manually; remote CI is
+  #         the authoritative gate. The agent runs a quality tool ONLY
+  #         when one of three triggers fires:
+  #           1. the user explicitly asks this turn (e.g. /quality-fix),
+  #           2. CI / the remote pipeline reports a concrete failure —
+  #              then run exactly that failing check to reproduce + fix,
+  #           3. the new-gate carve-out below.
+  # true  = opt-in legacy behaviour: agent runs the quality pipeline
+  #         whenever work is ready for verification, without asking.
   #
   # Carve-out (always runs regardless of this flag): when the change
   # introduces a NEW CI gate, smoke test, or test file, the agent
   # MUST execute it locally to prove the gate works. Without that
   # execution the new gate is unverified evidence.
-  local_auto_run: true
+  local_auto_run: false
 
   # Wait for remote CI to finish on the PR / pipeline (true, false)
   # true  = after push, poll GitHub check-runs / pipeline status and

package/src/config/host-capabilities.yml

@@ -1,31 +1,40 @@
 # Host-capability facts for `discipline_profile: auto` resolution.
 #
 # EVIDENCE-GATED NULL-LIFT DISABLE-LIST — not a model taxonomy.
-# Council lock (claude-sonnet-4-5 + gpt-4o, 2026-07-07, recorded in
+# Council locks (claude-sonnet-4-5 + gpt-4o, 2026-07-07, recorded in
 # agents/settings/contexts/weak-host-lift-tiering-verdict.md): entries here
-# name ONLY host models with a MEASURED null discipline lift (the package's
-# discipline tier is redundant on them — they sit at the discipline ceiling).
-# Speculative strong/weak classifications of unmeasured models (per vendor,
-# per family, per glob) are FORBIDDEN: they rot at model-release cadence and
-# encode certainty no measurement backs.
+# name ONLY host models with a MEASURED null discipline lift. Speculative
+# strong/weak classifications of unmeasured models are FORBIDDEN: they rot
+# at model-release cadence and encode certainty no measurement backs.
 #
 # Entry contract — every entry carries either:
 #   - measured: <report date · pinned report · N pairs>   (CLAIMS-grade), or
 #   - extrapolated: true + rationale                       (explicit maintainer
-#     judgement, labeled as such — e.g. a strictly-stronger sibling of a
-#     measured-null model). Never an unlabeled assumption.
+#     judgement, labeled as such). Never an unlabeled assumption.
 #
 # Matching: exact model-id prefix match against the session's model id
 # (vendor-neutral — Claude, GPT, Gemini, open-source ids all welcome once
-# measured). Unknown / unmatched models resolve per `unknown_default`.
-#
-# Fail-safe direction: `unknown_default: lift_enabled` means a new or
-# unmeasured model gets the `essential` discipline tier — it costs ~3x tokens
-# on a host that turns out strong, but never silently drops the measured
-# lift on a weak one. The list only ever GROWS by measurement.
+# measured).
 
 lift_disabled_models:
   - id: claude-sonnet-4-6
-    measured: "2026-07-05 · internal/bench/reports/ab-v2/2026-07-05T07-00-31Z-ab-v2-paired.json · n=84 pairs, full 30-task corpus, discipline Δ=+0.000 (p=1.0)"
+    measured: "2026-07-05 · internal/bench/reports/ab-v2/2026-07-05T07-00-31Z-ab-v2-paired.json · n=84 pairs, full 30-task corpus, discipline Δ=+0.000 (p=1.0) — ceiling null"
+  - id: gpt-5-mini
+    measured: "2026-07-07 · internal/bench/reports/ab-v2/2026-07-07T10-33-53Z-ab-v2-paired.json · n=90 pairs, full 30-task corpus via codex prompt-prepend injection — replication FAILED with headroom (corpus Δ=+0.024 p=0.70; trapE family 0.733→0.667). NOT a validated harm claim (capability trend 89%→82% is n.s., p=0.07). Injection-surface confound documented in docs/benchmark.md."
 
-unknown_default: lift_enabled
+# Resolution for UNMEASURED models, per vendor family — the P2-verdict
+# council (2026-07-07, 2-round debate) replaced the earlier blanket
+# `lift_enabled` fail-safe: the evidence ledger is now 1 measured lift
+# (Claude weak class) vs 2 measured nulls (Claude strong ceiling; GPT weak
+# failed replication), so unknown non-Claude hosts default OFF (the lift
+# costs 1.2-1.7x and has no measured benefit off-Claude as shipped), while
+# unknown Claude-family hosts keep the fail-safe toward the one measured
+# lift. This is evidence-structure granularity (WHERE measurements exist),
+# not a strength taxonomy; it grows/changes only by measurement.
+#
+# Family detection: model-id prefix. `claude-` -> anthropic; everything
+# else resolves via `default`. Legacy single-value `unknown_default` keys
+# are still read by the resolver (mapped onto `default`).
+unknown_defaults:
+  anthropic: lift_enabled
+  default: lift_disabled

package/src/config/profiles/balanced.ini

@@ -9,9 +9,11 @@
 
 rule_loading_tier=balanced
 
-; Successor knob (ADR-110) — value preserves this preset's prior behaviour
-; via the legacy mapping (minimal->off, balanced->essential, full->full).
-discipline_profile=essential
+; Successor knob (ADR-110). P2-verdict council 2026-07-07: balanced-heritage
+; installs get `auto` — the lift enables only where measured (unmeasured
+; Claude-family hosts -> essential; measured-null and unmeasured non-Claude
+; hosts -> off, per src/config/host-capabilities.yml).
+discipline_profile=auto
 
 ; Chat history (crash recovery) — balanced = phase-level traceability
 chat_history_frequency=per_phase

package/src/scripts/_cli/cmd_analyze_session.ts

@@ -326,10 +326,29 @@ export function main(argv: string[] | null = null): number {
 
 // --- CLI entry ---
 
-const _isCliEntry =
-    process.argv[1] !== undefined &&
-    import.meta.url === pathToFileURL(path.resolve(process.argv[1])).href;
-if (_isCliEntry || process.argv[1] === _HERE) {
+function _isCliEntry(): boolean {
+    if (process.argv[1] === undefined) {
+        return false;
+    }
+    const argvUrl = pathToFileURL(path.resolve(process.argv[1])).href;
+    if (import.meta.url === argvUrl) {
+        return true;
+    }
+    // A symlinked invocation (e.g. via an installed `.augment/` projection,
+    // or macOS /var → /private/var temp dirs) makes the raw URLs differ:
+    // import.meta.url is the resolved real path while argv[1] keeps the
+    // symlink path. Compare realpaths so the entry guard still fires
+    // (without this the CLI silently no-ops when run through a symlink).
+    try {
+        const here = fs.realpathSync(fileURLToPath(import.meta.url));
+        const argv = fs.realpathSync(path.resolve(process.argv[1]));
+        return here === argv;
+    } catch {
+        return false;
+    }
+}
+
+if (_isCliEntry() || process.argv[1] === _HERE) {
     try {
         process.exitCode = main(process.argv.slice(2));
     } catch (e) {

package/src/scripts/_cli/cmd_conformance.ts

@@ -697,10 +697,29 @@ function main(argv: string[] | null = null): number {
 
 // --- CLI entry ---
 
-const _isCliEntry =
-    process.argv[1] !== undefined &&
-    import.meta.url === pathToFileURL(path.resolve(process.argv[1])).href;
-if (_isCliEntry || process.argv[1] === _HERE) {
+function _isCliEntry(): boolean {
+    if (process.argv[1] === undefined) {
+        return false;
+    }
+    const argvUrl = pathToFileURL(path.resolve(process.argv[1])).href;
+    if (import.meta.url === argvUrl) {
+        return true;
+    }
+    // A symlinked invocation (e.g. via an installed `.augment/` projection,
+    // or macOS /var → /private/var temp dirs) makes the raw URLs differ:
+    // import.meta.url is the resolved real path while argv[1] keeps the
+    // symlink path. Compare realpaths so the entry guard still fires
+    // (without this the CLI silently no-ops when run through a symlink).
+    try {
+        const here = fs.realpathSync(fileURLToPath(import.meta.url));
+        const argv = fs.realpathSync(path.resolve(process.argv[1]));
+        return here === argv;
+    } catch {
+        return false;
+    }
+}
+
+if (_isCliEntry() || process.argv[1] === _HERE) {
     try {
         process.exitCode = main(process.argv.slice(2));
     } catch (e) {