Nexus integration: external-repository review context and quick-vote diagnostics need investigation

[williamzujkowski]

Nexus consensus review is unreliable for this consuming repository because voters repeatedly assume they are reviewing changes to the nexus-agents product itself.

Observed with producer version 8.49.3 on 2026-09-11, real (not simulated) quick-mode votes:

• job-vote-34703d7d-4e51-494a-be08-45bd4d096d11: 2 approve, 1 reject. Scope voter assumed the Nexus product mission and nonexistent existing templates.
• job-vote-e74237e8-7c84-4f61-8f3c-2efeb286fe71: corrected repository and explicit user task; all three roles approved, but overall no_quorum with policy reason contrarian check errored (absolute_quorum quick-mode) despite zero reported role errors.
• job-vote-c8202293-edad-49ce-a50d-82d273128baf: final implementation summary explicitly identified this personal Astro blog repository; all three voters rejected because they considered external-repository proposals outside the Nexus product scope. All three used gemini-3.1-pro-preview.

The proposal was static research instructions, a GitHub issue template, evidence notes and two policy documentation corrections, requested by the blog owner. It was not a request to insert blog documentation into nexus-agents. These votes therefore do not constitute a usable factual review of the target diff. They remain recorded as rejected/no-quorum, never approved.

Acceptance:

• Inspect consuming configuration and actual voter context to locate the source of the product-only mission assumption; do not assume whether config or upstream is at fault.
• Verify a bounded external-repository fixture receives review of its actual scope without disguising the repository identity.
• Investigate the quick-mode no-quorum diagnostic separately; retain fail-closed handling rather than reinterpret role totals as approval.
• Report reproducible upstream findings in the appropriate Nexus tracker if warranted and link them here.
• Until repaired, record the limitation and use completed independent source/diff reviews plus required checks under existing authorization. No retry loop until a favorable vote.

Additional confirmed wrong-repository rejection — 2026-09-11

Job job-vote-516414e8-317e-4c53-8874-6c8f0ed74973 completed at 2026-09-11T15:07:49.569Z, producer 8.49.3, quick mode with three voters, simple_majority, fail_closed. Actual result: 0 approve, 3 reject, 0 errors; no simulated votes.

The proposal explicitly named williamzujkowski/williamzujkowski.github.io as the target and stated that it contained no nexus-agents code changes. Nevertheless, all three roles framed their rejection as reviewers “for nexus-agents” and treated work on a personal Astro blog as outside that product's mission. They acknowledged the described QA and security controls while rejecting the wrong repository scope.

This reproduces the context failure on a subsequent real review. The result remains rejected, not approved or inconclusive; it cannot substitute for a review of the actual target repository. One further attempt with corrected context was planned while completing the PR, with the same requirement to retain its actual outcome and avoid retrying until a favorable vote.

Successful bounded context mitigation — 2026-09-11

The single corrected-context attempt, job-vote-4b5c91cb-69d8-4fae-8e08-8fe57018a4c3, completed at 2026-09-11T15:10:46.359Z, producer 8.49.3, and approved 3–0, with no errors or simulated votes. All three roles used gemini-3.1-pro-preview; this is role diversity, not independent model-family diversity.

The prompt explicitly bound the roles to the author-authorized current workspace, identified the previous confusion between the tool's repository and the consuming repository, and presented the same concrete changes without relaxing acceptance criteria.

This is evidence that explicit context repair worked for one bounded attempt. It is not a robust integration fix or proof that the underlying cause has been resolved. This issue remains open, and all preceding rejected/no-quorum outcomes remain part of the record.

[williamzujkowski]

Backlog grooming (2026-09-12): investigation, no repository change yet. Keep open until the external-repository context and quick-mode diagnostic are reproduced in the upstream tracker or clearly bounded as a known limitation.

[williamzujkowski]

Backlog review reproduced the Nexus context limitation: a correctly scoped consuming-repo triage vote was rejected 4–3 because several voters treated it as outside nexus-agents' own repository, while another similarly scoped vote approved 5–2. This remains evidence for #595, not a reliable decision on blog work. Independent repository review and explicit user authorization remain the source of truth here.

[williamzujkowski]

Improvement review (14-day window) found repeated MISALIGNED (6) and SCOPE_CREEP (5) consensus rejections, including this session's consuming-repository votes. Its automatic issue filing also failed because the configured p2/p3 labels do not exist. This strengthens #595's case for a target-repository context guardrail and label-safe fallback; no duplicate issue filed.

[williamzujkowski]

Reproduced on 2026-09-13 with producer 8.49.3, real quick-mode supermajority and fail_closed: job-vote-9ce46750-66ab-435e-a942-5ca97f82501b completed at 05:06:11.668Z with 0 approve, 3 reject, 0 errors. All three roles used gemini-3.1-pro-preview.

The proposal explicitly named the consuming Astro blog repository, its owner's authorized backlog work, and separate fixes for #615 (safe YAML parsing) and #620 (published DoH corrections). Every rejection said the reviewers' mandate was the nexus-agents product and external repository work was outside scope. The security reviewer acknowledged the security controls and test plan while rejecting that wrong scope.

This result remains rejected. No favorable-result retry is being used. Work proceeds under the owner's existing authorization and this issue's documented independent-review/required-CI fallback. Upstream investigation remains linked at nexus-substrate/nexus-agents#6107.