Topolo BugFix
Bug analysis and issue-resolution tooling inside the Topolo portfolio.
Documentation Map
What It Is
Bug analysis and issue-resolution tooling inside the Topolo portfolio.
AI-powered bug fix automation service for all Topolo applications. Users report bugs, AI agents analyze and generate fixes, and PRs are automatically created for review.
The only public flow explicitly proved on 2026-03-23 is:
1. `POST /api/reports` 2. `GET /api/reports/:id/status`
Architecture
Owners: ai-platform
Source repos: Applications/TopoloBugFix
Dependencies: topolo-auth
Repo shape
- Applications/TopoloBugFix/README.md
- Applications/TopoloBugFix/deploy.sh
- Applications/TopoloBugFix/docs/
- Applications/TopoloBugFix/package.json
- Applications/TopoloBugFix/scripts/
- Applications/TopoloBugFix/src/
- Applications/TopoloBugFix/wrangler.toml
Runtime Surfaces
Hosts:
No primary host is registered.
Config: Applications/TopoloBugFix/wrangler.toml
Main: src/index.js
Routes: bugfix-staging.topolo.app, bugfix.topolo.app
API Reference
Coverage: curated
Source: Applications/TopoloBugFix
Source exists in repo: yes
Application exists in repo but has no registered OpenAPI spec in the current audit.
App API page: /reference/apps/topolo-bugfix
This system currently relies on a curated or README-derived contract surface instead of a source-controlled OpenAPI spec.
Auth and Permissions
Depends on Topolo Auth: yes
Service IDs:
No Auth service ID mapped in docs yet.
API key scopes
No API key scopes were found in the checked-in Auth catalog for this system.
Service permissions
No role/permission catalog rows were found in the checked-in Auth permissions seed.
Data Ownership
Binding: DB
Target: 1f992a7b-2ea9-4fa5-bcad-f057a67e3235
Environment: default
Source: Applications/TopoloBugFix/wrangler.toml
Binding: DB
Target: a2f8cb8a-0b65-4df9-9018-3b2642f06afe
Environment: production
Source: Applications/TopoloBugFix/wrangler.toml
Queues / Cron / Workflows
Queue bindings:
No queue bindings were detected.
Cron triggers
No cron triggers were detected.
Workflow signals
No explicit queue/workflow script or cron signal was discovered.
Environment Variables and Bindings
Environment variables:
AUTH_URL ENVIRONMENT GITHUB_API_URL GITHUB_REPO_OWNER All wrangler bindings
-
DB(d1) -> 1f992a7b-2ea9-4fa5-bcad-f057a67e3235 -
DB(d1) -> a2f8cb8a-0b65-4df9-9018-3b2642f06afe [production]
Deployments
Deployment environments: production
Routes: bugfix-staging.topolo.app, bugfix.topolo.app
Observability enabled: no explicit setting found
Wrangler surfaces
- Applications/TopoloBugFix/wrangler.toml -> topolo-bugfix-staging
Build and deploy commands
-
deploy— Applications/TopoloBugFix/package.json :: wrangler deploy -
deploy:staging— Applications/TopoloBugFix/package.json :: wrangler deploy -
deploy:prod— Applications/TopoloBugFix/package.json :: wrangler deploy --env production
Failure Modes
- No Auth service ID is registered for this system.
- No primary host is registered in the system registry.
Debugging Runbooks
Start with these entrypoints:
- Applications/TopoloBugFix/wrangler.toml
- Applications/TopoloBugFix
- Applications/TopoloBugFix/README.md
- Applications/TopoloBugFix/package.json
Change Log / Verification
Lifecycle: active
Last verified: 2026-03-29
Any code change to this system is expected to update the canonical docs in Websites/docs and refresh the verification date.