Shkarko RigSmith 1.25.0

🚀 Enhancements
- rig: Add stack edge pack reconstruction and edge status for carried fixes under republished NuGet ids
Reconstruct the committed manifest and fork integration snapshot, record explicit pack outcomes and provenance, and keep dry-run conflicts read-only. Canonicalize reconstruction and working-tree paths so NuGet retains project dependencies and original hooks chain reliably.
Preserve unrelated output files and directories during package cleanup, protect Git metadata paths, and reject non-edge members before fetching.
- rig: Add stack edge ci with credential-free build reports and an independent NuGet HTTP publisher that proves ids, versions, fork ancestry, package hashes and monotonicity; tip publishing requires explicit opt-in. Third-party dependency and assembly-name expectations remain build-job claims. Include a two-job workflow and security regression coverage.
Require the same trusted run number in both CI jobs to prevent inflated-version reports. Permit non-empty packed subsets of the publisher’s text-only allowed ids, and use independently discovered NuGet sibling ids for cross-member checks. Protect the publish workflow with a default-branch-only edge-publish environment and environment-scoped secret.
Stream report-job build and test diagnostics to stderr and preserve subprocess failure errors without putting output in report files.
Keep short feed-read timeouts separate from package uploads. Bound pushes with a 15-minute context deadline and two-minute response-header timeout, and explain how to check for a package that may have been stored after a timeout.
Render the GitHub run-number expression literally in the stack documentation so Vue does not evaluate it during the documentation build.
Keep CI-only commands out of the interactive edge menu; prompt for member and PR inputs when choosing pack or adopt.
- rig: Add the read-only stack edge manifest block with publishing prerequisites, adopted PR validation and a default 100 MB package limit, plus pure edge version and monotonicity helpers.
- rig: Expose edge init and stack doctor --edge with confirmed root workflow publication, default-branch-only publishing environments and environment secrets. Warn on moved adopted PRs in CI reports and cancel edge member prompts cleanly.
- rig: Adopt upstream PRs targeting the member's tracked branch as import-rooted, member-scoped edge topics without manifest edits or pushes, and warn when adopted PR heads move beyond their pins.
- rig: Return stack consumers from republished package ids to public releases with all-or-nothing sibling checks. Include tracked and non-ignored projects under packages, generated and vendor directories in release edits and all-or-nothing checks.
- rig: Watch NuGet stack releases with read-only reports and an independently verified publisher that opens or updates back-to-packages PRs. Add a scheduled two-job workflow example with trusted pinned rig installs, branch reuse, hand-migration no-ops and permission guidance. Local apply keeps interactive clean-tree confirmation. npm and deeper transitive delivery remain unsupported.
Preserve unchanged PR heads, refuse wrong-base PR reuse, escape branch API paths, and fail scheduled publication on read or transient API errors while reporting write denials. Keep report stdout clean and replace reports through a temporary file, preserving old readers and existing contents when preparation fails. Unix reports use 0600; Windows report privacy depends on directory ACLs.
- rig: Guard topic proposals against missing integration ancestry and add stack propose --track-only to refresh trackBranch safely after pull
🩹 Fixes
- shiprig: Exclude packages under testdata path segments from changerig and shiprig release discovery so test fixtures cannot block releases.
📖 Documentation
- rig: Use the published rigsmith/stack-action v1.0.0 pinned by full commit SHA in stack CI documentation and examples; document the action release sync checklist.