worktree start links .sdlc/pipeline.db but not .sdlc/project.yaml, so os-sdlc-runner cannot open in the worktree #526
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#526
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
After
worktree start ticket-19, the worktree had.sdlc/pipeline.db -> <main>/.sdlc/pipeline.dbbut 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.
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.
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