lisa-tracker-journey

name	lisa-tracker-journey
description	Vendor-neutral wrapper for executing a ticket/issue's Validation Journey end-to-end. Reads the required `tracker` from .lisa.config.json and dispatches to lisa-jira-journey, lisa-github-journey, or lisa-linear-journey. Parses the journey, satisfies prerequisites, executes the steps, captures evidence at each marker, and posts results via tracker-evidence.
allowed-tools	["Skill","Bash","Read"]

Tracker Journey: $ARGUMENTS

Thin dispatcher. Resolves the configured destination tracker and delegates to the matching vendor journey skill.

See the config-resolution rule for configuration and dispatch table.

Workflow

1. Resolve tracker config (same logic as lisa-tracker-write).
2. Dispatch:
   • Missing / empty → stop and report "No tracker configured in .lisa.config.json. Run /lisa:setup:jira, /lisa:setup:github, or /lisa:setup:linear first."
   • jira → invoke lisa-jira-journey with $ARGUMENTS verbatim. Arg shape: <TICKET_ID> [PR_NUMBER].
   • github → invoke lisa-github-journey with $ARGUMENTS verbatim. Arg shape: <ISSUE_REF> [PR_NUMBER].
   • linear → invoke lisa-linear-journey with $ARGUMENTS verbatim. Arg shape: <IDENTIFIER> [PR_NUMBER].
   • Anything else → stop and report "Unknown tracker '<value>' in .lisa.config.json. Expected 'jira', 'github', or 'linear'."
3. Pass through the output.

Rules

• The journey content is identical across vendors; only the parser source differs (the JIRA vendor reads description via Atlassian MCP; the GitHub vendor reads body via gh issue view --json body; the Linear vendor reads description via lisa-linear-access operation: get-issue).
• Evidence posting always goes through lisa-tracker-evidence — never bypass.