syntaqxA repository's pages fail one card at a time: each page still fails on what it is about (the pull request, the issue, the commit, the run, the file, the list), and every other read goes through part(), so a service that does not answer leaves Unavailable in that card's place, not a blank card or a crashed page. Pull request: the diff, Sessions, Decisions, What happened, the preview, the merge queue's findings, Labels, Milestone, Notifications and the reviewer and assignee pickers each say so in place (settings stay strict: unread, they would let checks be ignored). Issue: Labels, Milestone, Notifications, assignees, links from outside g1t, Work and Decisions. Commit: its pull request (a stream that could reject into an Await with no errorElement), comments and the issues it closed. Code, tree and file: branches (inside the branch menu), deployments, the fork's source, the About sidebar (Packages no longer says "No packages published" when it could not be read) and a file's CODEOWNERS check; environmentsFor and forkSourceFor no longer swallow failures. Actions: workflows; a run's artifacts and job summaries; a check run's annotations. Deployments: environments, history and g1t.page hosting each on their own, never "No deployments yet" or "members can turn on hosting" because of a failure; a deployment that cannot be read is a 503, not a 404. Work: Live now, the queue, What happened, Just landed. Lists: label and milestone filters, branch rows' pull requests and previews, activity (no longer "No activity yet"), fork descriptions, compare's branches and changes, new pull request's forks and a named fork. Overview: Needs you, deployments, observability. Boundaries around the README, About, the run graph, annotations, summaries, report cards and the sidebar boxes. Kept quiet on purpose, each a decoration or an extra the service checks again: teams for mentions, ended claims, merge choices (settings answer), job-by-job checks, watcher and tag counts, the star count, release suggestions, compute notes, the plan on Deployments. Checked: apps/web tsc -b; npm test (987, 1 skipped).74236deHistory
- ..
- 0001_init.sql
- 0002_lifecycle.sql
- 0003_repo_settings.sql
- 0004_up_to_date.sql
- 0005_assignees.sql
- 0006_merge_rules.sql
- 0007_timeline.sql
- 0008_plans.sql
- 0009_lifecycle_snapshot.sql
- 0010_merge_queue.sql
- 0011_agent_messages.sql
- 0012_exchanges.sql
- 0013_commit_statuses.sql
- 0014_mergeability.sql
- 0015_agent_runs_and_memory.sql
- 0016_by_author.sql
- 0017_agent_mentions.sql
- 0018_guardrails.sql
- 0019_memory_capture.sql
- 0020_agent_waits.sql
- 0021_confidence.sql
- 0022_required_checks.sql
- 0023_read_paths.sql
- 0024_g1t_name.sql
- 0025_requested_by.sql
- 0026_code_owners.sql
- 0027_labels_milestones_bases.sql
- 0028_rulesets.sql
- 0029_commit_checks.sql
- 0030_comment_edits.sql
- 0031_mention_revisions.sql
- 0032_contributions.sql
- 0033_agent_comments.sql
- 0034_sessions_and_claims.sql
- 0035_integration_and_decisions.sql
- 0036_subagents_and_links.sql
- 0037_queue_attempts.sql
- 0038_session_updates.sql
- 0039_queue_bypass.sql
- 0040_queue_evidence.sql
- 0041_pull_head_repo.sql
- 0042_merge_settings.sql
- 0043_commit_comments.sql
- 0044_queue_methods.sql
- 0045_pull_message_commits.sql
- 0046_reactions.sql
- 0047_commit_closes.sql
- 0048_attachments.sql