chore: replace legacy autogame-17 handles with EvoMap/evolver

[shaun0927]

Problem

Five locations in the repository still reference the legacy
personal-account handle autogame-17:

src/gep/issueReporter.js:14    DEFAULT_REPO = 'autogame-17/capability-evolver'
src/gep/skillPublisher.js:162  https://github.com/autogame-17/evolver
index.js:740                   https://github.com/autogame-17/evolver/issues
README.md:301                  | EVOLVER_ISSUE_REPO | autogame-17/capability-evolver | ... |
README.zh-CN.md:293            | EVOLVER_ISSUE_REPO | autogame-17/capability-evolver | ... |

GitHub currently 301-redirects autogame-17/capability-evolver and
autogame-17/evolver to EvoMap/evolver, so paths resolve today.
They depend on a GitHub redirect pinned to a personal-user account
(autogame-17).

See #408 for the full rationale.

Fix

Replace all five occurrences with EvoMap/evolver, the current org
slug where the issue tracker already lives.

Why this direction

• EvoMap/evolver is where release publishing happens
  (gh release list shows all three releases authored into this org).
• The issue tracker that every auto-report target resolves to is also
  EvoMap/evolver (issues [Auto] Recurring failure: Repeated failures with gene: gene_gep_repair_from_errors #395 – docs(SKILL): network allow-list missing evomap.ai used by privacyClient, taskReceiver, and skillPublisher #411 are filed there).
• Removing the redirect dependency eliminates a repo-jacking surface
  without requiring any behaviour change: the endpoints used at
  runtime are identical after the redirect.

If the project needs to keep the legacy name for some external
reason (e.g., existing indexers, older release URLs), the only entry
that materially matters for behaviour is the DEFAULT_REPO literal
in issueReporter.js. I can narrow the PR to just that line on
request.

Testing

No runtime behaviour change. The module's HTTP targets resolve to
the same repository before and after the patch:

$ node -e \"const r=require('./src/gep/issueReporter'); console.log(r)\"
{ maybeReportIssue: [Function: maybeReportIssue], ... }

$ node test/issueReporter.test.js
issueReporter.test.js: OK

Scope

Five files, +5/−5 lines.

Closes #408.

[autogame-17]

Thank you for the contribution, @shaun0927. As noted in SECURITY.md and our previous triage on related PRs, EvoMap/evolver is a generated distribution mirror of an internal maintainer branch and cannot accept code PRs directly -- the public tarball carries the release integrity signature that only our release pipeline can produce correctly against the internal maintainer branch.

This specific change has been recorded and will be hand-ported into the internal maintainer branch ahead of the next release, with credit to you. Closing this PR accordingly; the underlying issue will be closed or referenced when the port lands.

If you have more suggestions we welcome them as issues (not PRs) so we can triage without creating merge-path confusion.