writeonce/.gitignore
shoney.arickathil f0971e1481 feat: installable toolchain — version, wovm self-locate, dist tarball
Close the 3 gaps between "builds in the repo" and "installs from a tarball
like Go", so writeonce can ship to other developers.

- VERSION file at repo root single-sources the toolchain version (0.1.0).
- `woc version` -> "writeonce 0.1.0 linux/amd64"; `wovm --version` -> "wovm
  0.1.0" (stamped by the Makefile from VERSION; --version handled only in the
  plain-wovm path so a built app never shadows its own `version` arg).
- wo.toml `[runtime] wo = ">= X.Y"` is now ENFORCED: woc refuses a project
  requiring a newer toolchain than itself (>= and bare version parsed;
  unknown operators accepted forward-compatibly). Was parsed-and-ignored.
- woc self-locates wovm: --runtime > [build] runtime > $WO_RUNTIME > a `wovm`
  beside the woc binary (Sys.executable_name) > runtime/wovm rel CWD. An
  installed woc in <prefix>/bin finds its sibling wovm from any cwd.
- `just dist` (scripts/mkdist.sh) packages writeonce-<ver>-linux-amd64.tar.gz,
  Go-shaped (archive root writeonce/, bin/{woc,wovm}, README, VERSION), with a
  drift guard asserting VERSION == woc == wovm. dist/ gitignored.
- `just install-accept` (scripts/install-accept.sh) is the gate: extract, PATH,
  version, build+run a project from an unrelated cwd, constraint refusal — 6/0.

Verified: install-accept 6/0; woc-test 565/0; wovm suites + cli_smoke;
log-watcher 7/0. Linux-amd64 only (a cross matrix is future work).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-18 01:19:20 +02:00

103 lines
3.9 KiB
Text

# Cargo build artifacts
/target
# `woc .` manifest builds (wo.toml [build] target)
/docs/examples/log-watcher/target
/docs/examples/employee/target
# Rust runtime (crates/rt/): compiled binary + build artifacts
/crates/rt/target
/crates/rt/Cargo.lock
# C++ prototype build output
/prototypes/*/build
# OCaml/dune build artifacts (compiler/, the woc compiler front)
/compiler/_build
# C runtime (runtime/): compiled binary + WAL/snapshot data.
# `just rt-c-demo` and the default WO_DATA write ./wo-data at the repo root.
/runtime/wo-rt
/wo-data
/runtime/wo-data
# wovm VM core: binary + test build dir (ASan test binaries, smoke fixtures)
/runtime/wovm
/runtime/build/
# Runtime data directories for the sample projects.
# `wo.toml` points at `./data` which holds the per-project engine state.
/data
/docs/examples/*/data
# Legacy blog content and data (v1 writeonce storage)
/content
# Everything in .dev is developer-local (agent-tooling links, and the whole
# reference/ area: v1 archive, rest smoke files, study-tree symlinks —
# untracked 2026-08-08, disk-only; v1 history lives at the pre-move
# reference/ path). Only this README survives:
/.dev/*
!/.dev/README.md
/.dev/reference/
# Study-tree symlinks each contributor recreates per machine:
# ln -s <path-to-linux-src> .dev/reference/linux
# ln -s <path-to-go-src> .dev/reference/go
# ln -s <path-to-postgresql-src> .dev/reference/postgresql
# ln -s <path-to-mcp-python-sdk-src> .dev/reference/mcp-python-sdk
# (clone: https://github.com/modelcontextprotocol/python-sdk.git)
# ln -s <path-to-colibri> .dev/reference/colibri
# ln -s <path-to-llama.cpp> .dev/reference/llama-cpp
# ln -s <path-to-llvm-project> .dev/reference/llvm-project
# ln -s <path-to-dotnet-runtime> .dev/reference/dotnet-runtime
# (sparse clone -- only src/libraries/System.Linq:
# git clone --filter=blob:none --no-checkout --depth 1 \
# https://github.com/dotnet/runtime.git ~/projects/dotnet-runtime
# cd ~/projects/dotnet-runtime && git sparse-checkout init --cone \
# && git sparse-checkout set src/libraries/System.Linq && git checkout)
# Agent-orchestration scratch (SDD ledgers, briefs, review packages)
/.superpowers/
# Editor / OS noise — left broad on purpose so a contributor doesn't
# accidentally commit their IDE scratch or macOS metadata.
.DS_Store
*.swp
*.swo
/.idea/
/.vscode/*
!/.vscode/settings.json.example
!/.vscode/extensions.json
# Phase-F bench binaries (sources are committed; builds are not)
/runtime/bench/bench
/runtime/bench/goref/goref
prototypes/llama-moe-stream/
prototypes/wo-db/
# `tests/` un-ignored 2026-08-11 (plan 3 Task 2): the conformance corpus
# lands under `tests/corpus/` and must be tracked, not invisible to git
# the way the docs below already were once. See docs/plan/learnings.md,
# "check that a new document is actually tracked". No build artifacts
# land under `tests/` — the harness's own scratch files use mktemp
# outside the repo — so nothing needs re-ignoring beneath it.
# Documentation is version-controlled — repo doctrine puts docs under `docs/`,
# and ignoring them there defeats the point. These directories were ignored
# until 2026-08-10, which silently cost the blue-green vision doc (recovered
# from a session transcript) and left all seven forward-roadmap plan docs in
# `docs/superpowers/plans/` existing only on one developer's disk. The rules
# were also half-fiction: 33 of the 34 files under `docs/plan/exploration/`
# were already tracked, so the rule only swallowed *new* files — the worst
# possible failure mode. Do not re-add them.
# docs/examples/agent-loop/
# docs/examples/mcp-think/
# docs/plan/exploration/
# docs/plan/oop-vm/ (carries the .wob format + error-catalog contracts)
# docs/superpowers/plans/
# Python bytecode — the agent-loop / mcp-think samples are Python, and
# un-ignoring their directories above exposed these.
__pycache__/
*.pyc
dist/