/nxs.analyze runs per story from the hub against a member PR

[sameera]

/nxs.analyze runs per story from the hub against a member PR: pr-worktree is parameterized by member repo (the member-unsupported gate is deleted), conformance checks the story's ACs and the decision record's invariants at the PR head, the verdict posts as a PR review, and analyze-record.<story id>.md (story ID, PR number, analyzed head SHA, verdict) is committed into the hub entry.

Meta

• feature: docs/features/multi-repo-workspaces
• estimate: M
• candidate stories: pr-worktree targets a declared member repo; Per-story conformance against ACs and record invariants; analyze-record file committed to the hub entry
• source: decomposition of "Refactor multi-repo workspaces around PR-driven delivery (hub-born queue)" (2026-07-20)
• migrated: 2026-08-01, from the per-feature backlog file retired by Backlog Stubs Become GitHub Issues #185

Notes

note (2026-07-21): #114 (issue-sourced planning) makes the committed queue entry born at close, so there is no planning-time hub entry for a per-story analyze-record.<story id>.md to land in before close. The PR-review verdict is unaffected; the committed-record home must be reconsidered at promotion (aggregate at born-at-close, or carry it in the PR-review machine block).

note (2026-07-27): the nxs.pr block this stub hard-failed on no longer exists — the command is cancelled. Per-story analyze reads the engineer's committed scratch from the member checkout, and that read is soft: absent scratch changes no verdict, so there is nothing here to hard-fail on. The scratch/record work (#157) therefore drops out of blocked_by; it is preferred-first, not required, since it is what makes the scratch this stub reads non-empty.

dependency rewritten at migration (2026-08-01): this stub was recorded as blocked by hub-born-queue, which was superseded before implementation by issue-sourced planning (#114). The edge points at #114.