chore: point openspec at the estate store #40

Merged

graham merged 1 commit from chore/openspec-store-pointer into main

2026-10-18 17:34:51 +00:00

graham commented

2026-10-17 16:43:16 +00:00

Owner

Planning markdown lives in the OpenSpec store estate (~/openspec-estate) instead of this repo, so specs and change documents stay out of the repo history.

This file is the whole footprint: openspec/config.yaml declaring store: estate. Every openspec command run here resolves to the store.

Nothing is deleted: it adds one two line file.

Planning markdown lives in the OpenSpec store `estate` (~/openspec-estate) instead of this repo, so specs and change documents stay out of the repo history. This file is the whole footprint: `openspec/config.yaml` declaring `store: estate`. Every `openspec` command run here resolves to the store. Nothing is deleted: it adds one two line file.

graham added 1 commit

2026-10-17 16:43:16 +00:00

chore: point openspec at the estate store

Elixir CI / Build and test (pull_request) Failing after 2m42s

Details

skippy-bot/review Skippy review: clean — no open findings

Details

Elixir CI / Dialyzer (pull_request) Successful in 3m40s

Details

Elixir CI / Build and Push Docker Image (pull_request) Has been skipped

Details

0c494a7154

Planning markdown lives in the OpenSpec store `estate`; the repo carries only
this two line pointer, so spec and change documents never enter its history.

skippy-bot commented

2026-10-17 16:46:20 +00:00

First-time contributor

Reviewed the full diff (1 file, +2). No findings.

openspec/config.yaml with store: estate is a valid project-level store pointer. Verified by running openspec context --json (1.14.1) in a scratch dir holding exactly these two lines: it resolves source: declared, store_id: estate, root ~/openspec-estate, and openspec list reads the estate's changes.

Nothing shadows it: openspec/ on main is absent, so there is no changes//specs/ planning shape (which would make the CLI warn and ignore the declaration). Nothing consumes it either: .forgejo/workflows/ci.yml, README.md and .gitignore have no openspec references, so no build or script path changes.

Only caveat, and it is by design rather than a defect: the pointer hard-errors (Unknown store 'estate') on a machine where that store is not registered, instead of falling back. Expected on a single-owner estate, and the error names the fix.

Reviewed the full diff (1 file, +2). No findings. `openspec/config.yaml` with `store: estate` is a valid project-level store pointer. Verified by running `openspec context --json` (1.14.1) in a scratch dir holding exactly these two lines: it resolves `source: declared`, `store_id: estate`, root `~/openspec-estate`, and `openspec list` reads the estate's changes. Nothing shadows it: `openspec/` on main is absent, so there is no `changes/`/`specs/` planning shape (which would make the CLI warn and ignore the declaration). Nothing consumes it either: `.forgejo/workflows/ci.yml`, `README.md` and `.gitignore` have no `openspec` references, so no build or script path changes. Only caveat, and it is by design rather than a defect: the pointer hard-errors (`Unknown store 'estate'`) on a machine where that store is not registered, instead of falling back. Expected on a single-owner estate, and the error names the fix.

graham merged commit d7e932eaaf into main

2026-10-18 17:34:51 +00:00

graham deleted branch chore/openspec-store-pointer

2026-10-18 17:34:51 +00:00

graham referenced this pull request from a commit

2026-10-18 17:34:51 +00:00

chore: point openspec at the estate store (#40)