@theholocron/holocron-plugin-fern 5.0.0-alpha.180 → 5.0.0-alpha.182

package/dist/index.d.mts

@@ -1,7 +1,10 @@
 import { AuthError, DnsRecordRequest, ResolveTokenInput, Wiki, WikiProvisionOpts, WikiProxyConfig } from "@theholocron/cli";
+//#region src/auth.d.ts
+declare const resolveToken: (input?: ResolveTokenInput) => string;
+//#endregion
 //#region src/capabilities/wiki.d.ts
 declare const FERN_VERSION = "5.114.1";
-interface FernWikiOptions {
+interface FernWikiOptions extends ResolveTokenInput {
   /** Absolute path to the working repo root. Injected by the loader from RuntimeContext. */
   repoRoot?: string;
   /** Active org name (e.g. "theholocron"). Injected by the loader from RuntimeContext. */
@@ -52,12 +55,32 @@ declare class FernWiki implements Wiki {
   constructor(opts: FernWikiOptions);
   provision(callOpts?: WikiProvisionOpts): Promise<string>;
   proxyConfig(): WikiProxyConfig | null;
+  /**
+   * Confirms `HOLOCRON_FERN_TOKEN`/`FERN_TOKEN` resolves, or a Fern token
+   * is stored in the keyring — not a live check. Fern exposes no
+   * lightweight endpoint to verify a token actually works (the only
+   * token-consuming operation is a full `fern generate`, see
+   * holocron#1079); this only confirms one is configured, the same way
+   * CI's `fern generate --docs` step would find it.
+   *
+   * Deliberately ignores `cliToken` (`--token`): CI's step only ever sees
+   * the env var from a GitHub Actions secret, never a CLI flag — and a
+   * bare `--token <value>` meant for some OTHER provider is forwarded to
+   * every loaded plugin as a fallback (see AGENTS.md), so honoring it
+   * here would report "configured" even when no Fern-specific credential
+   * exists anywhere CI would actually look.
+   *
+   * Only `AuthError` (the specific "no token found" signal) is treated as
+   * `ok: false` — any other error (e.g. a real keyring failure) is a
+   * genuine problem and must surface as a failure, not get misreported as
+   * a missing token.
+   */
+  whoami(): Promise<{
+    ok: boolean;
+  }>;
   dnsRecord(): DnsRecordRequest | null;
 }
 //#endregion
-//#region src/auth.d.ts
-declare const resolveToken: (input?: ResolveTokenInput) => string;
-//#endregion
 //#region src/index.d.ts
 type FernPluginOptions = FernWikiOptions;
 declare function wiki(opts: FernPluginOptions): Wiki;

package/dist/index.mjs

@@ -2,6 +2,14 @@ import { mkdir, readFile, writeFile } from "node:fs/promises";
 import { join } from "node:path";
 import { stringifyJson } from "@theholocron/json-utils";
 import { AuthError, createResolveToken } from "@theholocron/cli";
+//#region src/auth.ts
+const resolveToken = createResolveToken({
+	envName: "HOLOCRON_FERN_TOKEN",
+	vendorEnvName: "FERN_TOKEN",
+	keyringService: "fern",
+	errorMessage: "no Fern token found. Set HOLOCRON_FERN_TOKEN / FERN_TOKEN, or run: holocron auth set fern <token>"
+});
+//#endregion
 //#region src/capabilities/wiki.ts
 const FERN_VERSION = "5.114.1";
 var FernWiki = class {
@@ -34,6 +42,38 @@ var FernWiki = class {
 			headers: { "X-Fern-Host": this.opts.domain.split("/")[0] }
 		};
 	}
+	/**
+	* Confirms `HOLOCRON_FERN_TOKEN`/`FERN_TOKEN` resolves, or a Fern token
+	* is stored in the keyring — not a live check. Fern exposes no
+	* lightweight endpoint to verify a token actually works (the only
+	* token-consuming operation is a full `fern generate`, see
+	* holocron#1079); this only confirms one is configured, the same way
+	* CI's `fern generate --docs` step would find it.
+	*
+	* Deliberately ignores `cliToken` (`--token`): CI's step only ever sees
+	* the env var from a GitHub Actions secret, never a CLI flag — and a
+	* bare `--token <value>` meant for some OTHER provider is forwarded to
+	* every loaded plugin as a fallback (see AGENTS.md), so honoring it
+	* here would report "configured" even when no Fern-specific credential
+	* exists anywhere CI would actually look.
+	*
+	* Only `AuthError` (the specific "no token found" signal) is treated as
+	* `ok: false` — any other error (e.g. a real keyring failure) is a
+	* genuine problem and must surface as a failure, not get misreported as
+	* a missing token.
+	*/
+	async whoami() {
+		try {
+			resolveToken({
+				...this.opts,
+				cliToken: void 0
+			});
+			return { ok: true };
+		} catch (err) {
+			if (err instanceof AuthError) return { ok: false };
+			throw err;
+		}
+	}
 	dnsRecord() {
 		const { org, domain, fernOrg } = this.opts;
 		if (!domain) return null;
@@ -132,14 +172,6 @@ function updateInstancesBlock(content, instanceUrl, customDomain, multiSource, r
 	return content.replace(blockRe, newBlock);
 }
 //#endregion
-//#region src/auth.ts
-const resolveToken = createResolveToken({
-	envName: "HOLOCRON_FERN_TOKEN",
-	vendorEnvName: "FERN_TOKEN",
-	keyringService: "fern",
-	errorMessage: "no Fern token found. Set HOLOCRON_FERN_TOKEN / FERN_TOKEN, or run: holocron auth set fern <token>"
-});
-//#endregion
 //#region src/index.ts
 function wiki(opts) {
 	return new FernWiki(opts);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theholocron/holocron-plugin-fern",
-  "version": "5.0.0-alpha.180",
+  "version": "5.0.0-alpha.182",
   "description": "Holocron plugin for Fern. Implements the wiki capability for engineering knowledge publishing.",
   "keywords": [
     "fern",
@@ -47,10 +47,10 @@
     "tsx": "4.23.15",
     "typescript": "^5.9.3",
     "vitest": "^4.1.11",
-    "@theholocron/cli": "5.0.0-alpha.180"
+    "@theholocron/cli": "5.0.0-alpha.182"
   },
   "peerDependencies": {
-    "@theholocron/cli": "5.0.0-alpha.180"
+    "@theholocron/cli": "5.0.0-alpha.182"
   },
   "engines": {
     "node": ">=22"