worktree start links .sdlc/pipeline.db but not .sdlc/project.yaml, so os-sdlc-runner cannot open in the worktree #526

Closed
opened 2026-09-03 12:40:41 +00:00 by jared · 2 comments
Owner

Context

After worktree start ticket-19, the worktree had .sdlc/pipeline.db -> <main>/.sdlc/pipeline.db but no .sdlc/project.yaml (it is gitignored in the main checkout). This breaks os-sdlc-runner, which cannot open the project without project.yaml in cwd.

Expected behavior

start links or copies project.yaml alongside pipeline.db (or os-sdlc-runner resolves project.yaml from the main checkout).

Workaround

copied project.yaml into the worktree by hand.


Discoverer: hyperthrive-websites, session 01WczDUXXTYSuFuZNRQQLf49, 2026-09-03. worktree start missing project config file linkage breaks downstream tool.

## Context After `worktree start ticket-19`, the worktree had `.sdlc/pipeline.db -> <main>/.sdlc/pipeline.db` but no `.sdlc/project.yaml` (it is gitignored in the main checkout). This breaks os-sdlc-runner, which cannot open the project without project.yaml in cwd. ## Expected behavior start links or copies project.yaml alongside pipeline.db (or os-sdlc-runner resolves project.yaml from the main checkout). ## Workaround copied project.yaml into the worktree by hand. -------- **Discoverer:** hyperthrive-websites, session 01WczDUXXTYSuFuZNRQQLf49, 2026-09-03. worktree start missing project config file linkage breaks downstream tool.
Author
Owner

Mechanism: the worktree CLI does not link gitignored runtime files (here .sdlc/project.yaml). Related, not folded: #982 asks to link .venv and other gitignored files and to let a project declare extra link paths.

Mechanism: the worktree CLI does not link gitignored runtime files (here .sdlc/project.yaml). Related, not folded: #982 asks to link .venv and other gitignored files and to let a project declare extra link paths.
Author
Owner

Resolution

Done: Superseded by #982, which states the defect more clearly

Evidence: #982 covers project.yaml plus other gitignored runtime files (.venv); #526 evidence and its resolve-from-main option were copied to #982

Follow-ups: none

## Resolution **Done:** Superseded by #982, which states the defect more clearly **Evidence:** #982 covers project.yaml plus other gitignored runtime files (.venv); #526 evidence and its resolve-from-main option were copied to #982 **Follow-ups:** none
jared closed this issue 2026-10-18 19:15:06 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
jared/cc-os#526
No description provided.