fix(server): seed goose-native-ui and hermes-native-ui default agents

[PattaraS]

Summary

_ensure_default_agents in server/app.py seeds the built-in <harness>-native-ui
agents at server startup (this is what populates GET /v1/agents and what any
head resolving a native agent by name relies on). It seeded 9 of the 11
native-ui agents declared in the harness registry
(harness_plugins.native_agents): goose-native-ui and hermes-native-ui
were added to the registry (full NativeCodingAgent records + _materialize_* _agent_spec functions) but their startup seeders were never wired in.

Result: those two agents never appear in GET /v1/agents, so anything looking
them up fails with 'goose-native-ui'/'hermes-native-ui' not auto-registered on the server — which is how the harness capability bench surfaced this.

Change

Add the two missing seeder pairs (_build_goose_native_bundle /
_ensure_default_goose_agent, and the hermes equivalents), mirroring the
existing kiro pattern exactly, and call them from _ensure_default_agents. No
new mechanism — just the wiring that was omitted when goose/hermes were added
to the registry.

Test Plan

• pytest tests/test_native_coding_agents.py -> 7 passed.
• Live (harness bench, native-tui): before this change goose/hermes fail at
  not auto-registered; after, both get PAST registration and reach terminal
  provisioning (where each hits a separate downstream issue — hermes a
  lazy-chat/first-turn gate, goose a terminal-ensure 500 — both tracked
  separately, not caused by this change).
• ruff check clean.

Demo

N/A -- server startup agent seeding.

Type of change

• Bug fix
• New feature
• Documentation

Test coverage

• Automated tests added/updated
• Manual verification completed

Coverage notes

The seeding is covered by tests/test_native_coding_agents.py (agent-name
contract). The end-to-end "goose/hermes register on a live server" path needs
the native-tui bench with logged-in vendor CLIs, which CI lacks, so it was
verified by hand.

Follow-up (not this PR)

The per-harness hardcoded seeder list in _ensure_default_agents is the root
seam: a native harness — in-repo or a community plugin — is invisible until
someone hand-adds a seeder here, even though native_agents() already
enumerates them (plugins included). Making _ensure_default_agents iterate
native_agents() instead of 13 hardcoded calls would make native harnesses
(and plugins) register automatically. Filed as a follow-up rather than folded
in here to keep this a minimal, obvious fix.

[PattaraS]

/review

[omnigent-ci]

Polly AI Review

Summary

This is a minimal, correct, low-risk fix. It adds the two missing startup seeders (_build_goose_native_bundle / _ensure_default_goose_agent and the hermes pair) and wires them into _ensure_default_agents, mirroring the existing kiro pattern exactly. I verified against the checked-out main: the imports resolve (GOOSE_NATIVE_CODING_AGENT / HERMES_NATIVE_CODING_AGENT exist in harness_plugins.py), the materialize functions exist with matching signatures (_materialize_goose_agent_spec(tmpdir) and _materialize_hermes_agent_spec(tmpdir) both take only tmpdir — correctly called without the model=None arg that kiro uses), and _tar_gz_dir / _ensure_builtin_agent are the same helpers the sibling seeders use. Approve.

Blocking issues

None.

Security vulnerabilities

None. No new dependencies, no changed lockfile pins, no extras, no new network/auth surface — purely additive server-startup seeding of already-declared built-in agents.

Non-blocking notes

• The PR description already calls out the real design smell: _ensure_default_agents hardcodes one seeder call per harness, so any native harness is invisible until someone hand-adds a pair here even though native_agents() enumerates them. Filing the registry-driven iteration as a follow-up is the right call for keeping this PR minimal; worth landing soon so this class of omission stops recurring.
• The change adds no direct regression test asserting goose-native-ui / hermes-native-ui actually appear in GET /v1/agents after _ensure_default_agents runs. tests/test_native_coding_agents.py covers the name contract but not the seeding wiring itself (which is exactly what was missing here). A small test invoking _ensure_default_agents with a fake store and asserting both names get registered would guard against a future re-omission — optional given the follow-up above.

---

_{Automated review by Polly · workflow run}

[github-actions]

🏷️ Doc impact: needs-doc-update

Two new native coding-agent harnesses (goose-native-ui and hermes-native-ui) are registered as built-in default agents, adding user-facing integrations that require documentation.

Drafting a docs PR to omnigent-ai/omnigent-site (staged on 0.5-docs until release)…

_{Auto-classified on merge. Set the label manually before merging to override. · run}