dreamteamer 0.30.0 → 0.31.0

package/collections/containers.collection.yaml

@@ -1,81 +0,0 @@
-name: containers
-description: >-
-  A workspace running as a container — one person's editor, harness and compiled workspace over a
-  named volume set, answered over the Docker Engine API rather than from a folder of files.
-use_when: >-
-  a workspace has to RUN somewhere for someone — `dt start container <name> --template <t>` makes
-  one and prints its editor URL; `dt list containers` says what is running and where; `stop`, `open`,
-  `rm` are the lifecycle. Not a record: nothing lands under data/, nothing is committed, and Docker
-  keeps the history
-# MACHINERY WITH A DRIVER, NOT A RECORD COLLECTION. `storage.driver: docker` says every verb on this
-# collection is answered by src/containers.js over the Engine API: `list` is GET /containers/json,
-# `get` is an inspect, `add`/`start` create-and-start, `rm` removes. The derived storage.path names a
-# folder that never exists, so every walker (check, commit, the store's index) reads zero records here
-# and never writes one; the REST route and the CLI dispatch to the driver before the store is asked.
-# `group: system` folds it out of the orientation block's domain listing, beside `repos` and the
-# compiled kinds, which is where a stranger's mental model puts "the thing my workspace runs in".
-storage:
-  driver: docker
-schema:
-  type: object
-  required: [name, template]
-  properties:
-    # ---- identity ----
-    name:
-      type: string
-      description: The workspace name — also the container name and the stem of its three volumes (`dreamteamer-<name>-workspace` · `-home` · `-files`).
-    template:
-      type: string
-      description: The template it was made from — an image carrying `dreamteamer.template`, `dreamteamer.ports` and `dreamteamer.modules` labels; `--template hq` resolves to `<DT_REGISTRY>/hq:<DT_TEMPLATE_TAG>` or to `DT_IMAGE_hq`.
-    image:
-      type: string
-      description: The image reference the container runs.
-    id:
-      type: string
-      description: Docker's short id.
-    # ---- runtime ----
-    state:
-      type: string
-      enum: [created, running, paused, restarting, exited, dead]
-      description: Docker's container state.
-    status:
-      type: string
-      description: Docker's own phrase — `Up 2 hours`, `Exited (0) 3 minutes ago`.
-    started:
-      type: string
-      format: date-time
-      description: When it last started.
-    # ---- network ----
-    editor_url:
-      type: string
-      description: Where the person opens the machine — `http://localhost:<port>/`, its home (every workspace, create, clone); the host port comes from DT_PORT_BASE upward, bound to DT_BIND (127.0.0.1). Never carries the image's URL token — `dt open container <name>` prints the URL that does.
-    port:
-      type: integer
-      description: The host port the editor is published on.
-    bind:
-      type: string
-      description: The host address it is bound to — loopback unless the host .env says otherwise.
-    # ---- storage ----
-    workspace_dir:
-      type: string
-      description: Where the workspace is mounted inside — `/workspaces/<name>`, the dev-container convention.
-    volumes:
-      type: object
-      description: The three named volumes — `workspace` (the repo), `home` (the person's logins and editor settings), `files` (FILES_FOLDER). Plain `rm` keeps them; `rm --force` removes them.
-    mounts:
-      type: array
-      items: { type: string }
-      description: Extra bind or volume mounts passed as `--mount <host-path|volume>:<container-path>[:ro]` — targets under /workspaces · /home/node · /files · /mnt only, none at or under another mount's target (the own volumes included), and no bind source inside another.
-    # ---- person ----
-    person:
-      type: string
-      description: Whose container this is — the git identity injected as env; the harness login happens INSIDE, once, and is never injected.
-    # ---- provenance ----
-    created:
-      type: string
-      format: date-time
-      description: When Docker created it.
-order: 146
-list_fields: [name, template, state, editor_url, person]
-icon: deployed_code
-group: system

package/collections/images.collection.yaml

@@ -1,46 +0,0 @@
-name: images
-description: >-
-  A template a workspace container is made from — a Docker image carrying the `dreamteamer.template`,
-  `dreamteamer.ports` and `dreamteamer.modules` labels — as the local Docker holds it.
-use_when: >-
-  choosing what a container runs — `dt list images` shows the templates present, `dt add image
-  --template <t>` pulls one, `dt rm image <ref>` removes one; a template is an IMAGE WITH LABELS, not
-  a record here, so there is nothing to author — publish an image with the labels and it appears
-# The second driver-backed collection (see containers.collection.yaml for what that means). `list` is
-# GET /images/json filtered to the template label, `get` an inspect, `add --template` a pull, `rm` a
-# delete. No records, no folder, no commit.
-storage:
-  driver: docker
-schema:
-  type: object
-  required: [image]
-  properties:
-    # ---- identity ----
-    image:
-      type: string
-      description: The image reference — `<registry>/<template>:<tag>`.
-    template:
-      type: string
-      description: The `dreamteamer.template` label — the word `--template` takes.
-    id:
-      type: string
-      description: Docker's image id.
-    # ---- what it runs ----
-    ports:
-      type: string
-      description: The `dreamteamer.ports` label — the in-container port the editor listens on (8080 by convention).
-    modules:
-      type: string
-      description: The `dreamteamer.modules` label — the modules the template installs, comma-separated.
-    # ---- size and time ----
-    size_mb:
-      type: integer
-      description: Image size in megabytes.
-    created:
-      type: string
-      format: date
-      description: When the image was built.
-order: 147
-list_fields: [template, image, size_mb, created]
-icon: layers
-group: system

package/collections/proofs.collection.yaml

@@ -1,96 +0,0 @@
-name: proofs
-storage:
-  path: proofs
-  codec: yaml
-  shape: file
-  suffix: proof
-id:
-  generate: '{{ name | slug }}'
-schema:
-  type: object
-  required:
-    - name
-    - about
-    - kind
-  properties:
-    name:
-      type: string
-      description: The proof id — must equal the filename.
-    about:
-      type: array
-      items:
-        type: string
-      description: What this proof is ABOUT — one or more artifact refs it proves something about. An artifact ref is `skills/<id>` · `commands/<id>` · `command-bindings/<id>` · `<module-id>/bin/<file>`.
-    kind:
-      type: string
-      enum:
-        - gate
-        - live
-      description: '`gate` — a static check with no fixture record; `live` — runs against a real record and is judged by `expect`.'
-    mode:
-      type: string
-      enum:
-        - readonly
-        - writes
-      description: Whether a `live` proof only reads the workspace or actually writes to it. Required when kind is live, forbidden on a gate.
-    description:
-      type: string
-      description: What this proof asserts, in one line.
-    external:
-      type: boolean
-      description: Excludes this proof from a bare `--all` run — it needs a network call, a credential or a mount that is not always present. `--external` still runs it.
-    requires:
-      type: object
-      description: What must already be present for this proof to be runnable at all — missing ones make it UNAVAILABLE rather than FAIL.
-      properties:
-        env:
-          type: array
-          items:
-            type: string
-          description: '.env keys (names only, never values) that must be set.'
-        bin:
-          type: array
-          items:
-            type: string
-          description: Binaries that must be on PATH.
-    given:
-      type: object
-      description: The record a `live` proof runs against — either a live filter over a collection or a checked-in fixture. Exactly one of `where`/`fixture`.
-      properties:
-        collection:
-          type: string
-          description: A collection NAME (not a reference) the record is picked from — e.g. `notes`, never `collections/notes`.
-        where:
-          type: object
-          description: 'A filter narrowing which record is picked — the ordinary filter grammar, one reference hop deep. ⚠ It may NOT use `{record}`: the given is what PICKS the record, so nothing substitutes here and compile refuses the literal.'
-        pick:
-          type: string
-          description: '`latest` (the collection''s own `sort_field`, descending — refused when the collection declares none) or an explicit record id. `any` is refused. A `fixture` given REQUIRES a `pick: <id>` naming one of its records.'
-        fixture:
-          type: boolean
-          description: Read the record from this proof's own fixtures folder instead of the live workspace.
-    steps:
-      type: array
-      items:
-        type: object
-      description: What actually runs, in order — a shell command (`run`) or a bound command (`perform`). Required; a gate takes one or more `run` steps, a live proof one or more of either.
-    expect:
-      type: array
-      items:
-        type: object
-      description: 'What must hold for a `live` proof to PASS. Live only, and every row is exactly ONE of four forms — `collection`+`where`+`count` · `record`+`where` · `step` (`exit`/`stdout`/`stdout_json`) · `path`+`exists`. A row whose keys span two forms is a compile error, because compile and the judge would otherwise read it as different shapes. `count` takes its own closed operator set (`_eq _neq _gt _gte _lt _lte _delta`) and every operand must be an INTEGER; a `record:` row REQUIRES a non-empty `where` and takes only the literal `{record}` as its target; a `step:` index past the last step is refused; `stdout` and `stdout_json` are FILTER MAPS (`{ _contains: ''…'' }` · `{ ''a.b'': { _gte: 1 } }`) and a scalar, a list or a bare key is refused, because the judge reads only a map and a row it skips asserts nothing. A `where`''s string literals substitute `{record}` and `{record.<field>}` against the picked record before the filter runs — in an expectation only, never in `given.where`.'
-    timeout:
-      type: integer
-      description: Seconds allowed per `run` step before it is killed.
-order: 46
-# ⚠ NO `last-modified` HERE (M12). Every other list_fields carries it, and on a proof it renders as
-# a bare `-` in the MIDDLE of the row: `dt list proofs` appends two computed columns (availability
-# and the ledger tail) after the declared ones, so the empty cell sits between the about list and
-# the answer the reader came for. A proof's meaningful date is its LAST RUN, which is the `last`
-# column, not the mtime of a file git already tracks.
-list_fields:
-  - name
-  - kind
-  - about
-icon: verified
-group: system

package/skills/using-dreamteamer/references/exporting.md

@@ -1,53 +0,0 @@
-# exporting — the workspace for a reader that is not a coding agent
-
-`compile` renders the runtime for harnesses that read files. `dt export <target>` renders it for a
-consumer that does not: today **NotebookLM**, which holds a bounded number of *sources* per notebook
-and takes its standing instructions as a 10,000-character *persona*. `dt help` has the flags; this
-page has the judgment.
-
-## what travels, and what never does
-
-Sensitivity is SCHEMA, decided once where the field is declared — never a flag on the export and
-never inferred from a field's name (`email` travels unless somebody marked it):
-
-- **a whole collection**: `dt set collections/<c> sensitive=true`. No record of it is written; the
-  schema source and the persona NAME the omission so the reader knows the gap is deliberate.
-- **one field**: `dt add-field <c> --name <f> … --sensitive`, or `dt set-field <c> --name <f>
-  --sensitive` (`--sensitive false` clears). The field is projected out of every record.
-
-Also never exported as records: the system collections (they ARE the schema source) and `codec: file`
-collections (bytes a view draws). **Before the first export of a workspace, read the report** — it
-prints every field that WAS exported per collection; that list is the review.
-
-## what a notebook gets
-
-- **`dt · schema`** — one source: workspace → module → collection → field, one heading level per
-  step, with each collection's `use when`, id shape and every field's type, enum values and reference
-  target. The lexicon the persona cannot afford in full.
-- **`dt · <collection>`** — one source per collection, `## <collection>/<id>` per record, references
-  rendered as `companies/acme (Acme Ltd)`. Over `--max-words` it shards into `dt · <c> [n/m]`.
-- **the persona** — a Markdown template with `{{workspace}}` `{{schema_brief}}` `{{sources}}`
-  `{{omitted}}` `{{exported_at}}` `{{engine_version}}` `{{schema_title}}` `{{collections}}`; the
-  engine ships a default, `--instructions <file.md>` replaces it, an unknown placeholder is an
-  error. `--response-length` and `--mode` ride along to `notebooklm configure`.
-
-**The budget is the plan's source cap** (`--plan standard|plus|pro|ultra|<n>`, default `standard` =
-50). Too many sources is a refusal that names the count and the remedies — nothing is dropped
-quietly. A workspace with more collections than the plan has sources narrows with `--collections`.
-
-## syncing
-
-Without `--notebook`/`--create` the export is a pure render into `--out` (default
-`.cache/dreamteamer/notebooklm/`, gitignored) and touches no network. With one, it makes the notebook
-match **by title**: adds new sources, replaces those whose content hash changed, removes its own stale
-ones (the `dt · ` prefix marks ownership — a source added by hand is never touched), then applies the
-persona. `notebook.json` in the out dir keeps the notebook id and per-source hashes, so the second run
-is incremental and `--create` is needed once. Every vendor call names the notebook with `-n`;
-`notebooklm use` is never run. **Preflight is `notebooklm auth check --test`** — the bare check
-reports a stale session as valid — and an expired login is the operator's to renew (`notebooklm
-login` opens a browser).
-
-## asking
-
-Not a verb here. Ask with `notebooklm ask -n <id> --json`, and treat an answer as real only when it
-has non-blank text AND at least one reference — exit 0 with an empty answer is a known shape.