@geraldmaron/construct 1.1.0 → 1.2.0

package/bin/construct-postinstall.mjs

@@ -24,7 +24,9 @@ import path from 'node:path';
 import { fileURLToPath } from 'node:url';
 
 import { stageProjectAdapters } from '../lib/install/stage-project.mjs';
-import { missingIgnorePatterns } from '../lib/host-disposition.mjs';
+import { syncProjectAdapters } from '../lib/adapters-sync.mjs';
+import { missingIgnorePatterns, isConstructPackageRepo } from '../lib/host-disposition.mjs';
+import { sanitizeNpmSpawnEnv } from '../lib/npm-spawn-env.mjs';
 
 const HERE = path.dirname(fileURLToPath(import.meta.url));
 const PKG_ROOT = path.resolve(HERE, '..');
@@ -59,7 +61,7 @@ const initCwd = process.env.INIT_CWD || process.cwd();
 try {
   const pkgRealRoot = statSync(PKG_ROOT).isDirectory() ? PKG_ROOT : null;
   if (pkgRealRoot && pkgRealRoot.startsWith(initCwd) && initCwd === PKG_ROOT) {
-    log('install is inside the Construct repo itself; skipping sync');
+    log('Construct tool repo — syncing project adapters for dogfooding');
     if (existsSync(path.join(PKG_ROOT, '.gitmessage')) && existsSync(path.join(PKG_ROOT, '.git'))) {
       const cfg = spawnSync('git', ['config', 'commit.template', '.gitmessage'], {
         cwd: PKG_ROOT,
@@ -67,6 +69,32 @@ try {
       });
       if (cfg.status === 0) log('configured git commit.template -> .gitmessage');
     }
+    try {
+      syncProjectAdapters({ projectRoot: PKG_ROOT, packageRoot: PKG_ROOT, log });
+    } catch (err) {
+      fail(`Tool-repo adapter sync failed: ${err.message}`, 'Run `npm run adapters` manually.');
+    }
+    const chatBuild = spawnSync('npm', ['run', 'build:chat'], {
+      cwd: PKG_ROOT,
+      stdio: 'inherit',
+      env: sanitizeNpmSpawnEnv(process.env),
+    });
+    if (chatBuild.status !== 0) {
+      fail('Ink TUI build failed', 'Run `npm run build:chat` manually.');
+    } else {
+      log('built apps/chat/dist/tui.mjs');
+    }
+
+    const dashBuild = spawnSync('npm', ['run', 'build:dashboard'], {
+      cwd: PKG_ROOT,
+      stdio: 'inherit',
+      env: sanitizeNpmSpawnEnv(process.env),
+    });
+    if (dashBuild.status !== 0) {
+      fail('Dashboard build failed', 'Run `npm run build:dashboard` manually.');
+    } else {
+      log('built lib/server/static/ (dashboard)');
+    }
     process.exit(0);
   }
 } catch { /* fall through */ }

package/examples/distribution/README.md

@@ -0,0 +1,42 @@
+# Distribution examples
+
+Branded PDF, HTML, deck, and PPTX samples generated from typed markdown sources. Use these to preview Construct's publish layouts (Space Grotesk, monochrome ink, hand-drawn figures).
+
+## Generate locally
+
+Prerequisites: `construct tools detect --figures` must report ready (pandoc, typst, d2, mmdc; pptxgenjs optional for PPTX). The platform PRD demo requires Playwright in `apps/dashboard` (`npm install`, `npx playwright install chromium`, and `ffmpeg` on PATH for MP4). If browsers are installed outside the sandbox cache, set `PLAYWRIGHT_BROWSERS_PATH` to your Playwright cache (e.g. `~/Library/Caches/ms-playwright` on macOS).
+
+```bash
+npm run examples:distribution
+open .tmp/distribution-examples/index.html
+```
+
+This exports PDF/HTML/deck artifacts with constrained figure sizing (58% max width, 2.35in max height) and records `agentic-platforms-prd.mp4` via the shipped Playwright recording manifest (`templates/demos/recordings/agentic-platforms-prd.json`) — cockpit walkthrough, then scroll through `prd-platform.pdf`.
+
+Deck-only (legacy):
+
+```bash
+npm run examples:deck
+```
+
+## Source layout
+
+| File | artifactType | Typst / HTML layout |
+|------|--------------|---------------------|
+| `sources/prd-platform.md` | prd-platform | construct-prd.typ |
+| `sources/adr.md` | adr | construct-decision.typ |
+| `sources/research-brief.md` | research-brief | construct-research.typ |
+| `sources/runbook.md` | runbook | construct-prd.typ |
+| `sources/rfc-platform.md` | rfc-platform | construct-decision.typ |
+| `sources/strategy.md` | strategy | construct-prd.typ |
+| `sources/deck-one-pager.md` | one-pager | construct-deck.html + PPTX |
+
+Edit sources, then re-run the generator. Outputs land in `.tmp/distribution-examples/` (gitignored).
+
+## Single-file export
+
+```bash
+node bin/construct export examples/distribution/sources/adr.md --to=pdf --figures
+```
+
+See [branding.md](../../docs/reference/branding.md) and [diagram-and-demo.md](../../docs/cookbook/diagram-and-demo.md).

package/examples/distribution/manifest.json

@@ -0,0 +1,53 @@
+{
+  "description": "Branded distribution examples — sources for npm run examples:distribution",
+  "outputDir": ".tmp/distribution-examples",
+  "items": [
+    {
+      "id": "prd-platform",
+      "source": "sources/prd-platform.md",
+      "artifactType": "prd-platform",
+      "formats": ["pdf", "html"],
+      "recording": "agentic-platforms-prd",
+      "demo": "agentic-platforms-prd",
+      "demoSurface": "playwright",
+      "demoArtifact": "prd-platform.pdf",
+      "demoFormat": "mp4"
+    },
+    {
+      "id": "adr",
+      "source": "sources/adr.md",
+      "artifactType": "adr",
+      "formats": ["pdf", "html"]
+    },
+    {
+      "id": "research-brief",
+      "source": "sources/research-brief.md",
+      "artifactType": "research-brief",
+      "formats": ["pdf", "html"]
+    },
+    {
+      "id": "runbook",
+      "source": "sources/runbook.md",
+      "artifactType": "runbook",
+      "formats": ["pdf", "html"]
+    },
+    {
+      "id": "rfc-platform",
+      "source": "sources/rfc-platform.md",
+      "artifactType": "rfc-platform",
+      "formats": ["pdf", "html"]
+    },
+    {
+      "id": "strategy",
+      "source": "sources/strategy.md",
+      "artifactType": "strategy",
+      "formats": ["pdf", "html"]
+    },
+    {
+      "id": "deck",
+      "source": "sources/deck-one-pager.md",
+      "artifactType": "one-pager",
+      "formats": ["deck", "pptx"]
+    }
+  ]
+}

package/examples/distribution/sources/adr.md

@@ -0,0 +1,84 @@
+---
+description: Distribution example — ADR with decision layout, diagrams, and citations.
+artifactType: adr
+subtitle: Centralize brand tokens for every export surface
+version: "1.0"
+doc_id: ADR-BRAND-001
+classification: internal
+status: accepted
+owner: cx-architect
+last_verified_at: 2026-06-22
+---
+
+# ADR-0044: Centralize Construct brand tokens for all export surfaces
+
+- **Date**: 2026-06-22
+- **Status**: accepted
+- **Deciders**: cx-architect, cx-docs-keeper
+- **Supersedes**: none
+
+## Problem
+
+Distribution exports (PDF, HTML, deck, PPTX) and dashboard/chat surfaces drifted when typography moved from retired font families to Space Grotesk and JetBrains Mono. Docs and templates cited stale names; some apps still declared unused npm font packages. Operators could not tell which file was canonical for brand behavior.
+
+## Context
+
+Construct ships a monochrome ink ramp and bundled OFL fonts under `templates/distribution/fonts/`. Chat and dashboard consume the same tokens via `lib/brand-tokens.mjs` and `lib/chat/design-tokens.mjs`. Profile-specific intake terminology flows through `lib/profiles/rebrand.mjs`.
+
+```mermaid
+flowchart LR
+  A[brand-tokens.mjs] --> B[Typst PDF]
+  A --> C[HTML deck]
+  A --> D[Dashboard CSS]
+  E[rebrand.mjs] --> F[CLI + API labels]
+```
+
+```d2
+direction: right
+
+tokens: brand-tokens.mjs {
+  shape: document
+}
+
+pdf: PDF export
+html: HTML export
+dash: Dashboard
+
+tokens -> pdf
+tokens -> html
+tokens -> dash
+```
+
+## Decision
+
+Adopt `lib/brand-tokens.mjs` as the single source of truth for visual brand primitives. Document naming, voice, tone, and profile rebrand in `docs/reference/branding.md`. Enforce retired-font drift with `scripts/audit/03d-brand.mjs` in the audit ratchet.
+
+## Rationale
+
+One token module prevents PDF and web surfaces from diverging when typography changes. A human-facing branding index reduces stale references in cookbooks. Mechanical audit catches Plus Jakarta / Geist regressions without blocking every Write hook.
+
+Evidence: Construct's own publish pipeline already routes Typst templates through `construct-brand.typ`, which imports numeric Space Grotesk weights only — see `templates/distribution/construct-brand.typ`.
+
+## Rejected alternatives
+
+**Per-surface CSS only.** Rejected because PPTX and Typst cannot read dashboard CSS variables; duplication would return on the next rebrand.
+
+**Blocking PostToolUse brand hook.** Rejected as too noisy; the audit ratchet pattern matches existing `03b-naming` enforcement.
+
+## Consequences
+
+Easier: onboarding maintainers, regenerating distribution examples, CI drift detection.
+
+Harder: any new surface must import tokens or fail `03d-brand`.
+
+Locked in: Space Grotesk + JetBrains Mono until an explicit ADR supersedes this one.
+
+## Reversibility
+
+Two-way door for documentation and audit scope; one-way for shipped PDFs already distributed to customers (they retain the font embedded at export time).
+
+## References
+
+- `docs/reference/branding.md`
+- `lib/brand-tokens.mjs`
+- https://fonts.google.com/specimen/Space+Grotesk (accessed 2026-06-22)

package/examples/distribution/sources/deck-one-pager.md

@@ -0,0 +1,65 @@
+---
+description: Golden slide-deck fixture for branded HTML deck and PPTX export examples.
+artifactType: one-pager
+subtitle: Governed agentic platform — stakeholder deck
+version: "0.1"
+doc_id: DECK-PLATFORM-001
+classification: internal
+status: draft
+owner: cx-product-manager
+last_verified_at: 2026-06-20
+---
+
+# Construct Platform Overview
+
+Monochrome ink · Space Grotesk typography · 16:9 slides
+
+---
+
+## Problem
+
+Platform teams orchestrating AI agents lack a **governed operational layer**.
+
+- Cold start — context re-discovered each session
+- Artifacts ship without provenance or citations
+- Exports use host styling, not Construct brand
+
+---
+
+## What Construct provides
+
+1. **Routing** — specialist chains with intent, track, and gates
+2. **Validation** — manifest-enforced structure before distribution
+3. **Document I/O** — many formats in; branded PDF, HTML, deck, PPTX out
+
+---
+
+## Document I/O at a glance
+
+| Direction | Formats |
+|-----------|---------|
+| **Ingest** | PDF, Office, email, AV |
+| **Author** | Typed markdown artifacts |
+| **Export** | PDF, DOCX, HTML, PPTX |
+
+High fidelity: **docling** sidecar (local-first). Fast tier: unpdf/mammoth.
+
+---
+
+## Branded exports
+
+One token set across all distributable formats:
+
+- Ink ramp `#0a0c10` → `#fafafa`
+- **Space Grotesk** body · **JetBrains Mono** code
+- Hand-drawn diagrams in PDF/HTML (D2 sketch + Mermaid)
+
+---
+
+## Next steps
+
+- Export: `construct export … --to=pptx`
+- Regenerate: `npm run examples:deck`
+- Matrix: [Document I/O reference](/reference/document-io)
+
+Review outputs in `.tmp/distribution-examples/`.

package/examples/distribution/sources/prd-platform.md

@@ -0,0 +1,161 @@
+---
+description: Golden prd-platform fixture for publish release-gate and demo tapes; not production product docs.
+artifactType: prd-platform
+subtitle: Governed agentic platform contract for enterprise IDE hosts
+version: "0.1"
+doc_id: PRD-PLATFORM-001
+classification: internal
+intake: none
+intake_rationale: Golden fixture for publish release-gate and demo tapes; not production product docs.
+status: draft
+owner: cx-product-manager
+last_verified_at: 2026-06-19
+publish:
+  demo: agentic-platforms-prd
+---
+
+# Platform PRD: Enterprise Agentic Platform
+
+- **Date**: 2026-06-19
+- **Owner**: cx-product-manager
+- **Status**: draft
+
+> Platform teams need a governed layer between IDE hosts and specialist-authored artifacts — not another chat wrapper. Construct routes work through provenanced invoke plans, blocks distribution until validate passes, and exports briefs that read like finished editorial documents with embedded diagrams rather than markdown dumps. This PRD defines that contract for enterprise agentic platforms.
+
+## Problem
+
+Platform teams orchestrating multiple AI agents lack a governed operational layer. Each coding session starts cold, artifacts ship without provenance, and high-risk writes bypass approval queues. Internal platform consumers (application developers, ops engineers, security admins) currently stitch together ad hoc prompt conventions instead of a durable contract for routing, evidence, and distribution.
+
+Three failure modes recur in internal platform reviews:
+
+1. **Cold start** — specialists re-discover repo context every session because invoke plans are not durable or replayable.
+2. **Unprovenanced artifacts** — PRDs and ADRs reach stakeholders without citation discipline or manifest-enforced structure.
+3. **Distribution drift** — PDF exports use host-default styling; diagrams lack Construct hand-drawn (Excalidraw-adjacent) styling and bundled typography.
+
+## Platform actors
+
+Application developers invoke specialist chains from IDE hosts and expect reproducible PRD outputs. Security admins require citation discipline and release gates before PDF distribution. Ops engineers need toolchain detection that fails loud when Pandoc, Typst, D2, or Mermaid renderers are missing.
+
+The actor map below shows how each role touches Construct without bypassing the shared gate:
+
+```d2
+direction: down
+
+developer: Application developer {
+  shape: person
+}
+
+security: Security admin {
+  shape: person
+}
+
+ops: Ops engineer {
+  shape: person
+}
+
+construct: Construct CLI {
+  style.fill: "#f5f3ff"
+  style.stroke: "#0a0c10"
+}
+
+gate: Release gate\nvalidate + citations {
+  style.fill: "#ede9fe"
+  style.stroke: "#7c3aed"
+}
+
+export: Publish export\nPDF + figures {
+  style.fill: "#0c1018"
+  style.font-color: "#e5e7eb"
+  style.stroke: "#0a0c10"
+}
+
+developer -> construct: invoke + review plan
+security -> gate: citation + reviewer policy
+ops -> export: toolchain detect
+construct -> gate
+gate -> export
+```
+
+## Goals and non-goals
+
+**Goals:** Route requests through provenanced workflow invoke plans; block publish until artifact validate passes; export styled PDFs with Construct-branded D2 and Mermaid figures via a single `construct publish` command; ship bundled typography and masthead layout so exports match across machines.
+
+**Non-goals:** Replacing host LLM execution (Construct returns plans; specialists author content). Mandating npm dependencies in core CLI per ADR-0001. Mandating cloud rendering — all figures resolve locally via D2 and mermaid-cli at export time.
+
+## Platform flow
+
+The end-to-end path from IDE host to distributable PDF is linear and fail-closed at validate:
+
+```mermaid
+flowchart TD
+  A[Host IDE] --> B[construct workflow invoke]
+  B --> C[cx-product-manager]
+  C --> D[Typed artifact on disk]
+  D --> E[construct artifact validate]
+  E --> F[construct publish --figures]
+  F --> G[Styled PDF with diagrams]
+```
+
+The architecture diagram below is the same pipeline at the component level — suitable for architecture reviews and onboarding decks:
+
+```d2
+direction: down
+
+host_ide: Host IDE (session) {
+  shape: person
+}
+
+invoke: construct workflow invoke
+author: Specialist chain
+artifact: Typed artifact {
+  shape: document
+}
+validate: construct artifact validate
+publish: construct publish
+pdf: Branded PDF {
+  shape: document
+}
+
+host_ide -> invoke -> author -> artifact -> validate -> publish -> pdf
+```
+
+## Functional requirements
+
+| ID | Requirement |
+|---|---|
+| FR-1 | `construct publish` runs `validateArtifactRelease` before export when type is known. |
+| FR-2 | Gate failure exits 2 with remediation hints pointing to `prd-workflow`. |
+| FR-3 | PDF export uses bundled Construct Typst template unless `.cx/publish-theme.typ` overrides. |
+| FR-4 | `--figures` renders fenced `d2` and `mermaid` via vendored `pandoc-ext/diagram` with hand-drawn distribution styling (D2 `--sketch`, Mermaid `handDrawn`). |
+| FR-5 | Masthead metadata (`doc_id`, `version`, `classification`) flows from YAML frontmatter — not repeated in body. |
+
+## Success metrics
+
+Adoption is measured by the share of PRDs that pass release gate on first validate and publish without `--no-gate`. Latency targets cover export with figures under ten seconds on a typical laptop.
+
+| Metric | Baseline | Target |
+|---|---|---|
+| Gate pass before publish | manual validate | enforced by default |
+| PDF export p95 | n/a | ≤10s with figures |
+| Demo tapes using `--no-gate` | unknown | 0 in CI |
+| Distribution diagram style | ad hoc | D2 `--sketch` + Mermaid `handDrawn` on every publish |
+
+## Risks and mitigations
+
+| Risk | Likelihood | Impact | Mitigation |
+|---|---|---|---|
+| Draft iteration blocked by hard gate | med | med | PostToolUse advisory hook during Write; gate only at publish |
+| Typst fonts missing on Linux | low | med | Bundled OFL fonts in `templates/distribution/fonts/` |
+| Agents bypass via MCP | med | high | `publish_run` respects gate by default |
+| Figure toolchain missing in CI | med | med | `construct tools detect --figures`; committed demo MP4s as fallback |
+
+Evidence for multi-agent orchestration patterns draws on
+https://arxiv.org/abs/2308.08155 (accessed 2026-06-19) and the LangGraph overview at
+https://langchain-ai.github.io/langgraph/ (accessed 2026-06-19).
+
+## References
+
+- Construct artifact manifest: `specialists/artifact-manifest.json`
+- PRD workflow skill: `skills/docs/prd-workflow.md`
+- Publish cookbook: `docs/cookbook/diagram-and-demo.md`
+- Golden D2 sources: `tests/fixtures/publish/diagrams/`

package/examples/distribution/sources/research-brief.md

@@ -0,0 +1,80 @@
+---
+description: Distribution example — research brief with analytics layout and source table.
+artifactType: research-brief
+subtitle: How teams evaluate agent orchestration layers in 2026
+version: "0.2"
+doc_id: RESEARCH-AGENT-ORCH-2026
+classification: internal
+status: complete
+owner: cx-researcher
+last_verified_at: 2026-06-22
+---
+
+# Research Brief: Agent orchestration adoption among platform teams
+
+- **Date**: 2026-06-22
+- **Author**: cx-researcher
+- **Domain**: developer-tools
+- **Status**: complete
+- **Recency baseline**: Sources from 2024 and later; oldest source used: 2023-08-01
+
+## Question
+
+Do platform teams prefer a governed orchestration layer with provenanced artifacts over host-native agent routing when both are available in the same IDE?
+
+## Method
+
+Searched arXiv and vendor docs (2024–2026), reviewed three internal ADRs on intake routing, and interviewed two construct maintainers. Inclusion: primary or secondary sources with reproducible claims about multi-agent workflows. Exclusion: marketing landing pages without technical depth.
+
+## Sources
+
+| Title / Path | Class | Reliability | Credibility | Date | URL | Verified | Relevance |
+|---|---|---|---|---|---|---|---|
+| Multi-agent survey | secondary | B | 3 | 2023-08-01 | https://arxiv.org/abs/2308.08155 | yes | Patterns for specialist routing |
+| LangGraph overview | primary | A | 4 | 2025-01-15 | https://langchain-ai.github.io/langgraph/ | yes | Stateful agent graphs |
+| Construct architecture | primary | A | 5 | 2026-06-01 | docs/concepts/architecture.mdx | yes | Internal contract |
+
+## Findings
+
+### Finding 1: Provenance gates reduce rework
+
+**Observation**: Teams that enforce `construct artifact validate` before publish report fewer stakeholder rejections on first review (internal survey, n=12, 2026-Q2).
+
+**Inference**: Manifest-enforced structure and citation lint correlate with faster sign-off, not just better prose.
+
+**Confidence**: medium — sample is internal and self-reported.
+
+**Sources**: Construct architecture; maintainer interviews.
+
+### Finding 2: Branded exports improve trust
+
+**Observation**: PDF exports with bundled typography and hand-drawn diagrams are perceived as “finished documents” versus raw markdown attachments (user testing, 2026-05).
+
+**Inference**: Visual consistency signals the same quality bar as the release gate.
+
+**Confidence**: medium — qualitative study only.
+
+**Sources**: Construct publish cookbook; diagram-and-demo user notes.
+
+```mermaid
+flowchart TD
+  Q[Research question] --> S[Source triage]
+  S --> F[Findings + confidence]
+  F --> R[Recommendation]
+```
+
+## Confidence summary
+
+| Theme | Confidence | Gap |
+|---|---|---|
+| Provenance gates | medium | Need external customer sample |
+| Branded exports | medium | Quantitative A/B on open-source adopters |
+
+## Recommendation
+
+Ship distribution examples (`npm run examples:distribution`) so evaluators can compare PRD, ADR, research, and runbook layouts with figures enabled — not markdown stubs alone.
+
+## References
+
+- https://arxiv.org/abs/2308.08155 (accessed 2026-06-22)
+- `docs/cookbook/diagram-and-demo.md`

package/examples/distribution/sources/rfc-platform.md

@@ -0,0 +1,82 @@
+---
+description: Distribution example — platform RFC with decision layout and component diagram.
+artifactType: rfc-platform
+subtitle: Distribution examples gallery for evaluators and CI
+version: "0.1"
+doc_id: RFC-PLATFORM-EXAMPLES-001
+classification: internal
+status: proposed
+owner: cx-architect
+last_verified_at: 2026-06-22
+---
+
+# RFC: Distribution examples gallery
+
+- **Date**: 2026-06-22
+- **Status**: proposed
+- **Authors**: cx-architect, cx-docs-keeper
+- **Reviewers**: cx-product-manager, cx-sre
+
+## Summary
+
+Add `examples/distribution/` sources and `npm run examples:distribution` to regenerate branded PDF, HTML, deck, and PPTX outputs under `.tmp/distribution-examples/` with figures enabled.
+
+## Motivation
+
+Evaluators and maintainers need side-by-side samples of PRD, ADR, research, runbook, and strategy layouts — not certification stubs. Visual richness (Mermaid + D2, metrics tables, severity matrices) demonstrates the publish pipeline under real toolchain conditions.
+
+## Detailed design
+
+```d2
+direction: right
+
+sources: examples/distribution/sources
+script: generate-distribution-examples.mjs
+out: .tmp/distribution-examples
+
+sources -> script -> out
+```
+
+| Artifact type | Typst layout | Example source |
+|---|---|---|
+| prd-platform | construct-prd.typ | prd-platform.md |
+| adr | construct-decision.typ | adr.md |
+| research-brief | construct-research.typ | research-brief.md |
+| runbook | construct-prd.typ | runbook.md |
+| strategy | construct-prd.typ | strategy.md |
+| one-pager deck | construct-deck.html | deck-one-pager.md |
+
+The generator reads `manifest.json`, calls `exportMarkdown` with `figures: true`, and writes `index.html` linking all outputs.
+
+```mermaid
+sequenceDiagram
+  participant Dev as Maintainer
+  participant Script as examples:distribution
+  participant Export as document-export
+  participant Out as .tmp/distribution-examples
+
+  Dev->>Script: npm run examples:distribution
+  Script->>Export: exportMarkdown per manifest item
+  Export->>Out: PDF + HTML (+ deck/PPTX)
+  Script->>Out: index.html gallery
+```
+
+## Drawbacks
+
+- Requires local pandoc, typst, d2, mmdc — fails loud when missing (intentional).
+- `.tmp/` is gitignored; CI may commit snapshots separately if needed.
+
+## Alternatives considered
+
+**Check in binary PDFs.** Rejected — large diffs and stale quickly.
+
+**MkDocs-only previews.** Rejected — does not exercise Typst brand templates.
+
+## Unresolved questions
+
+- Should certification gate regenerate examples on every `release:check`? Deferred — opt-in script for now.
+
+## References
+
+- `docs/reference/branding.md`
+- `scripts/generate-deck-examples.mjs` (prior art)