V0.11.2/service update

[gimlichael]

This pull request enables git-remote-pr to publish clean feature branches without upstream tracking and expands the release-note workflows for versioned changelogs and complete NuGet package coverage. It also updates repository guidance and aligns deterministic validation specifications with these behaviors.

First-publication PR workflow:

• Plans publication to origin or the sole GitHub remote using the current branch name, then establishes upstream tracking as part of the approved push.
• Verifies the published branch and tracking before writing PR metadata, while rejecting ambiguous remotes and incomplete or mismatched tracking.

Versioned changelog behavior:

• Gives yolo and auto the same concrete-version behavior, removes [Unreleased] only when its contents can be reconciled, and stops safely when the version or existing content is unresolved.
• Preserves ordinary [Unreleased] behavior and adds regression specifications for both autonomy modes and their boundaries.

Complete NuGet release coverage:

• Resolves the full branch delta against the integration branch by default, independent of same-named tracking branches, while preserving explicit range selection.
• Requires a complete version and availability block for every selected packable project, including unchanged packages with the defined default ALM entry.

Repository release guidance:

• Records the 0.11.2 release outcome and keeps the repository skill catalog aligned with the updated release-note workflows.

Contract validation:

• Extends deterministic checks to cover the updated skill contracts and package coverage requirements.

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Updates skill documentation, test suites, and validation workflows.

The PR appears safe to merge on the new changes reviewed, although the existing lone-flag validation finding remains outstanding.

Findings

1.  Incomplete flag passes validation ▶

Fix with agent prompt

### Issue 1
skills/git-visual-commits/scripts/validate-commit-subject.ps1:54-55
A subject such as `🇩 update budget` passes because the lone regional indicator falls within the bundled emoji range and counts as one grapheme. But it is not a complete flag emoji. This lets an invalid emoji-first subject through the validator.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The PR enables first-time PR publication from branches without upstream tracking, revises changelog and NuGet release-note guidance, broadens emoji selection, and separates PR workflow validation into its own suite.

• Publication plans now bind upstream setup to the approved push and verify tracking before PR metadata writes.
• Release-note guidance covers versioned changelogs and all selected packable projects, including unchanged ones.
• Deterministic tests and repository guidance reflect the revised workflows.

_{Reviews (5) · Last reviewed commit: "✅ stabilize progress coalescing regressi..."}

[greptile-apps]

Incomplete flag passes validation A subject such as 🇩 update budget passes because the lone regional indicator falls within the bundled emoji range and counts as one grapheme. But it is not a complete flag emoji. This lets an invalid emoji-first subject through the validator.

Prompt To Fix With AI

This is a comment left during a code review.
Path: skills/git-visual-commits/scripts/validate-commit-subject.ps1
Line: 54-55

Comment:
**Incomplete flag passes validation** A subject such as `🇩 update budget` passes because the lone regional indicator falls within the bundled emoji range and counts as one grapheme. But it is not a complete flag emoji. This lets an invalid emoji-first subject through the validator.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.