apps/api/src · flagon-io/g1t

archives.rsMerge GitHub pull request #8 (claude/cool-newton-7nm8r9): Docker deployments on g1t.page behind a switch that stays off until Cloudflare's container APIs are checked live, workflows a workspace manages in its repositories, tarball and zipball downloads, refs/pull/* kept to g1t alone, framework detection for g1t.page builds, and a workflow's event payload matching GitHub's.2d ago

audit.rsMerge workspace aliases through Actions and tokens: uses: g1t/deploy@v1 resolves to flagon-io/deploy, a token scoped to a repository reaches it under the alias, a g1t/ action is never taken from GitHub, and the Actions release creates g1t's action repositories when they are missing.2d ago

billing.rsThe contracts no longer describe g1t's own agents, and workspaces can keep their AI providers. Every consumer had already stopped using them, so the TypeScript and Rust contracts drop the workspace-agent, ability, look, skill-library, context, runner-agent and mention modules, the chat and docs RPCs agents posted and read through, the folio agent methods, the agent_waiting notification, agent.asked and memory.changed events, AI credit, token and gateway billing types, model routes and sessions, team agents, agent tokens, plan, review, message and confidence types, command rules, cost caps and confidence rules. The agents:run and models:* scopes are no longer offered by any preset, OAuth default or permission form, but a stored token or grant that names them still reads; and the removed operations are gone from the scope table, so the API's check that every operation has exactly one scope is strict again. What stored data needs in order to parse (old run and credential kinds, an agent team lead, retired rules and webhook events, old guardrail and integration settings) still parses, and a run's token is still PrincipalKind::Agent, which now means a run's token and the @g1t rows written before. The customize, marketplace, skills and claude-plugin contracts stay only until the mobile app drops its Customize screens.2d ago

blobs.rsThe artifacts service is services/artifacts, the Worker g1t-artifacts, bound as ARTIFACTS by the API, the site and the agents; its live rooms move to it with a Durable Object transfer from g1t-docs-service, and its database, bucket, indexes and queue keep their names. The git store's binding and settings are GITSTORE, its ops scripts gitstore-*, and workflow run artifacts keep their compatible API under run_artifacts modules. The deploy tool puts a Worker that has never deployed before the Workers in its stage that bind to it, and the deploy guide gives the cutover runbook.4d ago

broker.rsMerge branch 'main' into rm-agents2d ago

checks.rsMerge checks: statuses and check runs on every commit6d ago

deploy_keys.rsMerge branch 'worktree-agent-a5a5de74d8863d554' into worktree-agent-a16631325aecf58ca6d ago

deployments.rsMerge GitHub pull request #8 (claude/cool-newton-7nm8r9): Docker deployments on g1t.page behind a switch that stays off until Cloudflare's container APIs are checked live, workflows a workspace manages in its repositories, tarball and zipball downloads, refs/pull/* kept to g1t alone, framework detection for g1t.page builds, and a workflow's event payload matching GitHub's.2d ago

folios.rsThe API and MCP server no longer offer g1t's own agents. g1t is what your coding agents work against, not an agent of its own, so the operations that drove hosted agents are gone: messaging an agent on a pull request (message_agent, take_messages, answer_message), assigning or delegating an issue to g1t (assign_issue, delegate), plans (plan_work, get_plan, apply_plan), the context hub (search_context, get_entity), model routes, agents' computers, AI Gateway requests, "Fix with g1t" on a security alert, and every Customize route (marketplaces, plugins, connectors). The callbacks the agent sandbox reported through (/agent-runs/*, /runs/:id/usage, /plans/:id, /reviews/:id) go with them, update_repo_settings stops accepting agent_review, max_revisions and hold_low_confidence, import_issue stops accepting assign, and an old agent token with no run behind it is refused.2d ago

lib.rsThe merge queue works out who answers for a failed combination and tells the work: a state that fails while an entry ahead of it is still being tested is held until those ahead settle, so a broken change is blamed on itself and the entries tested with it are tested again instead of being taken out; an entry whose own checks pass but which fails with several entries ahead has smaller combinations (the default branch, half of the suspects and the entry) built and checked by the merge_group workflows, halving the suspects within three extra builds, and never landed. The result goes on the pull request's and its issue's timelines and into its session, as an integration_failure decision record (tested), and as integration.failed with the pull request, its issue, the combination, the failing check's name, conclusion and link, whether it was bisected, the suspects and the other pull requests; a combination that passes is an integration_passed decision and integration.passed. An entry the queue took out keeps its merge request: once a new commit's checks all pass, g1t merges it again as whoever queued it, which puts it back in the queue under the branch's rules as they are then.2d ago

limits.rsMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9'2d ago

logs.rsMerge Actions runs: summaries, attempts and re-runs, graceful cancel, log downloads, badges (actions 0009)6d ago

mcp.rsThe merge queue works out who answers for a failed combination and tells the work: a state that fails while an entry ahead of it is still being tested is held until those ahead settle, so a broken change is blamed on itself and the entries tested with it are tested again instead of being taken out; an entry whose own checks pass but which fails with several entries ahead has smaller combinations (the default branch, half of the suspects and the entry) built and checked by the merge_group workflows, halving the suspects within three extra builds, and never landed. The result goes on the pull request's and its issue's timelines and into its session, as an integration_failure decision record (tested), and as integration.failed with the pull request, its issue, the combination, the failing check's name, conclusion and link, whether it was bisected, the suspects and the other pull requests; a combination that passes is an integration_passed decision and integration.passed. An entry the queue took out keeps its merge request: once a new commit's checks all pass, g1t merges it again as whoever queued it, which puts it back in the queue under the branch's rules as they are then.2d ago

notifications.rsThe contracts no longer describe g1t's own agents, and workspaces can keep their AI providers. Every consumer had already stopped using them, so the TypeScript and Rust contracts drop the workspace-agent, ability, look, skill-library, context, runner-agent and mention modules, the chat and docs RPCs agents posted and read through, the folio agent methods, the agent_waiting notification, agent.asked and memory.changed events, AI credit, token and gateway billing types, model routes and sessions, team agents, agent tokens, plan, review, message and confidence types, command rules, cost caps and confidence rules. The agents:run and models:* scopes are no longer offered by any preset, OAuth default or permission form, but a stored token or grant that names them still reads; and the removed operations are gone from the scope table, so the API's check that every operation has exactly one scope is strict again. What stored data needs in order to parse (old run and credential kinds, an agent team lead, retired rules and webhook events, old guardrail and integration settings) still parses, and a run's token is still PrincipalKind::Agent, which now means a run's token and the @g1t rows written before. The customize, marketplace, skills and claude-plugin contracts stay only until the mobile app drops its Customize screens.2d ago

oauth.rsArtifacts contracts: folios, their four kinds, dashboard datasets, folio events and the artifacts scopes are typed and validated the same in TypeScript and Rust, with nothing using them yet5d ago

oidc.rsMerge the OIDC docs: deploying to AWS, Google Cloud or Azure with a job's short-lived identity token now says which of the cloud's hosts to allow under Workflow-only domains, for the deploying workflow and environment, since a job on g1t's machines reaches only the hosts its project allows; and tests for the audience a job asks for and for the token variables reaching each step.2d ago

openapi.rsThe merge queue works out who answers for a failed combination and tells the work: a state that fails while an entry ahead of it is still being tested is held until those ahead settle, so a broken change is blamed on itself and the entries tested with it are tested again instead of being taken out; an entry whose own checks pass but which fails with several entries ahead has smaller combinations (the default branch, half of the suspects and the entry) built and checked by the merge_group workflows, halving the suspects within three extra builds, and never landed. The result goes on the pull request's and its issue's timelines and into its session, as an integration_failure decision record (tested), and as integration.failed with the pull request, its issue, the combination, the failing check's name, conclusion and link, whether it was bisected, the suspects and the other pull requests; a combination that passes is an integration_passed decision and integration.passed. An entry the queue took out keeps its merge request: once a new commit's checks all pass, g1t merges it again as whoever queued it, which puts it back in the queue under the branch's rules as they are then.2d ago

operations.rsThe merge queue works out who answers for a failed combination and tells the work: a state that fails while an entry ahead of it is still being tested is held until those ahead settle, so a broken change is blamed on itself and the entries tested with it are tested again instead of being taken out; an entry whose own checks pass but which fails with several entries ahead has smaller combinations (the default branch, half of the suspects and the entry) built and checked by the merge_group workflows, halving the suspects within three extra builds, and never landed. The result goes on the pull request's and its issue's timelines and into its session, as an integration_failure decision record (tested), and as integration.failed with the pull request, its issue, the combination, the failing check's name, conclusion and link, whether it was bisected, the suspects and the other pull requests; a combination that passes is an integration_passed decision and integration.passed. An entry the queue took out keeps its merge request: once a new commit's checks all pass, g1t merges it again as whoever queued it, which puts it back in the queue under the branch's rules as they are then.2d ago

packages.rsMerge packages: roles, Actions access, source label, soft delete, API6d ago

people.rsCards you act on in chat; agents comment and review as themselves; names shown cleanly; commits on the calendar5d ago

pins.rsThe contracts no longer describe g1t's own agents, and workspaces can keep their AI providers. Every consumer had already stopped using them, so the TypeScript and Rust contracts drop the workspace-agent, ability, look, skill-library, context, runner-agent and mention modules, the chat and docs RPCs agents posted and read through, the folio agent methods, the agent_waiting notification, agent.asked and memory.changed events, AI credit, token and gateway billing types, model routes and sessions, team agents, agent tokens, plan, review, message and confidence types, command rules, cost caps and confidence rules. The agents:run and models:* scopes are no longer offered by any preset, OAuth default or permission form, but a stored token or grant that names them still reads; and the removed operations are gone from the scope table, so the API's check that every operation has exactly one scope is strict again. What stored data needs in order to parse (old run and credential kinds, an agent team lead, retired rules and webhook events, old guardrail and integration settings) still parses, and a run's token is still PrincipalKind::Agent, which now means a run's token and the @g1t rows written before. The customize, marketplace, skills and claude-plugin contracts stay only until the mobile app drops its Customize screens.2d ago

projects.rsMerge branch 'main' into worktree-agent-a69aeabc4b0deeb976d ago

protection.rsMerge GitHub pull request #8 (claude/cool-newton-7nm8r9): Docker deployments on g1t.page behind a switch that stays off until Cloudflare's container APIs are checked live, workflows a workspace manages in its repositories, tarball and zipball downloads, refs/pull/* kept to g1t alone, framework detection for g1t.page builds, and a workflow's event payload matching GitHub's.2d ago

reference.jsonThe merge queue works out who answers for a failed combination and tells the work: a state that fails while an entry ahead of it is still being tested is held until those ahead settle, so a broken change is blamed on itself and the entries tested with it are tested again instead of being taken out; an entry whose own checks pass but which fails with several entries ahead has smaller combinations (the default branch, half of the suspects and the entry) built and checked by the merge_group workflows, halving the suspects within three extra builds, and never landed. The result goes on the pull request's and its issue's timelines and into its session, as an integration_failure decision record (tested), and as integration.failed with the pull request, its issue, the combination, the failing check's name, conclusion and link, whether it was bisected, the suspects and the other pull requests; a combination that passes is an integration_passed decision and integration.passed. An entry the queue took out keeps its merge request: once a new commit's checks all pass, g1t merges it again as whoever queued it, which puts it back in the queue under the branch's rules as they are then.2d ago

renamed.rsMerge branch 'worktree-agent-a8385d293d42c913a'6d ago

responses.rsThe merge queue works out who answers for a failed combination and tells the work: a state that fails while an entry ahead of it is still being tested is held until those ahead settle, so a broken change is blamed on itself and the entries tested with it are tested again instead of being taken out; an entry whose own checks pass but which fails with several entries ahead has smaller combinations (the default branch, half of the suspects and the entry) built and checked by the merge_group workflows, halving the suspects within three extra builds, and never landed. The result goes on the pull request's and its issue's timelines and into its session, as an integration_failure decision record (tested), and as integration.failed with the pull request, its issue, the combination, the failing check's name, conclusion and link, whether it was bisected, the suspects and the other pull requests; a combination that passes is an integration_passed decision and integration.passed. An entry the queue took out keeps its merge request: once a new commit's checks all pass, g1t merges it again as whoever queued it, which puts it back in the queue under the branch's rules as they are then.2d ago

rest.rsThe merge queue works out who answers for a failed combination and tells the work: a state that fails while an entry ahead of it is still being tested is held until those ahead settle, so a broken change is blamed on itself and the entries tested with it are tested again instead of being taken out; an entry whose own checks pass but which fails with several entries ahead has smaller combinations (the default branch, half of the suspects and the entry) built and checked by the merge_group workflows, halving the suspects within three extra builds, and never landed. The result goes on the pull request's and its issue's timelines and into its session, as an integration_failure decision record (tested), and as integration.failed with the pull request, its issue, the combination, the failing check's name, conclusion and link, whether it was bisected, the suspects and the other pull requests; a combination that passes is an integration_passed decision and integration.passed. An entry the queue took out keeps its merge request: once a new commit's checks all pass, g1t merges it again as whoever queued it, which puts it back in the queue under the branch's rules as they are then.2d ago

rules.rsThe contracts no longer describe g1t's own agents, and workspaces can keep their AI providers. Every consumer had already stopped using them, so the TypeScript and Rust contracts drop the workspace-agent, ability, look, skill-library, context, runner-agent and mention modules, the chat and docs RPCs agents posted and read through, the folio agent methods, the agent_waiting notification, agent.asked and memory.changed events, AI credit, token and gateway billing types, model routes and sessions, team agents, agent tokens, plan, review, message and confidence types, command rules, cost caps and confidence rules. The agents:run and models:* scopes are no longer offered by any preset, OAuth default or permission form, but a stored token or grant that names them still reads; and the removed operations are gone from the scope table, so the API's check that every operation has exactly one scope is strict again. What stored data needs in order to parse (old run and credential kinds, an agent team lead, retired rules and webhook events, old guardrail and integration settings) still parses, and a run's token is still PrincipalKind::Agent, which now means a run's token and the @g1t rows written before. The customize, marketplace, skills and claude-plugin contracts stay only until the mobile app drops its Customize screens.2d ago

run_artifacts.rsThe artifacts service is services/artifacts, the Worker g1t-artifacts, bound as ARTIFACTS by the API, the site and the agents; its live rooms move to it with a Durable Object transfer from g1t-docs-service, and its database, bucket, indexes and queue keep their names. The git store's binding and settings are GITSTORE, its ops scripts gitstore-*, and workflow run artifacts keep their compatible API under run_artifacts modules. The deploy tool puts a Worker that has never deployed before the Workers in its stage that bind to it, and the deploy guide gives the cutover runbook.4d ago

runners.rsMerge GitHub pull request #8 (claude/cool-newton-7nm8r9): Docker deployments on g1t.page behind a switch that stays off until Cloudflare's container APIs are checked live, workflows a workspace manages in its repositories, tarball and zipball downloads, refs/pull/* kept to g1t alone, framework detection for g1t.page builds, and a workflow's event payload matching GitHub's.2d ago

security.rsThe contracts no longer describe g1t's own agents, and workspaces can keep their AI providers. Every consumer had already stopped using them, so the TypeScript and Rust contracts drop the workspace-agent, ability, look, skill-library, context, runner-agent and mention modules, the chat and docs RPCs agents posted and read through, the folio agent methods, the agent_waiting notification, agent.asked and memory.changed events, AI credit, token and gateway billing types, model routes and sessions, team agents, agent tokens, plan, review, message and confidence types, command rules, cost caps and confidence rules. The agents:run and models:* scopes are no longer offered by any preset, OAuth default or permission form, but a stored token or grant that names them still reads; and the removed operations are gone from the scope table, so the API's check that every operation has exactly one scope is strict again. What stored data needs in order to parse (old run and credential kinds, an agent team lead, retired rules and webhook events, old guardrail and integration settings) still parses, and a run's token is still PrincipalKind::Agent, which now means a run's token and the @g1t rows written before. The customize, marketplace, skills and claude-plugin contracts stay only until the mobile app drops its Customize screens.2d ago

telemetry.rsMerge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.2d ago

token_policy.rsOne kind of access token; presence and status; usernames keep their case; the tour is a miniature of the real app; icons for password managers5d ago

toolkit.rsThe artifacts service is services/artifacts, the Worker g1t-artifacts, bound as ARTIFACTS by the API, the site and the agents; its live rooms move to it with a Durable Object transfer from g1t-docs-service, and its database, bucket, indexes and queue keep their names. The git store's binding and settings are GITSTORE, its ops scripts gitstore-*, and workflow run artifacts keep their compatible API under run_artifacts modules. The deploy tool puts a Worker that has never deployed before the Workers in its stage that bind to it, and the deploy guide gives the cutover runbook.4d ago

tools.rsThe merge queue works out who answers for a failed combination and tells the work: a state that fails while an entry ahead of it is still being tested is held until those ahead settle, so a broken change is blamed on itself and the entries tested with it are tested again instead of being taken out; an entry whose own checks pass but which fails with several entries ahead has smaller combinations (the default branch, half of the suspects and the entry) built and checked by the merge_group workflows, halving the suspects within three extra builds, and never landed. The result goes on the pull request's and its issue's timelines and into its session, as an integration_failure decision record (tested), and as integration.failed with the pull request, its issue, the combination, the failing check's name, conclusion and link, whether it was bisected, the suspects and the other pull requests; a combination that passes is an integration_passed decision and integration.passed. An entry the queue took out keeps its merge request: once a new commit's checks all pass, g1t merges it again as whoever queued it, which puts it back in the queue under the branch's rules as they are then.2d ago

why.rsThe merge queue works out who answers for a failed combination and tells the work: a state that fails while an entry ahead of it is still being tested is held until those ahead settle, so a broken change is blamed on itself and the entries tested with it are tested again instead of being taken out; an entry whose own checks pass but which fails with several entries ahead has smaller combinations (the default branch, half of the suspects and the entry) built and checked by the merge_group workflows, halving the suspects within three extra builds, and never landed. The result goes on the pull request's and its issue's timelines and into its session, as an integration_failure decision record (tested), and as integration.failed with the pull request, its issue, the combination, the failing check's name, conclusion and link, whether it was bisected, the suspects and the other pull requests; a combination that passes is an integration_passed decision and integration.passed. An entry the queue took out keeps its merge request: once a new commit's checks all pass, g1t merges it again as whoever queued it, which puts it back in the queue under the branch's rules as they are then.2d ago