Megamono

DOCUMENTATION

On this page
  1. When to use it
  2. Usage
  3. Options
  4. Next steps

docs-archive

Apply a terminal lifecycle transition and archive a repository document

When to use it

This is a lifecycle mutation, not just a report. Preview with dryRun=true and review the terminal status, replacement, and reason.

Usage

Configure an Nx target on the owning project, then invoke it with npm exec -- nx run <project>:<target>. The executor identifier is not a standalone CLI command.

json
{
  "targets": {
    "reviewed-action": {
      "executor": "@megamono/plugin:docs-archive",
      "options": {
        "id": "<id>"
      }
    }
  }
}

This target is a configuration example. Supply required values and review side effects before invoking it.

Options

Use these options with @megamono/plugin:docs-archive. Nx uses the camelCase names shown here; the CLI reference describes command-line aliases. Some options are required only for particular choices.

OptionRequiredTypeDefaultDescription
idYesstring—Stable document ID to archive.
statusNostring—Type-valid terminal status. Allowed: "completed", "aborted", "retired", "superseded", "complete".
reasonNostring—Required reason when aborting a plan.
replacementIdNostring—Replacement spec ID when superseding a spec.
completedAtNostring—Completion timestamp override for deterministic automation.
configNostring"megamono.json"—
docsRootNostring——
dryRunNobooleanfalse—

Next steps

Review changed files and run the affected project's checks. For options that accept structured values, run the generator's --help or consult the schema in the installed package.

Megamono

One repository system for the applications, tools, and people building together inside it.

BUILD

Get startedGuidesDocumentationCLI referenceCapabilitiesInference

SOURCE

GitHub ↗

MIT licensed

© 2026 Megamono

By

Commune Software