Ask Jev AGENTS.md changelog

https://raw.githubusercontent.com/pollinations/pollinations/HEAD/AGENTS.md

− - `operations/` — Internal dashboards, monitoring, economics, and infrastructure− - `operations/social/` — Discord/Reddit/GitHub automation− - Auth: `pk_` (frontend), `sk_` (backend). Keys: https://enter.pollinations.ai/keys− - `operations/economics/web` local development must read Tinybird staging−   `operations/economics/secrets/web.dev.json`.−   `operations/economics/secrets/web.json`. Never decrypt that production file− A bot sets the Dev project Area on every new issue and PR, plus the issue type and Priority on issues, following `operations/github/project-manager.md`. That file is the one definition of areas, types and priorities; read it before classifying work by hand. Labels are only for workflows (`APP-*`, `BEE-CENSUS`, `HONEY-CENSUS`, `POLLI`, `NEWS`, `POLLEN-QUEST`/`DRAFT-QUEST`, `VOTING`, `MERGE-HOLD`) and goals (`REVENUE`); don't repurpose them or create new labels ad hoc.+ - `operations/` — Internal dashboards, monitoring, data sync, news, app management and infrastructure; folder map in `operations/README.md`+ - `operations/news/` — News pipeline: daily, weekly and monthly posts, per-PR Discord posts and the News page data+ - Auth: `sk_` keys authenticate requests; `pk_` App Keys only identify an app (OAuth `client_id`) and get `401` as a key. Keys: https://enter.pollinations.ai/keys+ - `operations/dashboards/economics/web` local development must read Tinybird staging+   `operations/dashboards/economics/secrets/web.dev.json`.+   `operations/dashboards/economics/secrets/web.json`. Never decrypt that production file+ A bot sets the Dev project Area on every new issue and PR, plus the issue type and Priority on issues, following `operations/infrastructure/project-manager/project-manager.md`. That file is the one definition of areas, types and priorities; read it before classifying work by hand. Labels are only for workflows (`APP-*`, `BEE-CENSUS`, `HONEY-CENSUS`, `POLLI`, `NEWS`, `POLLEN-QUEST`/`DRAFT-QUEST`, `VOTING`, `MERGE-HOLD`, and the reward labels `reward-1`, `reward-3`, `reward-5`, `reward-10`, `rewar

https://raw.githubusercontent.com/pollinations/pollinations/HEAD/AGENTS.md

− ### Design Questions− - Before committing to a design, surface unresolved choices that could materially change the user outcome, scope, UX, constraints, or architecture. Ask even when the request is executable if the answer could improve it.− - Investigate facts available in the codebase or documentation yourself. Ask the user about intent and tradeoffs. Prefer one consequential question at a time; group up to three only when their answers are independent. Give a recommendation and its tradeoff, while allowing another answer.− - Use each answer to revise the design and subsequent questions. Stop when consequential choices are settled; handle routine, reversible details autonomously. Briefly reflect the resulting design before building.− - Avoid repeating answered questions or asking for permission already given. Existing safety approval requirements still apply.+ - Skills from other repos (`grill-me`, `grilling`) stay unedited and pinned in+   `skills-lock.json`; refresh them with `npx -y skills@1.7.2 add+   mattpocock/skills --skill grill-me --skill grilling --agent claude-code --copy -y`.+ ### Grill Plans Before Building+ - Use the `grilling` skill often (`.claude/skills/grilling/`; users start it with `/grill-me`). Grill every non-trivial feature, design, API or pricing change, quest, and any plan with open choices, even when the request already looks executable.+ - Look facts up yourself in the code, docs, issues and PRs; ask the user only about intent and tradeoffs. Ask every question that is unblocked now in one numbered round, each with your recommended answer, then let the answers shape the next round.+ - Keep working on parts that don't depend on the answers. Decide routine, reversible details yourself, and briefly restate the settled design before building.+ - Don't repeat answered questions or ask for permission already given. Existing approval and safety rules still apply.

https://raw.githubusercontent.com/pollinations/pollinations/HEAD/AGENTS.md

− Guild ID `885844321461485618` (https://discord.gg/pollinations-ai-885844321461485618) — use for Discord MCP tools.− - Run `npx biome check --write <file>` after edits and before commits.− A bot sets the Dev project Area on every new issue and PR, plus the issue type and Priority on issues, following `operations/github/project-manager.md`. That file is the one definition of areas, types and priorities; read it before classifying work by hand. Labels are only for workflows (`APP-*`, `BEE-CENSUS`, `HONEY-CENSUS`, `POLLI`, `NEWS`, `POLLEN-QUEST`/`DRAFT-QUEST`, `VOTING`) and goals (`REVENUE`); don't repurpose them or create new labels ad hoc.+ Guild ID `885844321461485618` (https://discord.gg/k9F7SyTgqn) — use for Discord MCP tools.+ - Run `npx @biomejs/biome check --write <file>` after edits and before commits. It runs the repo's own Biome once `npm ci` has installed it; a bare `npx biome` can run an unrelated npm package.+ ## Data-processing documentation maintenance+ - Update the public provider inventory or Privacy Policy and its Last updated date when a change makes their statements inaccurate. Keep routing details, evidence and unresolved provider reviews in the relevant PR or issue. Update the internal DPA only when its proposed terms, annexes or publication blockers change; keep it outside website assets and navigation until approved.+ - Verify affected recipients, locations, data use, retention, processing terms and transfer safeguards from operational and contractual evidence. Record unknowns; do not present them as verified. A model name, hostname or provider headquarters does not establish where processing occurs.+ - Check applicable contract and notice requirements before recipient changes or other material processing changes take effect. Editing a provider list is not customer notice. Obtain operator/legal review before changing contractual commitments; escalate urgent exceptions to the maintainer.+ - For support email, use `.claude/skills/pollinations-support-triage/SKILL.md`.+ A bot sets the Dev project Area on every new issue and PR, plus the issue type and Priority on issues, following `operations/github/project-manager.md`. That file is the one definition of areas, types and priorities; read it before classifying work by hand. Labels are only for workflows (`APP-*`, `BEE-CENSUS`, `HONEY-CENSUS`, `POLLI`, `NEWS`, `POLLEN-QUEST`/`DRAFT-QUEST`, `VOTING`, `MERGE-HOLD`) and goals (`REVENUE`); don't repurpose them or create new labels ad hoc.

https://raw.githubusercontent.com/pollinations/pollinations/HEAD/AGENTS.md

− Catalog fields are defined in `operations/app-management/app.js`; categories and platform detection in `operations/app-management/ingestion/submission.js`. After manual catalog edits, run `node operations/app-management/app.js validate`.− - Encrypted secret-file changes must use a dedicated PR. Never bundle them into a model, feature, pricing, or refactor PR.+ New submissions must credit Pollinations with the badge (`packages/ui/src/brand/badge-made-with.svg`) in the README, or on the app page when there is no repository, and upload a 16:9 screenshot (PNG/JPEG/WebP, ≤5 MB, ≥1280×720). Publishing converts it to WebP 1280×720 on `media.pollinations.ai` and sets `screenshotUrl`.+ Catalog fields are defined in `operations/app-management/app.js`; categories and platforms in `operations/app-management/ingestion/submission.js`. After manual catalog edits, run `node operations/app-management/app.js validate`.+ - Maintain project skills in `.claude/skills/`. Expose them to Codex through+   relative directory links in `.agents/skills/`; keep command adapters as+   pointers to their maintained instructions, never copied workflows.+ - `packages/sdk`, `packages/ui` and `packages/polli-cli` publish to npm from `main` only when their `version` changes; CI skips a version already on npm. A PR that changes what one of them ships bumps that version (prereleases take the next number on the same tag, e.g. `5.1.0-alpha.8`), including the package's own `package-lock.json` where it has one. SDK changes also get a `CHANGELOG.md` entry.