sfh-context-workspacelisted

# Workspace is where effects live; context is what a step knows Keep these axes separate. ```text workspace: current files and side effects context: selected task/evidence/instructions profile: CLI/model/settings session: provider-native conversation cache run artifacts: durable evidence ``` Read [references/context-workspace-session.md](references/context-workspace-session.md). ## Workspace rules - Omitted `workspace:` preserves caller-cwd behavior; do not rely on that accidentally. - Read-only analysis can use `current`. - A change flow should normally use `auto` or `git-worktree`. - One run reuses one managed worktree across implement/test/review/fix visits. - Reviewers read the writer's current workspace. - Do not put multiple potential writers in one fan-out. - `cleanup: keep` for human inspection, release preparation, migrations, or ambiguous completion. - Never assume a clean completed worktree was merged; sfh workspace cleanup and publication are separate concerns. ## Context rules - Use named sources for fixed contracts and bounded handoffs. - Give each step only relevant sources and keep order intentional. - Use `file` for repository knowledge, `inline` for short fixed rules, and `template` for current artifacts. - Bound source and bundle size; use `tail`/`truncate` or an explicit compaction stage. - Do not edit correctness-critical context files while a run is active. Treat them as immutable execution inputs. - External or symlinked context requires explicit