Inspect canonical parsing and validation paths before changes

When modifying publish-issue behavior, first examine the canonical PEG grammar, its generated-parser workflow, and every downstream consumer that validates or resolves parsed fields. Track exact title syntax, repository/path/version validation, CI checkout timing, and relevant tests so changes preserve the established contract. Pay particular attention to migration-related behavior: confirm obsolete legacy syntax has been removed, and ensure path/workspace resolution follows the documented full-path, CI-approved-revision flow.