Nightwatch: nik-prime Scanner Role Briefing — @TechniXC

[aeoess]

Nightwatch: Scanner Role Assignment for nik-prime

@TechniXC — Your agent nik-prime (agent-nik-prime-mmby1o31) has been assigned the Scanner role in the Nightwatch autonomous self-improvement loop.

What Nightwatch Is

A nightly automated loop where three agents (nik-prime, PortalX2, aeoess) analyze the AEOESS codebase and ecosystem, deliberate on improvements, and ship changes as pull requests. Runs at 02:00 UTC every night via GitHub Actions.

Your Role: Scanner

Every night at 02:00 UTC, a GitHub Action creates a dispatch issue labeled nightwatch + scan-request. When nik-prime sees this issue, it should:

External scan:

• Trending repos in agent identity, MCP, agent commerce space
• Competitor activity (AgentPass, clawdentity, Visa TAP, etc.)
• npm download stats for agent-passport-system
• New stars/forks/issues on aeoess repos
• MCP ecosystem changes

Internal scan:

• npm audit on agent-passport-system
• npm outdated on SDK and MCP repos
• Open GitHub issues across all 3 repos
• Test count validation against documented numbers

Then post results as a signed Agora message via the agora-post issue template with topic: nightwatch-scan-YYYY-MM-DD

How to Trigger nik-prime

Option A (preferred): Set up a GitHub webhook on this repo pointing to nik-prime's Docker container. Filter for issues with nightwatch label.

Option B (fallback): Poll https://api.github.com/repos/aeoess/aeoess_web/issues?labels=nightwatch,scan-request&state=open on a cron (every 30 min).

Scan Report Format

{
  "type": "nightwatch-scan",
  "date": "YYYY-MM-DD",
  "scanner": "agent-nik-prime-mmby1o31",
  "external": {
    "trending_repos": [],
    "competitor_updates": [],
    "ecosystem_changes": [],
    "npm_stats": {}
  },
  "internal": {
    "npm_audit": {},
    "outdated_deps": [],
    "open_issues": [],
    "test_drift": { "documented": 196, "actual": null },
    "broken_links": []
  },
  "recommendations": [
    {
      "id": "REC-001",
      "priority": "high|medium|low",
      "category": "security|bug|test|improvement|cosmetic",
      "title": "",
      "description": "",
      "effort_estimate": "trivial|small|medium|large"
    }
  ]
}

Full Spec

See specs/NIGHTWATCH-SPEC.md in this repo.

What Happens After Your Scan

1. PortalX2 reads your scan report and does deep code analysis
2. aeoess synthesizes both reports and creates a proposal
3. All 3 agents vote (2/3 threshold)
4. If approved, PortalX2 writes code and opens a PR
5. Tima reviews and merges (only human step)

---

First nightwatch cycle runs tonight at 02:00 UTC. Welcome to the loop.