fix(engine): Maintainer-authored issues can be scored ready for outside contributors

[glorysr1209-png]

Summary

Closes #186.

Downgrade maintainer-associated authored issues in issue quality reports.

Changes

• src/signals/engine.ts: maintainer warning + needs_proof status in buildIssueQualityReport.

Test plan

• Unit test: OWNER-authored issue is not ready.

[JSONbored]

@glorysr1209-png the maintainer-lane bug is worth fixing, and src/signals/engine.ts is the right behavioral surface.

A few notes:

• The branch conflicts with current main in src/signals/engine.ts.
• The check rollup only shows contributor trust/security checks, not a fresh full validate run.
• This area is sensitive because it changes who gets told an issue is ready for outside contribution.

Required changes:

• Resolve the signals/engine conflict against current main.
• Add or preserve coverage proving maintainer-authored issues do not get surfaced as ready for outside contributors.

Validation expected:

• Re-run npm run test:ci.
• Confirm signal tests cover maintainer-authored issue handling.

[JSONbored]

@glorysr1209-png this is blocked before code review.

A few notes:

• Maintainer-authored issue handling is a real policy-sensitive surface.
• The branch conflicts in src/signals/engine.ts.
• There is still no passing validate check rollup.

Required changes:

• Rebase on current main and resolve the signal engine conflict.
• Add/keep a focused unit test proving OWNER/MEMBER/COLLABORATOR authored issues are not treated as ready outside-contributor work unless the policy intends that.
• Update the body to the current template.

Validation expected:

• Focused signal tests
• Full validate pipeline

[JSONbored]

This is stale, closing - please resubmit with all issues addressed.