graham/prop
Watch
1
0
Fork
You've already forked prop
 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

chore: point openspec at the estate store #29

Open
graham wants to merge 1 commit from chore/openspec-store-pointer into main
pull from: chore/openspec-store-pointer
merge into: graham:main
Conversation 1 Commits 1 Files changed 1 +2
graham commented 2026-10-17 16:43:18 +00:00
Owner
Copy link

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.
chore: point openspec at the estate store
All checks were successful
skippy-bot/review Skippy review: clean — no open findings
Details
6c2926d10a
 
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:45:01 +00:00
First-time contributor
Copy link

No findings.

Verified the pointer actually does what it claims: from a directory carrying only this two-line config, openspec list (CLI 1.14.1) resolves OpenSpec root: estate (/home/graham/openspec-estate), exits 0 and writes nothing locally. The file is byte-identical to the pointer already in agent-relay, network, infra and ntxarms, estate is registered in ~/.local/share/openspec/stores/registry.yaml with a matching id: in the store's .openspec-store/store.yaml, and openspec init explicitly refuses to create a local root while the pointer stands, so nothing can silently shadow it. No code in this repo references openspec/, so no build, test or CI path changes.

No findings. Verified the pointer actually does what it claims: from a directory carrying only this two-line config, `openspec list` (CLI 1.14.1) resolves `OpenSpec root: estate (/home/graham/openspec-estate)`, exits 0 and writes nothing locally. The file is byte-identical to the pointer already in `agent-relay`, `network`, `infra` and `ntxarms`, `estate` is registered in `~/.local/share/openspec/stores/registry.yaml` with a matching `id:` in the store's `.openspec-store/store.yaml`, and `openspec init` explicitly refuses to create a local root while the pointer stands, so nothing can silently shadow it. No code in this repo references `openspec/`, so no build, test or CI path changes. <!-- skippy-pr-review -->
All checks were successful
skippy-bot/review Skippy review: clean — no open findings
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin chore/openspec-store-pointer:chore/openspec-store-pointer
git switch chore/openspec-store-pointer

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff chore/openspec-store-pointer
git switch chore/openspec-store-pointer
git rebase main
git switch main
git merge --ff-only chore/openspec-store-pointer
git switch chore/openspec-store-pointer
git rebase main
git switch main
git merge --no-ff chore/openspec-store-pointer
git switch main
git merge --squash chore/openspec-store-pointer
git switch main
git merge --ff-only chore/openspec-store-pointer
git switch main
git merge chore/openspec-store-pointer
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
graham/prop!29
No description provided.