# DARKOZA Language 0.2.0-alpha.1 — Release report

**Date:** 2026-11-12  
**Environment:** srv7700305575, Linux, Python 3.14.4  
**Release status:** implemented and locally validated; static public preview only.

## Delivered

- Unified CLI: dkz (version, check, build, run, exec, debug, fmt, test, pkg, doc).
- Runtime: Stage-0 Python stack VM; DKZ-BYTECODE v2; v1 compatibility retained.
- Standard library: abs, min, max, clamp, sqrt, contains, starts_with,
  ends_with, plus existing len and to_text.
- Package manager: offline project init, manifest validation, package archive,
  local installation, listing and removal.
- Debugger: interactive instruction step/continue/breakpoints and JSONL trace.
- Formatter: validation-first indentation normalization and read-only check mode.
- Test runner and API signature documentation generator.
- Formalized runtime, language, package manager, debugger and toolchain docs.

## Test evidence

- Python bytecode compilation of compiler modules, launchers and tests: PASS.
- Full unit suite: **65 tests passed, 0 failures**.
- Existing DKZ-BYTECODE v1 fixture: successfully decoded and executed.
- New v2 intrinsic opcodes: validation rejects their use in v1 payloads.
- Hello-world compile/run: PASS; expected output returned.
- Formatter check and idempotence: PASS.
- Package smoke test: init -> validate -> pack -> install: PASS.
- Package tests reject path traversal and checksum corruption.
- API documentation generator wrote a sample reference successfully.

Test command:

    bin/dkz test -q

## Package-manager security controls

- Offline-only; no automatic network fetch.
- Canonical relative paths; traversal and backslash paths rejected.
- Symlink and special-file entries rejected.
- File count and uncompressed size bounded.
- Archive members must match the checksum manifest exactly.
- Manifest entry must be a regular source file.
- Installs are staged and atomically renamed.
- Existing project files cannot be overwritten by the archive output.

These controls are useful safeguards, not an independent security audit.

## Performance and maturity boundary

No representative throughput, latency, CPU or memory comparison was performed.
No native backend, self-hosted compiler, Stage-1/Stage-2 agreement, formal
verification, external security audit or production workload integration is
claimed.

The package manager has no online registry, signing/trust model, dependency
solver or import linker. The formatter is conservative and does not reflow
expressions. Debugger source-line mapping is not implemented.

## Deployment boundary

The public release is static documentation and downloadable source. No hosted
code-execution endpoint, production service, payment path, credential path,
database, DNS, firewall or existing Caddy route is changed by this release.
Existing DKZ source and binaries were backed up before promotion. Rollback
consists of restoring the pre-release source snapshot and prior versioned
directory.

## Next gates

1. Fuzzing and differential verification of lexer, parser, compiler, bytecode
   verifier and VM.
2. Independent security review and package-signature design.
3. Implement module linking and a dependency graph with supply-chain controls.
4. Build and verify a self-hosted compiler.
5. Isolated execution worker, quotas and abuse controls before hosted execution.
