Skip to content

docs: move PR ready and landing guidance into ship-landing skill - #73

Merged
jazz127 merged 2 commits into
housefeature/evidence-boundary-coveragefrom
fm/evidence-boundary-coverage-r2
Sep 27, 2026
Merged

jazz127 merged 2 commits into
housefeature/evidence-boundary-coveragefrom
fm/evidence-boundary-coverage-r2

Conversation

@jazz127

@jazz127 jazz127 commented Sep 27, 2026 •

Copy link
Copy Markdown
Owner

Purpose

Move the PR reporting-boundary evidence instructions into upstream's ship-landing skill through housefeature/evidence-boundary-coverage.

Change

  • Replace the old AGENTS.md PR ready/landing block with the upstream ship-landing pointer.
  • Put this feature's published-body read-back, evidence-validation=failed, and publication-scope rules into the skill.
  • Register the skill in the documentation audience inventory. The review fix updates two documentation links that pointed to the old AGENTS.md location.

This durable branch is house-based and is not a clean upstream contribution candidate. Review also noted preexisting URL parsing behavior and a helper naming concern in runtime code; this instruction relocation does not change that code.

Validation

Synthetic/offline built-CLI validation: no-mistakes review, test, document, and lint stages completed. The pipeline's local probes are not external account confirmation. CI was skipped because this feature base has no matching check workflow.

Merge order

The upstream skill-layout PR #67 has merged. Merge this PR into housefeature/evidence-boundary-coverage first. Then open the house-based integration merge PR, preserving current house rules where the older durable branch conflicts. Use merge commits.

evidence-artifact: /tmp/fm-firstmate-upstream-5872-merge-r1/pr73-evidence.txt
evidence-command: no-mistakes axi status
evidence-captured: 2026-09-27T10:34:04Z

Pipeline attestation

@jazz127
jazz127 merged commit 3f0b421 into housefeature/evidence-boundary-coverage Sep 27, 2026
@jazz127
jazz127 deleted the fm/evidence-boundary-coverage-r2 branch September 28, 2026 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant