sauron-cli 1.3.0 → 1.4.0

package/OpenSpec-main/openspec/initiatives/context-store-and-initiatives/tasks.md

@@ -1,308 +0,0 @@
-# Context Store And Initiatives Tasks
-
-This tracks roadmap execution for the initiative. Roadmap items live in
-`roadmap.md`; detailed working notes live under `work-items/`.
-
-## Current Beta Priority
-
-After the manual beta pass, prioritize the things a fresh user hits while
-getting started before deeper model work:
-
-1. Finish Item 11 observations enough to keep implementation grounded.
-2. Item 12: no-argument context-store setup, path safety, and
-   cleanup.
-3. Item 13: "Next for your agent" output, direct JSON paths,
-   and baseline guidance/delivery polish.
-4. Item 14: update the beta guide so it matches the improved first-run flow.
-5. Item 15: context-store project roots and sparse schema-led
-   initiatives.
-6. Items 16-18: leave escalation, team hardening, and initiative-hosted
-   target-bound changes until after the onboarding path feels sane.
-7. Item 19: review beta workspace compatibility near the end, before workspace
-   behavior becomes public/stable.
-
-## 1. Lock The Direction
-
-Work item: `work-items/01-lock-the-direction/`
-
-- [x] Record the workspace-to-initiative product boundary in initiative docs.
-- [x] Mark the old workspace reimplementation roadmap as historical reference.
-- [x] Defer workspace apply, verify, and archive until initiative-linked repo
-  changes exist.
-- [x] Complete a non-spec direction pass so roadmap, work items, docs, and
-  active change artifacts point to the initiative as product intent.
-- [x] Decide whether user-facing workspace docs need any change now; default to
-  no unless they misrepresent current behavior.
-- [x] Decide how to handle active no-task workspace changes after the
-  disposition pass.
-- [x] Record final evidence and remaining risks for Item 1.
-
-## 2. Stabilize Workspace As Local View
-
-Work item: `work-items/02-stabilize-workspace-as-local-view/`
-
-- [x] Re-anchor generated workspace guidance in the initiative direction.
-- [x] Decide that generated guidance should stop recommending workspace-level
-  `changes/` as the planning home for coordinated work.
-- [x] Decide that `workspace update` should refresh generated workspace
-  guidance for existing workspaces.
-- [x] Decide that workspace-planning action context should treat beta workspace
-  artifacts as local compatibility context.
-- [x] Decide to defer doctor installed-skill summaries and only update stale
-  `workspace update` wording for now.
-- [x] Define exact local-view behavior to preserve.
-- [x] Review current workspace setup, link, relink, list, open, update, and
-  doctor behavior against that definition.
-- [x] Identify any product wording or guidance gaps left after Item 1.
-
-## 3. Add Context Store Foundation
-
-Work item: `work-items/03-add-context-store-foundation/`
-
-- [x] Define the initial store/backend data model.
-- [x] Decide that the first slice is core API only, with no CLI surface yet.
-- [x] Decide that the first backend is Git/local checkout config only.
-- [x] Decide where context store roots, local registry YAML, and portable store
-  metadata YAML live.
-- [x] Implement context-store foundation helpers and tests.
-
-## 4. Add Collection Foundation
-
-Work item: `work-items/04-add-collection-foundation/`
-
-- [x] Define collection mount rules.
-- [x] Decide validation/template hooks stay inert extension fields for this
-  slice.
-- [x] Prove `initiatives/` can mount without store-specific logic.
-
-## 5. Ship Initiative MVP
-
-Work item: `work-items/05-ship-initiative-mvp/`
-
-- [x] Define initiative file shape and validation.
-- [x] Add templates for requirements, design, decisions, questions, and tasks.
-- [x] Implement create/list mounted collection operations and CLI adapter.
-- [x] Decide full read/show, update, and delete policy should move to later
-  agent-first discovery and lifecycle work.
-
-## 6. Add Minimal Context Store UX
-
-Work item: `work-items/06-add-minimal-context-store-ux/`
-
-- [x] Create Item 6 work-item tracking notes.
-- [x] Define high-level `context-store setup`, `register`, `list`, and `doctor`
-  UX direction.
-- [x] Decide exact checked-in store metadata and machine-local registry
-  behavior.
-- [x] Decide setup/register/list/doctor human behavior and responsibility split.
-- [x] Decide `initiative list` partial-success behavior across registered
-  stores.
-- [x] Decide final Item 6 edge cases: id inference, non-empty setup folders,
-  registry conflicts, empty states, JSON exit behavior, and static completions.
-- [x] Update `initiative list` to default across registered stores, with
-  `--store` as a filter and `--store-path` as an escape hatch.
-- [x] Add focused tests and verification for context-store CLI behavior.
-
-## 7. Add Agent-First Initiative Discovery
-
-- [x] Define `initiative show <id>` human and JSON output.
-- [x] Search registered stores by default and handle ambiguous initiative ids.
-- [x] Return canonical initiative metadata, store identity, root path, and
-  metadata path for agent reads.
-- [x] Keep work-progress status out of this command.
-
-## 8. Connect Repo-Local Changes To Initiatives
-
-Work item: `work-items/08-connect-repo-local-changes-to-initiatives/`
-
-- [x] Decide that the initiative link lives in repo-local `.openspec.yaml`.
-- [x] Add repo-local initiative metadata.
-- [x] Add an agent-friendly create or link flow for repo-local changes.
-- [x] Decide command naming for `--initiative` linking on new change creation.
-- [x] Confirm whether create/link output should report where the change lives,
-  which initiative it references, and the next suggested command.
-- [x] Confirm whether `--initiative <id>` searches registered stores by default
-  or requires explicit store selection in multi-store setups.
-- [x] Keep canonical initiative context in the context store; do not add a
-  checked-in `initiative.md` snapshot by default.
-
-## 9. Reject Initiative Resolve
-
-Work item: `work-items/09-add-initiative-resolve/`
-
-- [x] Pressure-test whether a standalone `initiative resolve` command is needed.
-- [x] Decide not to add `openspec initiative resolve`, now or later.
-- [x] Keep canonical initiative discovery in `initiative show`.
-- [x] Keep local path mapping in workspace behavior.
-- [x] Keep implementation progress in repo-local status.
-- [x] Reject all-repo scans, all-workspace scans, explicit path scanning as an
-  initiative command, Git remote matching, cloning, worktree creation, and
-  initiative backlinks.
-
-## Proposed Discussion: Initiative Next / Agent Handoff UX
-
-Work item draft:
-`work-items/proposed-initiative-next-agent-handoff-ux/`
-
-- [ ] Decide whether to add this as a numbered roadmap item between Item 9 and
-  Item 10.
-- [ ] Decide whether the surface is `initiative next`, workspace initiative
-  opening, or repo-local status guidance.
-- [ ] Decide whether it suggests one next action or multiple ranked options.
-- [ ] Decide that progress/status stays out of scope, unless we explicitly want
-  this command to grow into a broader status surface.
-
-## 10. Let Workspaces Open Initiatives
-
-- [x] Create Item 10 work-item tracking notes.
-- [x] Lock the command UX for opening an initiative as a local workspace view.
-- [x] Define the private local view record for selected context store,
-  initiative, local links, opener, and selected tools.
-- [x] Decide the private local view record storage namespace and keying.
-- [x] Decide the default open target: initiative directory versus full context
-  store.
-- [x] Decide where generated runtime files live and how they are regenerated.
-- [x] Define runtime identity rules for macOS, Codespaces, WSL, SSH, and
-  containers without path translation.
-- [x] Decide the prepare/JSON surface for agents and desktop integrations.
-- [x] Decide the Codex Desktop behavior for generated workspace roots and attached
-  paths.
-- [x] Define advisory edit-boundary output for Item 10.
-- [x] Confirm this slice opens known local paths only and does not create
-  clones, branches, worktrees, or submodules.
-
-## 11. Manual Beta Reality Pass
-
-Work item: `work-items/11-manual-beta-reality-pass/`
-
-- [ ] Manually run the current context-store, initiative, workspace, and
-  repo-local change flows from a fresh user's point of view.
-- [ ] Capture notes on confusing commands, missing prompts, unclear output, and
-  places where the docs over-explain or under-explain.
-- [ ] Update initiative notes as observations come in.
-- [ ] Decide which findings should become implementation slices versus docs-only
-  fixes.
-
-## 12. Context Store First-Run And Cleanup UX
-
-Work item: `work-items/12-context-store-first-run-and-cleanup-ux/`
-
-- [x] Decide and implement interactive no-argument `context-store setup`.
-- [x] Define target-path safety behavior for managed defaults, explicit paths,
-  Git repos, and non-empty directories.
-- [x] Add local cleanup support for unregistering or removing a context store.
-- [x] Make setup and cleanup output report the agreed human-facing summary and
-  exact JSON state without workflow `next_commands`.
-- [x] Update docs and tests for first-run setup and cleanup behavior.
-
-## 13. Agent Handoff Output And Delivery Polish
-
-Work item: `work-items/13-agent-handoff-output-and-delivery-polish/`
-
-- [ ] Decide which commands should print "Next for your agent" handoff guidance.
-- [ ] Add direct created-path JSON fields where agents currently have to
-  reconstruct artifact paths.
-- [ ] Clarify commands-oriented delivery so workflow slash commands are separate
-  from baseline OpenSpec guidance.
-- [ ] Warn when a selected tool cannot receive workflow slash commands.
-- [ ] Update docs, generated agent guidance, and tests for the polished handoff
-  and delivery output.
-
-## 14. Workspaces Beta Guide Split
-
-Work item: `work-items/14-workspaces-beta-guide-split/`
-
-- [ ] Update the user-facing guide to prefer interactive terminal setup for
-  local choices.
-- [ ] Move initiative creation, initiative editing, and repo-local change
-  creation into "ask your coding agent" guidance.
-- [ ] Keep explicit flags, JSON output, cwd rules, and caveats in the
-  agent-facing CLI playbook.
-- [ ] Decide which flags remain useful in user docs as escape hatches for
-  ambiguity.
-- [ ] Record any interactive prompt gaps found while writing the guide.
-
-## 15. Context Store Project Roots And Schema-Led Initiatives
-
-Work item:
-`work-items/15-context-store-project-roots-and-schema-led-initiatives/`
-
-- [x] Create Item 15 work-item tracking notes.
-- [ ] Update initiative direction language so context stores are OpenSpec-aware
-  shared project roots, not only cross-team/cross-repo coordination folders.
-- [ ] Decide the minimal context-store OpenSpec structure:
-  `.openspec-store/store.yaml`, `openspec/config.yaml`,
-  `openspec/schemas/`, and collection mounts.
-- [ ] Decide the store-local config shape for initiative collection defaults,
-  including whether to use `collections.initiatives.schema`.
-- [ ] Decide how context-store setup creates, preserves, or repairs
-  store-local `openspec/config.yaml`.
-- [ ] Define the built-in high-level initiative schema and its initial
-  artifacts.
-- [ ] Decide whether `initiative create` creates only `initiative.yaml`, or
-  `initiative.yaml` plus one schema-selected seed artifact such as `brief.md`.
-- [ ] Replace eager six-file initiative scaffolding with sparse iterative
-  creation.
-- [ ] Add initiative artifact status/instructions behavior rooted at the
-  initiative directory.
-- [ ] Reuse project-local schema resolution with the context-store root as the
-  project root for initiative commands.
-- [ ] Decide whether schema CLI commands need `--store` or `--store-path`
-  selectors.
-- [ ] Guard planning-home resolution so context stores with `openspec/config.yaml`
-  do not accidentally make the store an implementation repo.
-- [ ] Preserve existing six-file beta initiatives as readable valid
-  initiatives.
-- [ ] Update docs, generated agent guidance, and tests for the project-like
-  context-store model.
-
-## 16. Add Escalation UX
-
-Work item: `work-items/16-add-escalation-ux/`
-
-- [ ] Define local-to-initiative recommendation triggers.
-- [ ] Carry current planning context into a new initiative.
-- [ ] Keep prompts grounded in affected areas.
-
-## 17. Harden Team-Shared Coordination
-
-Work item: `work-items/17-harden-team-shared-coordination/`
-
-- [ ] Document recommended Git-backed store setup.
-- [ ] Define teammate onboarding and repair flows.
-- [ ] Add sync status and conflict guidance.
-
-## 18. Explore Initiative-Hosted Target-Bound Change Artifacts
-
-Work item: `work-items/18-explore-initiative-hosted-target-bound-change-artifacts/`
-
-- [ ] Confirm "change home" stays internal language and user-facing wording is
-  closer to "where should this plan live?"
-- [ ] Define user-facing naming for initiative work items, briefs,
-  target-bound changes, artifact homes, and editable targets.
-- [ ] Decide whether initiative-hosted artifacts can graduate into executable
-  changes, and which target metadata is required first.
-- [ ] Decide the configuration or opt-in surface for repo-local versus
-  initiative-hosted artifacts.
-- [ ] Define how `openspec new change` selects and reports the artifact home,
-  implementation target, initiative link, and action context.
-- [ ] Decide how initiative-hosted target-bound changes bind to repo specs,
-  implementation roots, validation, archive, and sync behavior.
-- [ ] Record compatibility behavior for existing repo-local and
-  workspace-local changes.
-- [ ] Identify follow-on implementation slices and risks.
-
-## 19. Review Workspace Beta Compatibility Before Public Release
-
-Work item:
-`work-items/19-review-workspace-beta-compatibility-before-public-release/`
-
-- [ ] Inventory workspace beta compatibility code and tests.
-- [ ] Decide which beta-only compatibility paths should be removed before
-  public release.
-- [ ] Decide which compatibility paths need explicit migration behavior or
-  release notes.
-- [ ] Remove low-value shims that only support unpublished beta workspace
-  shapes.
-- [ ] Update docs, tests, and agent guidance to match the chosen public
-  workspace compatibility contract.

package/OpenSpec-main/openspec/initiatives/context-store-and-initiatives/work-items/01-lock-the-direction/evidence.md

@@ -1,154 +0,0 @@
-# Work Item 01 Evidence
-
-## 2026-05-20 Initial Direction Lock
-
-Completed before this work item folder was created:
-
-- Added locked disposition to `roadmap.md`.
-- Added locked product boundary to `direction.md`.
-- Marked `openspec/changes/workspace-reimplementation-roadmap/START_HERE.md` as historical reference.
-- Marked `openspec/changes/workspace-reimplementation-roadmap/HISTORICAL_DIRECTION.md` as historical reference.
-- Marked `openspec/changes/workspace-reimplementation-roadmap/` as historical
-  reference.
-- Marked `workspace-apply-repo-slice` and `workspace-verify-and-archive` as
-  deferred until initiative-linked repo-local changes exist.
-
-Research findings:
-
-- Current workspace setup, link, relink, list, open, update, and doctor behavior
-  is useful beta local-view infrastructure and should be preserved.
-- Live specs describe current workspace-planning behavior. They should not be
-  rewritten during the initial direction lock; initiative artifacts should carry
-  future product intent until behavior changes.
-- Existing runtime behavior should remain intact until initiatives and linked
-  repo-local changes can replace workspace-level planning.
-
-Verification:
-
-- `git diff --check` passed after the initial direction-lock edits.
-- `openspec validate workspace-reimplementation-roadmap --no-interactive`,
-  `openspec validate workspace-apply-repo-slice --no-interactive`, and
-  `openspec validate workspace-verify-and-archive --no-interactive` failed
-  because those existing active changes have no spec deltas. That predates the
-  disposition wording and is tracked as an active-change cleanup question.
-
-## 2026-05-21 Initiative Entry Point
-
-Added `README.md` as the initiative entry point and linked it from
-`.initiative.yaml`.
-
-The README explains:
-
-- this initiative is the source of product intent
-- the reading order for direction, roadmap, tasks, decisions, questions, and
-  work items
-- specs remain the current behavioral contract behind the code
-- specs should not be rewritten for future intent until behavior changes
-
-Updated `work-items/01-lock-the-direction/tasks.md` to mark the initiative
-source-of-intent review complete.
-
-## 2026-05-21 Historical Workspace Roadmap Review
-
-Reviewed the historical workspace reimplementation entry points:
-
-- `openspec/changes/workspace-reimplementation-roadmap/START_HERE.md`
-- `openspec/changes/workspace-reimplementation-roadmap/HISTORICAL_DIRECTION.md`
-- `openspec/changes/workspace-reimplementation-roadmap/README.md`
-- `openspec/changes/workspace-reimplementation-roadmap/proposal.md`
-- `openspec/changes/workspace-reimplementation-roadmap/POC_REFERENCE_GUIDE.md`
-
-Added a guard near the top of
-`openspec/changes/workspace-reimplementation-roadmap/HISTORICAL_DIRECTION.md` stating
-that the remaining sections are historical POC follow-up direction and should
-not be treated as active implementation guidance.
-
-The roadmap README and handoff prompt already direct agents to the initiative
-direction first and warn not to continue the old flat sibling queue unless a
-later initiative-linked repo-change design reactivates it.
-
-## 2026-05-21 Active Workspace Proposal Review
-
-Reviewed active workspace proposal artifacts:
-
-- `workspace-reimplementation-roadmap`
-- `workspace-agent-guidance`
-- `workspace-apply-repo-slice`
-- `workspace-verify-and-archive`
-
-Added small notes to `workspace-apply-repo-slice` and
-`workspace-verify-and-archive` clarifying that the remaining proposal sections
-are preserved for later reference, not discarded, and should become relevant
-again after initiatives and initiative-linked repo-local changes exist.
-
-Left `workspace-agent-guidance` untouched because it already has unrelated
-worktree edits and should be handled as a separate active-change disposition
-decision.
-
-## 2026-05-21 User-Facing Docs Decision
-
-Decision: Do not update `docs/cli.md` as part of the initial direction lock
-unless it misrepresents current user-facing behavior.
-
-Reasoning:
-
-- The direction lock is for contributors and agents deciding what to build next.
-- User-facing docs should describe current CLI behavior, not future initiative
-  intent.
-- Initiatives do not have a CLI surface yet, so announcing the pivot in user
-  docs would draw attention to an internal product direction before users can act
-  on it.
-
-Revisit user-facing docs when initiative or context-store commands exist, or if
-current docs promise unavailable workspace apply, verify, or archive behavior.
-
-Verification:
-
-- `git diff --check` passed.
-- No files under `openspec/specs/` or `schemas/workspace-planning/` were
-  modified in this pass.
-
-## 2026-05-21 Active Change Disposition
-
-Decision: Keep the active workspace changes as deferred reference placeholders.
-
-Rationale:
-
-- Workspace agent guidance, apply, verify, and archive are still expected to
-  matter after initiative infrastructure exists.
-- The immediate focus should be context stores, initiatives, and
-  initiative-linked repo-local changes.
-- Keeping the proposals preserves research and continuity without making them
-  the next implementation queue.
-
-Follow-up:
-
-- Revisit the deferred workspace changes after initiative-linked repo-local
-  changes define the durable handoff model.
-
-## Final Item 1 State
-
-Item 1 is complete.
-
-What is locked:
-
-- Initiative artifacts are the source of product intent for context stores,
-  collections, initiatives, workspaces, and repo-local changes.
-- Specs and schemas remain the current behavioral contract and were not edited
-  for future intent.
-- Historical workspace roadmap artifacts remain available as reference, not as
-  the active shipping queue.
-- Deferred workspace changes remain active reference placeholders because their
-  domains are expected to matter after initiative infrastructure exists.
-- User-facing docs were intentionally left unchanged unless they misrepresent
-  current behavior.
-
-Remaining risks:
-
-- `openspec list` still shows deferred workspace changes as active no-task
-  changes. This is intentional for now but may remain visually noisy.
-- `workspace-agent-guidance` has unrelated worktree edits and should be handled
-  carefully before any future commit or archive decision.
-- Future agents still need to read the initiative README first; the historical
-  workspace docs are safer now, but still contain useful old lifecycle details
-  deeper in the file.

package/OpenSpec-main/openspec/initiatives/context-store-and-initiatives/work-items/01-lock-the-direction/plan.md

@@ -1,90 +0,0 @@
-# Work Item 01: Lock The Direction
-
-## Goal
-
-Make the workspace-to-initiative pivot explicit enough that future agents and
-contributors do not continue implementing the older "workspace owns the plan"
-model.
-
-The locked model is:
-
-```text
-Context stores sync truth.
-Collections shape truth.
-Initiatives coordinate work.
-Workspaces open local views.
-Changes implement repo-owned slices.
-```
-
-## Direction
-
-This work item is a non-spec direction pass, not a runtime removal.
-
-Specs should continue to describe the current behavioral contract behind the
-code. Product intent, roadmap decisions, and future direction should live in the
-initiative artifacts until a later implementation change intentionally updates
-behavior and its specs together.
-
-Keep:
-
-- workspace setup, link, relink, list, open, update, and doctor
-- linked repos and folders as local planning context
-- workspace-local skills as local agent guidance
-- "workspace visibility is not change commitment"
-
-Mark as transitional:
-
-- workspace-level `changes/` planning
-- `workspace-planning` schema
-- workspace-scoped status/instructions compatibility
-
-Defer:
-
-- workspace apply, verify, and archive as first-class lifecycle commands
-- branch/worktree orchestration
-- strong cross-repo validation
-- dependency graph enforcement
-
-Supersede:
-
-- workspace as the durable shared planning home
-- workspace-level planning artifacts as the canonical cross-repo plan
-- workspace change planning as the long-term source of truth
-
-## Files To Review Now
-
-- `openspec/initiatives/context-store-and-initiatives/*.md`
-- `openspec/initiatives/context-store-and-initiatives/work-items/**/*.md`
-- `openspec/changes/workspace-reimplementation-roadmap/START_HERE.md`
-- `openspec/changes/workspace-reimplementation-roadmap/HISTORICAL_DIRECTION.md`
-- `openspec/changes/workspace-reimplementation-roadmap/*`
-- active `openspec/changes/workspace-*` proposals
-- `docs/cli.md`
-
-## Files To Leave Alone For Now
-
-- `openspec/specs/**/*.md`
-- `schemas/workspace-planning/**`
-
-Those files should change only when we intentionally change behavior or create a
-repo-owned implementation change that updates the relevant behavioral contract.
-
-## Non-Goals
-
-- Do not remove current workspace-planning runtime behavior.
-- Do not delete the `workspace-planning` schema.
-- Do not add CLI deprecation warnings until the initiative replacement exists.
-- Do not implement context stores in this work item.
-- Do not edit OpenSpec specs as part of the initial direction lock.
-
-## Done When
-
-- Initiative artifacts clearly carry the product intent and roadmap decisions.
-- Historical workspace roadmap artifacts no longer read as the active shipping
-  queue.
-- User-facing docs describe current workspaces as local views where that does
-  not contradict current behavior.
-- Existing workspace-planning behavior is clearly treated as current behavior,
-  not the future product model, in initiative and roadmap artifacts.
-- Workspace apply, verify, and archive are clearly deferred.
-- Fresh agents can identify the initiative direction as the source of truth.

package/OpenSpec-main/openspec/initiatives/context-store-and-initiatives/work-items/01-lock-the-direction/tasks.md

@@ -1,44 +0,0 @@
-# Work Item 01 Tasks
-
-## Tracking Setup
-
-- [x] Create initiative-level `tasks.md`, `decisions.md`, and `questions.md`.
-- [x] Create `work-items/01-lock-the-direction/`.
-- [x] Record why roadmap implementation is tracked inside the initiative instead
-  of creating a new OpenSpec change.
-
-## Direction Lock Already Captured
-
-- [x] Add locked disposition to `roadmap.md`.
-- [x] Add locked product boundary to `direction.md`.
-- [x] Mark `openspec/changes/workspace-reimplementation-roadmap/START_HERE.md` as historical reference.
-- [x] Mark `openspec/changes/workspace-reimplementation-roadmap/HISTORICAL_DIRECTION.md` as historical reference.
-- [x] Mark `workspace-reimplementation-roadmap` as historical reference.
-- [x] Mark `workspace-apply-repo-slice` as deferred.
-- [x] Mark `workspace-verify-and-archive` as deferred.
-
-## Non-Spec Direction Pass
-
-- [x] Keep OpenSpec specs unchanged until behavior changes.
-- [x] Review initiative artifacts for a clear source-of-intent story.
-- [x] Review historical workspace roadmap artifacts for any remaining language
-  that tells agents to continue the old shipping queue.
-- [x] Review active workspace proposal artifacts for any remaining language that
-  presents workspace apply, verify, or archive as next.
-- [x] Decide whether user-facing docs need changes now; default to no unless
-  they misrepresent current behavior.
-- [x] Record a decision that specs remain current behavioral contracts, while
-  initiative docs carry future product intent.
-
-## Active Change Disposition
-
-- [x] Decide whether `workspace-agent-guidance` should be reframed, closed, or
-  kept as a local-view guidance item.
-- [x] Decide whether no-task deferred workspace changes should stay active,
-  move to archive, or be represented only by initiative work items.
-
-## Verification
-
-- [x] Run `git diff --check`.
-- [x] Confirm no OpenSpec specs were modified in this pass.
-- [x] Record evidence in `evidence.md`.

package/OpenSpec-main/openspec/initiatives/context-store-and-initiatives/work-items/02-stabilize-workspace-as-local-view/evidence.md

@@ -1,68 +0,0 @@
-# Stabilize Workspace As Local View Evidence
-
-## Direction Evidence
-
-`direction.md` says the durable shared object is a synced context store, with
-initiatives as the first major collection. It defines workspaces as local
-working views over context stores and repos, and repo changes as repo/team-owned
-implementation plans.
-
-The locked product boundary supersedes the older model where a workspace-level
-`changes/` tree owned the canonical shared cross-repo plan. Existing
-workspace-planning behavior can remain as beta or legacy infrastructure, but it
-should not steer new lifecycle design.
-
-## Subagent Research
-
-Implementation research found that workspace setup, link, relink, list, open,
-update, and doctor already mostly behave like local-view infrastructure:
-
-- shared link names live in workspace state
-- machine-local paths and opener/skill state live in local state
-- `workspace open` launches linked folders as a local working set
-- linked repos are treated as context for workspace-planning commands
-- `workspace update` refreshes workspace-local skills and leaves linked repos
-  untouched
-
-Guidance research found that the generated `AGENTS.md` block is the most
-important mismatch because it still frames the workspace as planning across
-linked repos and says to use `changes/` for workspace-level planning.
-
-Test research found strong current coverage for setup/list/doctor, link/relink,
-open, update, artifact placement, and workspace-planning guards. The targeted
-workspace/artifact test slice passed, as did the skill-template parity test.
-
-## Main Risk
-
-If generated workspace guidance continues to recommend workspace-level
-`changes/`, agents may treat the workspace as the durable shared planning
-object even though the initiative direction assigns durable coordination to
-initiatives and implementation planning to repo-local changes.
-
-## Implementation Evidence
-
-The first implementation slice updates the generated workspace `AGENTS.md`
-guidance and makes `workspace update` refresh the workspace-local open surface.
-It also updates workspace-planning action context so beta workspace artifacts are
-reported as `workspace-local` compatibility context instead of the source of
-truth.
-
-Doctor/status review found that local path mappings, unresolved links, repair
-steps, malformed local state, missing local state, repo specs paths, and skill
-drift warnings are already covered. Normal installed-skill summaries are
-deferred for now; the current slice only updates stale `workspace update`
-wording so it matches the guidance refresh behavior.
-
-Verification:
-
-- `pnpm run build`
-- `pnpm exec vitest run test/commands/workspace.test.ts test/commands/artifact-workflow.test.ts test/core/workspace/foundation.test.ts`
-- `pnpm run lint`
-- `git diff --check`
-
-## Closeout Evidence
-
-Live docs no longer describe workspaces as durable planning homes or as the
-canonical place for cross-repo planning. Historical and deferred workspace
-artifacts remain as reference material, with active deferred proposals labeled
-so they do not steer the next implementation slice.