docs(releases): add 0_7_essence.md (core points of 0.7)

[aaltshuler]

A one-page distillation of the 0.7 release for quick reference, alongside the
full v0.7.0.md:

• Cluster-only server (boots only from --cluster, clusters on object storage)
• Config = two single-owner surfaces (cluster.yaml + ~/.omnigraph/config.yaml); omnigraph.yaml removed
• Unified, capability-aware CLI (one load, honest addressing, stored-query-by-name, aliases, --yes)
• Engine & substrate (Lance 7, indexed traversal, derived-state indexes, recovery liveness, composite @unique)
• Provider-independent embeddings (OpenRouter default, same-space guarantee)
• Must-know breaking changes

🤖 Generated with Claude Code

Greptile Summary

This PR adds docs/releases/0_7_essence.md, a one-page quick-reference distillation of the v0.7.0 release that sits alongside the full v0.7.0.md. The content is accurate and well-structured against the canonical release notes.

• Five core changes covered: cluster-only server, two-surface config (cluster.yaml + ~/.omnigraph/config.yaml), unified capability-aware CLI, Lance 7 engine/substrate improvements, and provider-independent embeddings — all checked against v0.7.0.md and AGENTS.md with no factual errors found.
• Breaking changes list: correctly captures six of the most impactful removals (omnigraph.yaml, positional-URI boot, OpenRouter default, query --alias, positional graph URI, --mode requirement), but omits the --yes requirement for non-interactive destructive writes, which v0.7.0.md explicitly flags as a breaking change for CI scripts.

Confidence Score: 5/5

Documentation-only addition; no code paths, APIs, or on-disk formats are touched. Safe to merge after addressing the missing breaking-change bullet.

The change is a single new markdown file that accurately summarises the v0.7.0 release against both v0.7.0.md and AGENTS.md. All five core changes and the majority of must-know breaking changes are correctly stated; the one gap (the --yes requirement for CI scripts doing non-interactive destructive writes) is an omission in a summary doc, not a wrong statement, and the full details exist in the canonical v0.7.0.md.

docs/releases/0_7_essence.md — the must-know breaking changes list should include the --yes requirement for non-interactive destructive writes.

Important Files Changed

Filename	Overview
docs/releases/0_7_essence.md	New companion summary doc for the v0.7.0 release; all five core changes and most breaking changes accurately reflect the canonical v0.7.0.md. The --yes requirement for non-interactive destructive writes is noted as a feature in item 3 but omitted from the must-know breaking changes list.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[omnigraph CLI verb] --> B{Capability declared?}
    B --> C[any]
    B --> D[served]
    B --> E[direct]
    B --> F[control]
    B --> G[local]

    C --> H["--store / --server / --cluster / --profile"]
    D --> I["--server (+ --graph for multi-graph)"]
    E --> J["--store s3://… or file://…"]
    F --> K["--cluster dir | s3://…"]
    G --> L["No graph address needed"]

    I --> M[HTTP dispatch via GraphClient]
    J --> N[Embedded engine direct storage]
    H --> M
    H --> N

    M --> O{Destructive + non-local?}
    N --> O
    O -- "interactive TTY" --> P[Prompt user]
    O -- "non-TTY / --json" --> Q{--yes passed?}
    Q -- yes --> R[Execute]
    Q -- no --> S[Refuse]
    P -- confirmed --> R

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[omnigraph CLI verb] --> B{Capability declared?}
    B --> C[any]
    B --> D[served]
    B --> E[direct]
    B --> F[control]
    B --> G[local]

    C --> H["--store / --server / --cluster / --profile"]
    D --> I["--server (+ --graph for multi-graph)"]
    E --> J["--store s3://… or file://…"]
    F --> K["--cluster dir | s3://…"]
    G --> L["No graph address needed"]

    I --> M[HTTP dispatch via GraphClient]
    J --> N[Embedded engine direct storage]
    H --> M
    H --> N

    M --> O{Destructive + non-local?}
    N --> O
    O -- "interactive TTY" --> P[Prompt user]
    O -- "non-TTY / --json" --> Q{--yes passed?}
    Q -- yes --> R[Execute]
    Q -- no --> S[Refuse]
    P -- confirmed --> R

Loading

_{Reviews (2): Last reviewed commit: "docs(releases): 0_7_essence as a Slack-p..." | Re-trigger Greptile}

[greptile-apps]

Misleading parenthetical about S3 addressing

The phrase "(a remote is reached only with --server)" describes only HTTP dispatch, but --store s3://bucket/graph.omni also reaches a network-remote location via direct storage access. A reader could conclude they must use --server to address an S3-backed graph, when --store s3://… is the correct flag for direct-storage (non-HTTP) access. The v0.7.0.md is clearer: the distinction is served capability (HTTP, requires --server) vs direct capability (storage, uses --store/--cluster).

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[aaltshuler]

Closing as overtaken by events: v0.8.0 has shipped, so the 0.7-essence digest is historical. Content remains available on this PR if ever needed.