blogwright 0.3.3 → 0.4.0-beta.0

package/dist/render.d.ts

@@ -20,6 +20,26 @@ export interface StatusEntry {
 }
 /** The pretty drift tree for `status` (the plain form keeps the classic lines). */
 export declare function renderStatusTree(entries: StatusEntry[]): string[];
+/**
+ * Leveled-logger surface {@link logStatusEntries} reports through - both the
+ * CLI's own `Logger` (`packages/cli/src/logger.ts`) and core's
+ * `PluginLogger` (`blogwright-core`'s `plugin.ts`) satisfy it structurally,
+ * so this module needs neither type imported.
+ */
+export interface StatusLogger {
+    info(msg: string): void;
+    warn(msg: string): void;
+}
+/**
+ * Report `entries` through `logger`, choosing the pretty tree ({@link
+ * renderStatusTree}) on an interactive terminal or the plain, CI-stable form
+ * otherwise: a `present`/`missing` line via `logger.info`, or a `read
+ * failed` line via `logger.warn` for an entry whose `read()` threw. Shared
+ * by the CLI's own `status` command (`commands.ts`) and a plugin's generic
+ * `status` verb (`plugin-commands.ts`), so the two never carry two
+ * near-identical copies of the same render branch.
+ */
+export declare function logStatusEntries(entries: StatusEntry[], pretty: boolean, logger: StatusLogger): void;
 export interface HistoryEntry {
     hash: string;
     status: 'succeeded' | 'failed';
@@ -31,3 +51,38 @@ export interface HistoryEntry {
  * the newest success. Entries arrive newest-first (the caller sorts).
  */
 export declare function renderHistoryTable(entries: HistoryEntry[], now: number): string[];
+/** One installed plugin's row in `blogwright plugin list`. */
+export interface PluginListRow {
+    /** The CLI namespace the plugin claims - `Plugin.name`. */
+    namespace: string;
+    /** The npm package the plugin was loaded from. */
+    packageName: string;
+    /** From the package's own `package.json`; `undefined` when it declares none. */
+    version?: string | undefined;
+    /** The single top-level config key the plugin owns; `undefined` when it owns none. */
+    configKey?: string | undefined;
+}
+/** One plugin that failed to load, as `discover` reported it. */
+interface PluginListFailure {
+    packageName: string;
+    reason: string;
+}
+/** What `blogwright plugin list` has to show: the plugins that loaded, and the ones that did not. */
+export interface PluginListing {
+    rows: readonly PluginListRow[];
+    failures: readonly PluginListFailure[];
+}
+/**
+ * The `blogwright plugin list` listing, in the two forms every renderer in
+ * this module offers: an aligned table under a bold header on a TTY, and the
+ * same columns single-space separated otherwise. The plain form is the stable
+ * contract for CI logs and agents - the same split `history` makes
+ * (`commands.ts`), which is why the column set is identical in both and only
+ * the padding and the colour differ.
+ *
+ * Emits NOTHING for a listing with no rows and no failures, so a repo with no
+ * plugins installed gets its caller's empty-state line and not a header over
+ * an empty table.
+ */
+export declare function renderPluginList(listing: PluginListing, pretty: boolean): string[];
+export {};

package/dist/render.js

@@ -1,5 +1,5 @@
 /*
- * Pure presentation helpers: data in, lines out — the caller writes them.
+ * Pure presentation helpers: data in, lines out - the caller writes them.
  * Every renderer takes a `pretty` flag; the plain form is stable, line-oriented
  * output for CI systems and agents, the pretty form is for humans on a TTY.
  */
@@ -60,6 +60,31 @@ export function renderStatusTree(entries) {
         return `${connector} ${STATUS_MARKS[entry.state]} ${entry.title}${detail}`;
     });
 }
+/**
+ * Report `entries` through `logger`, choosing the pretty tree ({@link
+ * renderStatusTree}) on an interactive terminal or the plain, CI-stable form
+ * otherwise: a `present`/`missing` line via `logger.info`, or a `read
+ * failed` line via `logger.warn` for an entry whose `read()` threw. Shared
+ * by the CLI's own `status` command (`commands.ts`) and a plugin's generic
+ * `status` verb (`plugin-commands.ts`), so the two never carry two
+ * near-identical copies of the same render branch.
+ */
+export function logStatusEntries(entries, pretty, logger) {
+    if (pretty) {
+        for (const line of renderStatusTree(entries))
+            logger.info(line);
+        return;
+    }
+    // The plain form is the stable contract for CI logs and agents.
+    for (const entry of entries) {
+        if (entry.state === 'error') {
+            logger.warn(`${entry.title}: read failed (${entry.detail})`);
+            continue;
+        }
+        const mark = entry.state === 'present' ? colors.green('present') : colors.yellow('missing');
+        logger.info(`  ${mark}  ${entry.title} ${entry.detail ? colors.dim(entry.detail) : ''}`);
+    }
+}
 /**
  * The pretty deployment table for `history`: relative times, a live marker on
  * the newest success. Entries arrive newest-first (the caller sorts).
@@ -78,3 +103,66 @@ export function renderHistoryTable(entries, now) {
     });
     return [colors.bold(`${'hash'.padEnd(13)} ${' '} ${'finished'.padEnd(9)} duration`), ...rows];
 }
+/**
+ * Printed in place of a cell the plugin genuinely has no value for. An
+ * explicit marker, never an empty cell: plain output is column-per-line and
+ * whitespace-separated, so a blank cell would silently shift every column
+ * after it for whatever is parsing the line.
+ */
+const NO_CONFIG_KEY = '(none)';
+/** Printed for a plugin whose own `package.json` declares no `version` field at all. */
+const UNKNOWN_VERSION = '(unknown)';
+/** Column headers, in the order {@link pluginListCells} emits the cells. */
+const PLUGIN_LIST_HEADERS = ['namespace', 'package', 'version', 'configKey'];
+/** Heading the failure lines are printed under, in both forms. */
+const FAILED_TO_LOAD_HEADING = 'failed to load:';
+function pluginListCells(row) {
+    return [
+        row.namespace,
+        row.packageName,
+        row.version ?? UNKNOWN_VERSION,
+        row.configKey ?? NO_CONFIG_KEY,
+    ];
+}
+/** Pad every cell but the last to the widest value in its column. */
+function alignCells(cells, widths) {
+    return cells
+        .map((cell, i) => (i === cells.length - 1 ? cell : cell.padEnd(widths[i] ?? 0)))
+        .join('  ')
+        .trimEnd();
+}
+/**
+ * The `blogwright plugin list` listing, in the two forms every renderer in
+ * this module offers: an aligned table under a bold header on a TTY, and the
+ * same columns single-space separated otherwise. The plain form is the stable
+ * contract for CI logs and agents - the same split `history` makes
+ * (`commands.ts`), which is why the column set is identical in both and only
+ * the padding and the colour differ.
+ *
+ * Emits NOTHING for a listing with no rows and no failures, so a repo with no
+ * plugins installed gets its caller's empty-state line and not a header over
+ * an empty table.
+ */
+export function renderPluginList(listing, pretty) {
+    const lines = [];
+    if (listing.rows.length > 0) {
+        const cells = listing.rows.map(pluginListCells);
+        if (pretty) {
+            const widths = PLUGIN_LIST_HEADERS.map((header, i) => Math.max(header.length, ...cells.map((row) => (row[i] ?? '').length)));
+            lines.push(colors.bold(alignCells(PLUGIN_LIST_HEADERS, widths)));
+            lines.push(...cells.map((row) => alignCells(row, widths)));
+        }
+        else {
+            lines.push(PLUGIN_LIST_HEADERS.join(' '));
+            lines.push(...cells.map((row) => row.join(' ')));
+        }
+    }
+    if (listing.failures.length > 0) {
+        lines.push(pretty ? colors.bold(FAILED_TO_LOAD_HEADING) : FAILED_TO_LOAD_HEADING);
+        // The same `<package>: <reason>` shape `--help` already prints a failed
+        // plugin in (`cli.ts`'s `renderPluginFailure`), and for the same reason:
+        // the reason is `discover`'s own message, never an `Error.stack`.
+        lines.push(...listing.failures.map((failure) => `${failure.packageName}: ${failure.reason}`));
+    }
+    return lines;
+}

package/dist/repo.d.ts

@@ -1,6 +1,6 @@
 /**
  * Deploy source packaging: choose the repository files to ship and build a
- * deterministic zip of them. Pure domain — the VCS listing and file contents
+ * deterministic zip of them. Pure domain - the VCS listing and file contents
  * arrive through ports (see ports.ts; the process adapter owns jj/git).
  */
 import { type FileSystem } from 'blogwright-core';
@@ -8,7 +8,7 @@ import type { Ports } from './ports.js';
 /**
  * Filename injected into the source zip carrying the build revision. The site build
  * runs in a MicroVM from this zip (no `.git`), so `astro.config` reads the hash from
- * this file — see the repo's astro.config.mjs.
+ * this file - see the repo's astro.config.mjs.
  */
 export declare const COMMIT_FILE = ".commit-hash";
 /**
@@ -19,7 +19,7 @@ export declare const COMMIT_FILE = ".commit-hash";
 export declare function listRepoFiles(ports: Pick<Ports, 'vcs' | 'fs'>, cwd: string, ignore: string[], include?: string[]): Promise<string[]>;
 /**
  * Build a deterministic zip of the given files (read relative to cwd). Extra entries
- * (path → text content) are added in memory — used to inject build metadata such as
+ * (path → text content) are added in memory - used to inject build metadata such as
  * the commit hash without touching the working tree.
  */
 export declare function buildRepoZip(fs: FileSystem, cwd: string, files: string[], extra?: Record<string, string>): Promise<Uint8Array>;

package/dist/repo.js

@@ -1,16 +1,16 @@
 /**
  * Deploy source packaging: choose the repository files to ship and build a
- * deterministic zip of them. Pure domain — the VCS listing and file contents
+ * deterministic zip of them. Pure domain - the VCS listing and file contents
  * arrive through ports (see ports.ts; the process adapter owns jj/git).
  */
 import { zipSync } from 'fflate';
-import { FileNotFoundError } from 'blogwright-core';
-/** Fixed timestamp for reproducible zips (fflate requires 1980-2099). */
-const ZIP_MTIME = new Date('1980-01-01T00:00:00Z');
+import { FileNotFoundError, REPRODUCIBLE_ZIP_MTIME } from 'blogwright-core';
+/** Fixed timestamp for reproducible zips. See {@link REPRODUCIBLE_ZIP_MTIME} for why it is not UTC-constructed. */
+const ZIP_MTIME = REPRODUCIBLE_ZIP_MTIME;
 /**
  * Filename injected into the source zip carrying the build revision. The site build
  * runs in a MicroVM from this zip (no `.git`), so `astro.config` reads the hash from
- * this file — see the repo's astro.config.mjs.
+ * this file - see the repo's astro.config.mjs.
  */
 export const COMMIT_FILE = '.commit-hash';
 /**
@@ -20,7 +20,7 @@ export const COMMIT_FILE = '.commit-hash';
  */
 export async function listRepoFiles(ports, cwd, ignore, include = []) {
     const files = await ports.vcs.listFiles(cwd);
-    // An ignore entry matches an exact path or a directory boundary — "dist"
+    // An ignore entry matches an exact path or a directory boundary - "dist"
     // drops dist and dist/**, never dist-notes.md (files silently missing from
     // the deployed site are painful to trace back to a prefix collision).
     const matches = (f, entry) => {
@@ -54,12 +54,12 @@ async function includedFiles(fs, cwd, entry) {
     catch (err) {
         if (err instanceof FileNotFoundError && (await fs.exists(abs)))
             return [rel]; // a single file
-        throw new Error(`sourceInclude path "${entry}" is missing or empty — run the pre-deploy build that produces it before deploying`, { cause: err });
+        throw new Error(`sourceInclude path "${entry}" is missing or empty - run the pre-deploy build that produces it before deploying`, { cause: err });
     }
 }
 /**
  * Build a deterministic zip of the given files (read relative to cwd). Extra entries
- * (path → text content) are added in memory — used to inject build metadata such as
+ * (path → text content) are added in memory - used to inject build metadata such as
  * the commit hash without touching the working tree.
  */
 export async function buildRepoZip(fs, cwd, files, extra = {}) {

package/dist/seo.d.ts

@@ -10,6 +10,6 @@ export interface SeoDirectives {
  * Resolve robots.txt / sitemap.xml directives for a deploy from the environment + config.
  * `baseUrl` is the canonical origin the site is served from (e.g. https://example.com).
  * Defaults are environment-aware: production is indexable with a sitemap; every other
- * environment blocks crawlers and skips the sitemap — all overridable via config.seo.
+ * environment blocks crawlers and skips the sitemap - all overridable via config.seo.
  */
 export declare function resolveSeo(ctx: OpsContext, baseUrl: string | undefined): SeoDirectives;

package/dist/seo.js

@@ -11,7 +11,7 @@ function indexRobots(sitemapUrl) {
  * Resolve robots.txt / sitemap.xml directives for a deploy from the environment + config.
  * `baseUrl` is the canonical origin the site is served from (e.g. https://example.com).
  * Defaults are environment-aware: production is indexable with a sitemap; every other
- * environment blocks crawlers and skips the sitemap — all overridable via config.seo.
+ * environment blocks crawlers and skips the sitemap - all overridable via config.seo.
  */
 export function resolveSeo(ctx, baseUrl) {
     const isProd = !ctx.preview && ctx.env === 'production';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "blogwright",
-  "version": "0.3.3",
+  "version": "0.4.0-beta.0",
   "type": "module",
   "bin": {
     "blogwright": "./dist/bin.js",
@@ -17,16 +17,16 @@
     }
   },
   "dependencies": {
-    "fflate": "^0.8.3",
-    "blogwright-core": "0.3.3",
-    "blogwright-pds": "0.3.3"
+    "blogwright-core": "0.4.0-beta.0",
+    "blogwright-pds": "0.4.0-beta.0",
+    "fflate": "^0.8.3"
   },
   "devDependencies": {
+    "blogwright-build-agent": "0.1.0",
     "@types/node": "^26.1.0",
     "oxlint": "^1.72.0",
     "typescript": "^6.0.3",
-    "vitest": "^4.1.9",
-    "blogwright-build-agent": "0.1.0"
+    "vitest": "^4.1.9"
   },
   "description": "Full operations for a blog site on AWS: S3 + CloudFront hosting with builds in a Lambda MicroVM, PR previews, GitHub-OIDC CI deploys, and standard.site (AT Protocol) publishing",
   "keywords": [