NDDev-it-com/nddev-zcode-app

nddev-zcode-app

nddev-zcode-app is a reusable build system and installer for a complete, version-stamped ZCode setup. It recreates ~/.zcode from the managed nddev-builder marketplace on macOS or Ubuntu, backs up the previous installation, and selectively restores runtime state so sessions and credentials survive setup changes.

• Author: Danil Silantyev (github:rldyourmnd), CEO NDDev
• License: AGPL-3.0-or-later
• Release metadata: build/version.json
• Verified runtime baseline: references/zcode-baseline.json

What this repository contains

This public repository contains only the distributable implementation:

zcode_tools/   Marketplace source: the complete editable nddev-builder setup
cli-tools/     Installer and lifecycle commands for macOS and Ubuntu
build/         Version, artifact-integrity, manifest, and secret contracts
config/        Public product and native-format contract metadata
references/    Public ZCode compatibility baseline
docs/          Public architecture, installation, and secrets documentation

Development-only context, validation code, tests, and benchmarks are not part of the public distribution. The tracked public surface is owned by build/manifest.json.

See docs/architecture.md for the component and repository boundaries.

Quick start

# Optional: configure explicit API-key providers or custom local settings.
# Z.ai account OAuth remains the default; build/.env is gitignored.
cp build/.env.example build/.env
chmod 600 build/.env
$EDITOR build/.env

# Install the pinned ZCode app and CLI, if needed.
cli-tools/scripts/install.sh bootstrap --plan
cli-tools/scripts/install.sh bootstrap --apply

# Inspect and install the managed setup.
cli-tools/scripts/install.sh list

cli-tools/scripts/install.sh install --plan

Quit the ZCode desktop app before apply-mode target changes.

cli-tools/scripts/install.sh install --apply cli-tools/scripts/install.sh status cli-tools/scripts/install.sh status --json

Plan mode performs no writes and does not invoke a locally installed `zcode`
binary. It still parses and merges config, setting, provider, MCP, and hook
inputs, requires the explicit CLI model/provider bootstrap declared by
[`build/manifest.json`](build/manifest.json), rejects custom providers that reuse reserved `builtin:*` identities,
and rejects unresolved active placeholders in keys or values. Setup installation
in apply mode performs a bounded live runtime probe and rejects open
task/session databases or SQLite recovery sidecars before it changes the target.
See [docs/install.md](docs/install.md) for install, update, posture, backup,
restore, remove, and custom-target usage.

## Managed Setup

The public catalog installs one managed setup by default:

• nddev-builder enables its reusable core toolkit for creating and managing

ZCode marketplaces, plugins, and components. Its exact component inventory is the convention-discovered tree under zcodetools/marketplaces/nddev-builder/plugins/core/.

install uses nddev-builder when no setup flag is supplied. --setup nddev-builder is still accepted, and --marketplace nddev-builder remains a compatibility alias for the underlying ZCode-native storage format. --posture full-auto is the default; --posture safe renders the same managed setup with a stricter interaction posture. Every new BUILD-VERSION schema-2 stamp records setupid and posture, and status validates and reports both.