Make gods-eye-view run here #1

Make gods-eye-view run here

gods-eye-view was migrated to this forge from https://github.com/bilawalsidhu/gods-eye-view — every branch and tag, its history intact. It is someone else's project. Make it run here as an app without changing what it does.

The app is on the branch main — the source's default branch, and the default branch here. Start from main and open your pull against it; the other branches are history, not the app.

Adapt, don't rewrite:

• Read before you write: the language, how it starts today, how it reads its port and configuration, where it keeps state, how it installs and tests.
• Declare it in forge.json at the root, under app: run (the command that starts it) and health (a path that answers once it is up); install and test when the repository has them.
• Listen on the port in PORT, on HOST. A hard-coded port becomes the fallback, not the rule.
• Keep every piece of persistent state — a SQLite file, uploads, a data folder — under FORGE_APP_DATA. It must start on an empty one and restart on a full one.
• The forge runs processes, not containers: no Dockerfile, no compose file. Read those only to learn what the app needs. A second service it cannot do without (a database server, a queue) becomes the app's embedded or file mode where it has one.
• Its data: if it used a database server elsewhere (Postgres, MySQL), say in the pull where the rows are and what it uses now. Leave the old database untouched. Move the app's state under FORGE_APP_DATA (bun:sqlite, or the app's embedded mode). When rows exist, ship a one-shot import script (dump file in, FORGE_APP_DATA out) that a person runs on purpose, and say how to make the dump. Never commit or read at boot a connection string to the old database.
• Keep its routes, pages and behaviour as they were. The smallest diff a person can review quickly — no refactors, no restyling, no dependency churn beyond what running here needs.
• Write down what could not fit — a service the forge cannot run, a secret you do not have — plainly, in the pull, so a person can decide. An honest blocker beats a broken deploy.

Done means the pull's preview starts, answers its health path, and does what the original did.

Parked by the crew: the run ended without a pull: This repository has no model account: ask an admin to grant one

Parked by the crew: the run ended without a pull: This repository has no model account: ask an admin to grant one

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the run ended without a pull: This repository has no model account: ask an admin to grant one
2. the run ended without a pull: This repository has no model account: ask an admin to grant one

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Owner's go (via the steward, 2026-10-21): deploy this for a friend, cheaply. The earlier parks were "no model account" (fixed - open-router is granted to quill) - strikes reset. Follow the repo's direction: forge.json app block, PUPPETEER_SKIP_DOWNLOAD=1, no paid keys, never the dev-*.sh scripts. Done = the app answers at its forge URL showing the globe with the free feeds.

Parked by the crew: the run ended without a pull: This repository has no model account: ask an admin to grant one

Parked by the crew: the run ended without a pull: This repository has no model account: ask an admin to grant one

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the run ended without a pull: This repository has no model account: ask an admin to grant one
2. the run ended without a pull: This repository has no model account: ask an admin to grant one

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.