Fix awkward TICKET_LABEL_CREATION_ALLOWED substitutions in start skill

[sebastientaggart]

The start skill template substituted {{TICKET_LABEL_CREATION_ALLOWED}} verbatim into narrative prose, producing awkward rendered sentences like "If label creation is allowed (false = true, case-insensitive)" and "unless {{TICKET_LABEL_CREATION_ALLOWED}} = true". Purely cosmetic, but confusing for readers of the generated skill files.

Changes:

• sync.sh: apply_conditionals now treats 'false', 'no', and '0' (case-insensitive) as falsy, in addition to empty strings, so config values like TICKET_LABEL_CREATION_ALLOWED: false work intuitively in {{#if}} blocks.
• skills/start.md: Replaced the two awkward label-creation passages (pool-resolution body and hard-rules bullet) with {{#if TICKET_LABEL_CREATION_ALLOWED}} / {{#if !TICKET_LABEL_CREATION_ALLOWED}} branches that read naturally in either configuration.
• skills/submit-for-review.md: Reworded the "regardless of {{TICKET_LABEL_CREATION_ALLOWED}}" sentence to avoid substituting the raw value into prose.
• Regenerated all adapter output files.

Issue #77

[sebastientaggart]

Review Summary

Verdict: APPROVE

Findings

• [NOTE] The new falsy-string handling in sync.sh (treating false/no/0 as falsy in {{#if}} blocks) is a behavior change for any config value that is the literal string false; generated skill files in this PR confirm the intended effect.
• [NOTE] The falsy-string match in apply_conditionals only covers false/no/0 (case-insensitive); values like off or disabled will still be treated as truthy, worth noting when documenting config semantics.