context-resolution

Git push targets and project context are validated by reading .claude/workflow.yaml fields like project.name and project.template, then parsing git remotes to derive push_org and push_repo with enforced target safety and clear errors.

During initial git bootstrap setup, the system enumerates git remotes to pre-parse candidate org/repo pairs, allowing first-run configuration to proceed by deriving project identity directly from repository remote URLs.

GitHub and local brief tracking resolves briefs from GitHub issues or local files and maps brief lifecycle statuses to GitHub labels when tracking is enabled in the project configuration.

Non-GitHub remote URLs are supported for push target derivation but trigger warnings, as the system normalizes GitHub and SSH remote URLs to enforce target safety and prevent accidental cross-target operations.

Structured-workflows commands fail to resolve project identity when required .claude/workflow.yaml fields such as project.name, project.domain, or project.template are missing or invalid, producing clear validation errors.

Context resolution prevents accidental cross-target git operations by locking the session target after deriving push_org and push_repo from configured remotes, ensuring commands only execute against the validated target.