metaproc 0.2.0__tar.gz

metaproc-0.2.0/.env.example

@@ -0,0 +1,147 @@
+# ─────────────────────────────────────────────────────────────
+# .env.example — generated from the MetaprocEnv registry.
+#
+# DO NOT EDIT BY HAND. To regenerate after a registry change:
+#   uv --config-file uv.toml run --frozen metaproc env --template > .env.example
+# CI gates this file via tests/test_env_template.py.
+#
+# Copy to .env (gitignored) and replace placeholder values.
+# metaproc auto-loads .env on CLI bootstrap, so every variable here is
+# picked up by every `metaproc` command.
+#
+# Legend:
+#   REAL      — real default for this project, copy as-is
+#   SECRET    — illustration only, MUST be replaced with a real secret
+#   TUNABLE   — sensible default, change only if your situation requires it
+#   OPTIONAL  — commented out by default; uncomment and set if needed
+# ─────────────────────────────────────────────────────────────
+
+# TUNABLE — GCP project ID for Batch / Compute operations.
+export METAPROC_GCP_PROJECT=<your-gcp-project-id>
+
+# TUNABLE — Custom service account for Batch VMs. Required in practice — the
+# default compute SA lacks Secret Manager access, so Batch jobs fail silently
+# without it.
+export METAPROC_GCP_SERVICE_ACCOUNT=<worker-sa>@<your-gcp-project-id>.iam.gserviceaccount.com
+
+# TUNABLE — Docker image URI for the GCP Batch agent.
+export METAPROC_GCP_CONTAINER_IMAGE=<region>-docker.pkg.dev/<your-gcp-project-id>/<your-repo>/agent:latest
+
+# TUNABLE — GCP region for Batch jobs.
+export METAPROC_GCP_REGION=us-central1
+
+# TUNABLE — Filestore NFS server IP for shared run artifact storage.
+export METAPROC_GCP_FILESTORE_SERVER=10.0.0.10
+
+# TUNABLE — NFS share name on the Filestore instance.
+export METAPROC_GCP_FILESTORE_SHARE=/<your-share-name>
+
+# TUNABLE — Local mount point for the Filestore share on worker VMs.
+export METAPROC_GCP_FILESTORE_MOUNT_PATH=/mnt/filestore
+
+# TUNABLE — Runs directory on the Filestore mount, used by remote monitoring
+# commands.
+export METAPROC_GCP_FILESTORE_REMOTE_RUNS_DIR=/mnt/filestore/runs
+
+# TUNABLE — Boot disk size (GB) for worker VMs.
+export METAPROC_GCP_BOOT_DISK_GB=50
+
+# TUNABLE — Max run duration (seconds) per Batch task.
+export METAPROC_GCP_MAX_RUN_DURATION_S=28800
+
+# TUNABLE — GCS bucket for run artifact sync and wheel / workspace uploads.
+export METAPROC_GCS_BUCKET=<your-gcs-bucket>
+
+# TUNABLE — Git repo URL that worker containers clone to obtain project code.
+export METAPROC_REPO_URL=https://github.com/<your-org>/<your-repo>.git
+
+# TUNABLE — Git branch workers check out. Typically your current branch or
+# `main`.
+export METAPROC_RUN_BRANCH=main
+
+# TUNABLE — Repo-relative path containing Metaproc's pyproject.toml for editable
+# remote installs.
+export METAPROC_REPO_PACKAGE_PATH=.
+
+# OPTIONAL — GCS path to a prebuilt metaproc wheel. When set, workers install
+# from the wheel instead of cloning.
+# export METAPROC_WHEEL_GCS=gs://<your-gcs-bucket>/wheels/metaproc-0.2.0-py3-none-any.whl
+
+# OPTIONAL — GCS path to a workspace tarball for the active workflow plugin.
+# When set, workers extract and install the plugin from the tarball instead of
+# cloning.
+# export METAPROC_WORKSPACE_GCS=gs://<your-gcs-bucket>/workspaces/<your-plugin>.tar.gz
+
+# OPTIONAL — GCE machine type for orchestrator-launched worker VMs.
+# export METAPROC_MACHINE_TYPE=e2-standard-4
+
+# OPTIONAL — GCE machine type override for `run-process --backend gcp-worker`
+# fan-out workers. Distinct from METAPROC_MACHINE_TYPE, which scopes the
+# orchestrator-launched worker VMs.
+# export METAPROC_GCP_MACHINE_TYPE=e2-highmem-8
+
+# OPTIONAL — SSH gateway host for `metaproc gcp remote` commands.
+# export METAPROC_GATEWAY_HOST=<your-gateway-host>
+
+# SECRET — Base64-encoded service-account JSON for GCP auth. Alternative to ADC.
+export GCP_CREDENTIALS_BASE64=REPLACE_WITH_BASE64_ENCODED_SERVICE_ACCOUNT_JSON
+
+# SECRET — GitHub personal access token for gh-backed workflows.
+export GH_TOKEN=REPLACE_WITH_GITHUB_TOKEN
+
+# REAL — When truthy, the `gh` CLI skips interactive prompts.
+export GH_PROMPT_DISABLED=1
+
+# SECRET — Perplexity API key used by the web search provider.
+export PERPLEXITY_API_KEY=your_api_key_here
+
+# SECRET — Anthropic API key for direct Claude adapter use.
+export ANTHROPIC_API_KEY=REPLACE_WITH_ANTHROPIC_API_KEY
+
+# SECRET — OpenAI API key used by the PI CLI adapter and the codex-cli adapter
+# (Vehicle A, API-key mode).
+export OPENAI_API_KEY=REPLACE_WITH_OPENAI_API_KEY
+
+# SECRET — DeepSeek API key for the pi-cli `deepseek` provider (DeepSeek V4
+# family, direct API).
+export DEEPSEEK_API_KEY=REPLACE_WITH_DEEPSEEK_API_KEY
+
+# SECRET — Moonshot API key for the pi-cli `moonshot` provider (Kimi K2.6,
+# direct API).
+export MOONSHOT_API_KEY=REPLACE_WITH_MOONSHOT_API_KEY
+
+# SECRET — Gemini API key for direct (non-Vertex) Gemini adapter use.
+export GEMINI_API_KEY=REPLACE_WITH_GEMINI_API_KEY
+
+# SECRET — Google API key for direct Gemini adapter fallback.
+export GOOGLE_API_KEY=REPLACE_WITH_GOOGLE_API_KEY
+
+# OPTIONAL — GCP Secret Manager ref that provides GH_TOKEN to Batch workers.
+# export METAPROC_GCP_SECRET_GH_TOKEN=projects/<your-gcp-project-id>/secrets/<secret-name>/versions/latest
+
+# SECRET — Claude Code OAuth credential blob injected into Batch workers from
+# Secret Manager.
+export CLAUDE_CODE_CREDS_JSON=REPLACE_WITH_CLAUDE_CODE_CREDS_JSON
+
+# SECRET — Codex CLI ChatGPT-OAuth credential blob (contents of
+# ~/.codex/auth.json) injected into Batch workers from Secret Manager. Vehicle B
+# only — API-key mode arrives via OPENAI_API_KEY instead.
+export CODEX_CREDS_JSON=REPLACE_WITH_CODEX_CREDS_JSON
+
+# TUNABLE — Default per-step max concurrency. Edit here when Vertex MaaS DSQ
+# quota changes.
+export METAPROC_DEFAULT_MAX_CONCURRENCY=25
+
+# TUNABLE — Default number of workers per step when not specified per-step.
+export METAPROC_DEFAULT_NUM_WORKERS=1
+
+# OPTIONAL — Runtime run-artifact parent directory passed to Metaproc. Required
+# at workflow launch time; set explicitly or derive from workflow run settings.
+# export RUNS_DIR=/absolute/path/to/runs
+
+# OPTIONAL — metabrowser plugin parents to scan, os.pathsep-separated. Each
+# subdirectory containing manifest.toml is loaded. Built-ins and Python entry-
+# point plugins (e.g. metaproc's metabrowser_plugin subpackage) load
+# automatically; this is the opt-in surface for ad-hoc / workspace-local
+# plugins. Auto-discovery from the served root is intentionally NOT a source.
+# export METABROWSER_PLUGINS_DIRS=/path/to/my-plugins:/path/to/team-plugins

metaproc-0.2.0/.flowmarkignore

@@ -0,0 +1,7 @@
+# Generated, vendored, and byte-exact files must retain their source formatting.
+src/metaproc/metabrowser_plugin/plugin/elk.bundled.js
+src/metaproc/metabrowser_plugin/plugin/elkjs-license.txt
+tests/fixtures/
+*.template.md
+.agents/skills/
+.claude/skills/

metaproc-0.2.0/.gitignore

@@ -0,0 +1,189 @@
+# Additions to standard GitHub .gitignore:
+*.bak
+*.orig
+node_modules/
+tmp/
+trash/
+attic/
+.kash/
+.runs/
+**/.logs/
+**/.state/
+
+# Python tool caches
+.ruff_cache/
+
+# GitHub's standard Python .gitignore:
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+!tests/fixtures/claude_api_signals/oauth_refresh_400.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# PyPI configuration file
+.pypirc

metaproc-0.2.0/.node-version

@@ -0,0 +1 @@
+24.18.0

metaproc-0.2.0/.npmrc

@@ -0,0 +1,20 @@
+# Supply-chain safety. See SUPPLY-CHAIN-SECURITY.md.
+
+# Block install/lifecycle scripts by default (the primary exfiltration vector).
+# The repo's git hooks are installed explicitly via `npm run prepare` (an explicit
+# `npm run` still executes under ignore-scripts; install-time scripts do not).
+ignore-scripts=true
+engine-strict=true
+
+# Pin exact versions on `npm install <pkg>` and always maintain the lockfile.
+save-exact=true
+package-lock=true
+
+# 14-day cool-off floor: npm only resolves versions published >=14 days ago.
+# NOTE: `min-release-age` (days) is the npm key, honored on npm 11.10+. The
+# minutes-based `minimum-release-age` key is pnpm-only and silently ignored by
+# npm. On older npm, the cool-off is enforced via NPM_CONFIG_BEFORE in the shell
+# env plus the committed lockfile + frozen `npm ci` installs. Repository
+# workflows pin a compatible Node/npm pair and remove conflicting ambient
+# package-manager variables before invoking npm.
+min-release-age=14

metaproc-0.2.0/.nvmrc

@@ -0,0 +1 @@
+24.18.0

metaproc-0.2.0/CHANGELOG.md

@@ -0,0 +1,61 @@
+# Changelog
+
+All notable user-facing changes are recorded here.
+
+This project uses [Semantic Versioning](https://semver.org/) while it is in the 0.x
+development series.
+
+## [Unreleased][unreleased]
+
+## [0.2.0][] - 2026-07-31
+
+### Added
+
+- Dependency-aware execution of Markdown process specs.
+- Local, agent-CLI, and optional GCP Batch execution backends.
+- Resumable run state, validation, tracing, resource reports, and RunPool controls.
+- Credential-pool operations and adapter integrations.
+- A packaged Metabrowser plugin and portable Agent Skill.
+- Reproducible uv-based development, verification, build, and publishing workflows.
+
+### Changed
+
+- Require `softschema>=0.4.0,<0.5` and `frontmatter-format>=0.4.0,<0.5` (previously
+  `softschema>=0.1.4,<0.2` and `frontmatter-format>=0.3.0`). See the
+  [softschema 0.2.0](https://github.com/jlevy/softschema/releases/tag/v0.2.0) and
+  [softschema 0.3.0](https://github.com/jlevy/softschema/releases/tag/v0.3.0),
+  [softschema 0.4.0](https://github.com/jlevy/softschema/releases/tag/v0.4.0), and
+  [frontmatter-format 0.4.0](https://github.com/jlevy/frontmatter-format/releases/tag/v0.4.0)
+  release notes for the complete upstream migration surface.
+- `metaproc softschema validate` now includes softschema’s `outcome` discriminator
+  (`valid`, `invalid`, or `input_error`) alongside the existing `ok` field.
+- Mapping-based YAML and frontmatter writes are deterministic and alias-free: repeated
+  lists and mappings are expanded instead of emitting anchors.
+  Cyclic values raise `YamlSerializationError` without replacing an existing target.
+
+### Breaking
+
+- `metaproc softschema compile` now requires `--contract CONTRACT_ID`. softschema 0.3
+  makes the contract id a required input to `compile_model`, so the sidecar always
+  records the contract it was compiled for.
+- Softschema 0.2 enforces the contract-id grammar `[namespace:]Name[/version]`. This
+  applies to plugin `Contract` registrations, process-spec `schema` fields, artifact
+  `softschema.contract` metadata, and the `--schema` and `--contract` CLI options.
+  All externally authored IDs must use the new form.
+  Metaproc’s structure-report ID is now `metaproc:StructureReport/v1`, renamed from
+  `metaproc.structure_report.v1`; the other built-in IDs were already valid.
+- Structure reports written by earlier versions no longer validate.
+  Regenerate them with `metaproc structure-report`, or update both `softschema.contract`
+  and `structure_report.schema` to `metaproc:StructureReport/v1`.
+- Softschema 0.3 and 0.4 restrict YAML inputs to bounded, JSON-compatible values.
+  Aliases and anchors, merge keys, explicit tags, duplicate or non-string keys, unsafe
+  integers, negative zero, non-finite numbers, excessive depth, and oversized inputs are
+  rejected. Bare and quoted date- or timestamp-shaped scalars are accepted as strings in
+  0.4; callers that need temporal objects must construct them explicitly after
+  validation.
+- Compiled schemas are validated offline and remote `$ref` targets are never fetched
+  implicitly. Schemas consumed through Metaproc must be self-contained: use local `$defs`
+  references or a registered Pydantic model instead of network-resolved references.
+
+[unreleased]: https://github.com/jlevy/metaproc/compare/v0.2.0...HEAD
+[0.2.0]: https://github.com/jlevy/metaproc/releases/tag/v0.2.0