🐸 Frogue(Fed)

−use crate::entities::ap_actors;

−use crate::entities::{repositories, users};

−/// Fetch or create an actor for the given repository, generating a keypair if needed.

−/// Returns the appropriate URL based on whether this is a user actor or repository actor.

−/// Returns None if the URL doesn't match a local actor pattern or if the user doesn't exist.

−/// Matches both user actors at `{base}/~{user}` and repository actors at `{base}/~{owner}/{slug}`.

−//! Delivery worker: polls pending deliveries and sends them to follower inboxes.

−//! Also provides the shared `enqueue_delivery` helper for inserting activities

−//! and creating delivery rows.

−/// Polls every 2 seconds for pending deliveries and sends them with HTTP signatures.

−/// Shared helper used by inbox (Accept/Follow), following module (Follow, Undo),

−/// and notes (Create). Returns the activity ID.

−/// The `page` parameter (0-indexed) determines which slice of entries to return.

− // Query viewer's reactions to determine which notes they've liked or boosted

− use crate::entities::ap_reactions;

− use crate::entities::ap_reactions;

−/// Publish an activity signed by one actor but delivered to another actor's followers.

−/// This is used for comments: the comment is signed by the user actor but delivered

−/// to the repository's followers (since the user may have zero followers while the

−/// repo has many).

−/// * `signer_actor_id` - The actor who signs the activity (user actor for comments)

−/// * `follower_source_actor_id` - The actor whose followers receive the delivery (repo actor)

−/// and fans it out to all followers. If offerer_inbox is provided (remote Offer),

−/// also enqueues delivery to the offerer.

−//! Handles Offer (ticket creation), Resolve (ticket closure), Edit (ticket updates),

−//! Create (comments), and Add (patch sets) activities from remote actors.

−/// Per decision 7, inline patches are rejected. Origin-only patches are also rejected.

− // Reject{object: add.id, summary: "inline patch merge requests are not supported yet"}

− // Verify actor attribution: the activity's actor field must match the verified actor URL

− // Check if the Announce contains an embedded Note from an accepted followee

− /// Ticket comment: `{base}/~{owner}/{slug}/tickets/{number}/comments/{uuid}`.

− /// Patch comment: `{base}/~{owner}/{slug}/patches/{number}/comments/{uuid}`.

−/// Renders the markdown to HTML, stores the note, and creates a Create activity.

− use sea_orm::QueryFilter;

−/// Groups followers by sharedInbox when available to avoid duplicate deliveries.

− use sea_orm::QueryFilter;

− use std::collections::HashSet;

−/// Deserialize the icon field, which can be either a URL string or an Image object

− use serde::de::{self, Visitor};

− // Validate the actor URL's host matches the webfinger host (prevent JRD redirect attacks)

−/// This is a generic helper for fetching ActivityPub objects with proper signing.

−/// Used for both actor documents and note objects.

−/// If the cache entry is older than 24 hours, re-fetches and updates it in place.

−/// Only updates notes that we've previously stored. The content is re-sanitized.

−//! Supports both legacy draft-cavage signatures and RFC 9421 HTTP Message Signatures.

− use chrono::Datelike;

−use crate::activitypub::keys;

−use crate::activitypub::signatures::SignatureError;

−use base64::{Engine as _, engine::general_purpose::STANDARD as BASE64};

−/// Verify an inbound request's signature using RFC 9421 HTTP Message Signatures.

−/// 4. Parameters extracted: keyid (required), created (required), alg (optional)

− use actix_web::http::header::{HeaderMap, HeaderName, HeaderValue};

− /// ForgeFed: ticket tracker actor URL (self-referential for repos that track their own tickets).

− /// ForgeFed: patch tracker actor URL (self-referential for repos that track their own patches).

− /// ForgeFed: repositories whose tickets this actor tracks (bidirectional back-reference).

− /// ForgeFed: repositories whose patches this actor tracks (bidirectional back-reference).

−/// Offer.object can be a URL (fetch via signed_get) or an embedded Ticket/Patch.

−use super::ApUrls;

−

−use actix_session::Session;

−use actix_session::SessionExt;

−use actix_web::{FromRequest, HttpRequest, dev::Payload, error::ErrorUnauthorized};

−use argon2::Argon2;

−use argon2::password_hash::{

− PasswordHash, PasswordHasher, PasswordVerifier, SaltString, rand_core::OsRng,

−};

− // Remote-created comments (author is None) can only be changed by the owner

−/// The authors who wrote comments, looking up both local users and remote actors.

− // Use preferred_username if available, otherwise extract from actor_url

−//! is the ActivityPub Follow activity's id we sent, used for matching Accept/Reject.

−//! and the status (pending/accepted/rejected) with the assigned URL if accepted.

− /// The local user who wrote this comment (null for remote-authored comments).

− /// The format of the content: 'markdown' (default) or 'html' (for remote content).

− /// Local user who created this patch proposal (null for remote-created proposals).

− /// The activity URL of the last emitted/accepted Resolve, for Undo(Resolve) correlation.

− /// The activity URL of the last emitted/accepted Resolve, for Undo(Resolve) correlation.

− // Creating a new patch proposal OR updating an existing one by change-id

− // Check if there are any differences between the patch and target branch

− // If ready option was provided and we just created, open the patch proposal

− use crate::activitypub::ApUrls;

− use crate::activitypub::types;

− use crate::entities::prelude::{ApFollowers, ApRemoteActors};

− use crate::entities::{ap_followers, ap_remote_actors, users};

− use std::collections::HashSet;

−/// Emits Offer+Accept activities when a patch is opened via push with ready option

− use uuid::Uuid;

− use uuid::Uuid;

− // In a full implementation, this would use git format-patch to generate the actual patches

−use actix_session::{SessionMiddleware, storage::CookieSessionStore};

− /// The environment variable key that enables public https url configuration and federation. No default value.

− /// A 64 character-long string used to sign/verify the session cookie. Default: randomly generated, so a server restart will invalidate all current sessions.

− /// Environment variable holding the directory bare git repositories live under.

− /// Environment variable holding the name the SSH server should be advertised

− /// under in clone URLs.

− /// Environment variable holding the SSH user Frogue should advertise in clone URLs.

− /// Timeout in seconds for a guest that authenticated but never opened the TUI.

− /// Environment variable for registration mode. See [`registration::RegistrationMode`]. default: open

−use pulldown_cmark::{Event, Options, Parser, Tag, html};

−/// The sanitizer permits only checkbox inputs — no text fields, no hidden inputs,

−/// no way to submit a form. The `type` attribute is gated by value rather than

−/// by name, so a non-checkbox input cannot be injected via raw HTML.

−/// Renders `source` from markdown to HTML, rewriting relative file links to tree URLs.

−/// This is used when rendering markdown files in the repository browser, so that

−/// links like `[docs](./docs/guide.md)` become navigable links to the tree view.

− // Only checkbox inputs from task lists should survive; raw HTML inputs are not allowed.

−/// A valid change-id is exactly 32 characters long and uses only the reverse-hex

−/// alphabet: z, y, x, w, v, u, t, s, r, q, p, o, n, m, l, k (16 letters from

−/// 'k' to 'z' inclusive).

−/// Attempts to merge the source ref into the target branch according to the policy.

−/// Creates a merge commit with target as the first parent and source as the second.

−use crate::entities::patch_proposals::Model as PatchProposal;

−use crate::entities::patch_proposals::{MergePolicy, Status};

−/// Whether `user` may change the merge policy of a patch proposal in a repository

−/// owned by `owner`. Only the repository owner may change the merge policy.

− // Remote-created patches (creator is None) can only be revised by the owner

−use chrono::Utc;

−use uuid::Uuid;

−/// Updates a patch proposal with the given fields, including the resolve_activity_url.

−/// If snapshot OIDs are provided, they are stored to preserve the diff state at close time.

− if len > 0xFFFF {

−use crate::auth::hash_password;

−use crate::entities::{invites, users};

−/// Returns the invite validity duration, read from the environment or the default.

−/// Returns the number of invites allowed per day, read from the environment or the default.

−/// Returns Ok(()) if registration should proceed, or an error if it should be blocked.

− // A row git could not shape into a commit is dropped rather than

− // failing the whole listing, the same way `refs` treats a ref

− // that is not a commit.

− // Could be a mode change or an empty diff; treat as Modified.

− // We can't tell from paths alone; the diff header clarifies.

− // `\ No newline at end of file` and other metadata lines are ignored.

−/// the visitor sent it and as its primary subtag, so `fr-CA` finds `README.fr.md`

−/// as well as `README.fr-CA.md`, and both the `.` and `_` separators are tried

−/// because repositories use both. Only the top level of the tree is looked at.

− let odd = [0x00u8, 0x01, 0xFF, b'a', b'b'];

− // Newest commit: modify file1.txt (2 additions, 1 deletion) + add file3.txt (3 additions)

− // Total: 2 files, 5 insertions, 1 deletion

− // Binary files show as "-" in numstat, which we should handle gracefully

− // Topic's history should include all three: the branch's commit plus its ancestors.

−use crate::state_read;

−use crate::{AppState, FROGUE_PUBLIC_URL_VAR_KEY, SshThrottleConfig};

−/// Buffer size for child communication. Needs to be small-ish because it stays on the child's stack

−/// Yeah, so this one (pun intended) is weiiiird. It has only one use but i was feeling weird just puting "1" as arg. 1 is the file descriptor of stderr.

−/// of possession: the client signed with it, so we know they hold the private half.

− /// A key that was verified (the client signed it) but belongs to no user yet.

− /// This is the registration candidate.

− // it's already registered. The auth_publickey step will verify possession.

− /// Route incoming data to either git or the TUI, depending on what's active.

− /// status is what the client waits for. Dropping the whole handle here would

− /// drop the kill sender too, which the waiting task reads as "stop" - and

− /// that would cut the answer off mid-flight.

− // TODO: check that it really cuts the connection if we're still on the login after SSH_TUI_TIMEOUT_SECONDS_VAR_KEY

− // Owner can always push. For public repos, any authenticated user can

− // run receive-pack; the pre-receive hook will restrict what refs they

− // may touch.

−//! picture - the command is parsed by [`crate::repositories::parse_git_command`],

−//! which accepts exactly those two words and nothing else - so the server runs

−//! `git` as a child process on a single channel and shuttles its standard

−//! streams back and forth.

−use russh::keys::ssh_key;

−use russh::keys::{PrivateKey, load_secret_key};

−use crate::{AppState, SshThrottleConfig, config::*};

−/// KINDA DEPRECIATED How to reach the SSH server, for the clone URLs the webui shows.

−/// TODO: Remove fully

−/// Spawns the registration form and handles input/output through the provided channels.

−//! A simple terminal UI that allows unauthenticated users to register an account

−//! by providing username, email, and password. The SSH public key is taken from

−//! the verified connection and displayed as read-only.

−use crossterm::ExecutableCommand;

−use crossterm::terminal;

−use actix_web::{Error, error::ResponseError};

−use opentelemetry::global;

−use opentelemetry::{KeyValue, Value};

−/// Installs the global subscriber and returns the handle that owns the pipeline.

− /// Held for its `Drop`, which drains the exporter. `None` when export is off.

−/// The root span per request, like [`tracing_actix_web::DefaultRootSpanBuilder`]

−/// but with one correction: a `5xx` built by a handler is an error.

−/// error, so a handler that answers a bare `HttpResponse::InternalServerError()`

−/// (which is how every failure path in this crate reports a database problem)

−/// would be recorded as `otel.status_code=OK`. Marking the status from the

−/// response code makes those traces come out red in Jaeger, where the operator

−/// looks for them.

− // Remote-created tickets (creator is None) can only be changed by the owner

− // Space around the names is what writing a label's name by hand leaves behind.

− // Every one of the labels, not any of them: a filter of `bug,improvement` is a

− // ticket that is both a bug and an improvement.

−/// The authors who created tickets, looking up both local users and remote actors.

−use super::{

− Page,

− components::{Complaint, PasswordField, TextField},

−};

−/// The registration page, showing `message` instead of the form (for closed mode).

− /// The base URL we can find this comment at. MUST contain the "/comments" part.

− // let delete_action = format!("{}/{}/delete", base_action, comment.uuid);

−use crate::views::{

− Page,

− components::{RepositoryChrome, RepositoryTab},

− repositories::CommitSummary,

−};

−use super::{

− Page,

− components::{RefSelect, RepositoryChrome, RepositoryTab},

− repositories::CommitSummary,

−};

−use crate::views::{

− Page, RefSummary,

− commit::{diff_stats_summary, file_diffs},

− commits::CommitLine,

− components::{Complaint, RefSelect, RepositoryChrome, RepositoryTab},

− repositories::CommitSummary,

−};

−/// A repository heading: the owner, a slash, the slug, and the visibility indicator.

−/// A comment author, local or remote: local gets a `~username` link, remote gets

−/// a link to their actor URL plus a badge saying so.

−/// Renders Previous/Next links based on the current page and whether more items exist.

−/// The base_url should include the path but not the query string.

−use super::{

− Page,

− components::{RepositoryChrome, RepositoryTab},

− tree::Breadcrumb,

−};

−use super::Page;

−use super::{ActionTarget, Note, NoteActions, NoteAuthor, NoteAuthorHandle};

−use super::{Page, components::Complaint};

−use super::components;

−use crate::activitypub::notes::NoteReactions;

−/// A unified note component with author, content, permalink, counts, and actions.

− use super::*;

−use super::{

− Page,

− commit::{diff_stats_summary, file_diffs},

− components::{

− AuthorName, Complaint, FilterLink, RepositoryChrome, RepositoryTab, TextArea, TextField,

− },

− repositories::CommitSummary,

− /// If the diff cannot be shown, the reason (e.g. merged before snapshots existed).

−use super::{

− ActionTarget, Note, NoteActions, NoteAuthor, NoteAuthorHandle, Page,

− components::{Complaint, TextArea},

−};

−use crate::{entities::ap_notes, views::components};

−use super::{

− Page,

− components::{RepositoryChrome, RepositoryTab},

− repositories::RefSummary,

−};

−use super::{Page, components::Complaint};

−use super::{

− Page,

− components::{Complaint, DeleteForm, RepositoryChrome, RepositoryTab, TextArea, TextField},

− form::{MergePolicySelect, VisibilityRadios},

−use super::{

− Page,

− components::{Complaint, DeleteForm, TextArea},

−};

−use super::{

− Page,

− components::{

− AuthorName, Complaint, DeleteForm, FilterLink, RepositoryChrome, RepositoryTab, TextArea,

− TextField,

− },

−use super::{

− Page,

− components::{RepositoryChrome, RepositoryTab},

−};

−use crate::AppState;

−use crate::entities::{prelude::Users, users};

−use crate::state_read;

−use crate::views;

−use crate::AppState;

−use crate::entities::repositories;

−use crate::entities::users;

−use crate::entities::{ap_followers, ap_remote_actors};

−

−use crate::state_read;

− use sea_orm::ActiveModelTrait;

− use sea_orm::Set;

− use crate::entities::ap_reactions;

− use sea_orm::ActiveModelTrait;

− use sea_orm::Set;

− use sea_orm::ActiveModelTrait;

− use sea_orm::Set;

− use crate::entities::ap_reactions;

− use sea_orm::ActiveModelTrait;

− use sea_orm::Set;

−/// Remove an announce (unboost) from a remote note by sending an Undo(Announce) activity.

− use crate::entities::ap_reactions;

− use sea_orm::ColumnTrait;

− use sea_orm::QueryFilter;

− // Note: We don't have author email in the Commit struct, so we omit attributed_to

− // In the future, this could be matched by author name or extended to include email

− // Look up the creator (local tickets have creator_id, remote tickets have remote_actor_id)

−use crate::AppState;

−use crate::state_read;

−use crate::AppState;

−use crate::state_read;

−use crate::AppState;

−use crate::views;

−use crate::state_read;

−use crate::{AppState, activitypub, registration};

−use std::sync::Arc;

−use crate::AppState;

−use crate::state_read;

−/// Generates patch files using git format-patch for the range default_branch..branch

−/// GET `/~{user}/remote-tickets` - list of remote tickets/MRs this user has opened

−/// GET `/~{user}/remote-tickets/new` - form to open a ticket/MR on a remote tracker

− // Verify the bidirectional reference: tracker must list the repo in tracksTicketsFor/tracksPatchesFor

− // Exception: be lenient when tracker == repo actor (self-tracking case)

− // For patches, we need to build a Patch object with attachment and collection

−use actix_web::{HttpRequest, HttpResponse, get, http::header, post, web};

−use crate::AppState;

−use crate::highlight;

−use crate::markdown;

−use crate::repositories::store;

−use crate::repositories::{self, RepositoryPath};

−use crate::state_read;

−/// The `rev` must resolve to a commit via [`repositories::git::resolves_to_commit`];

−/// otherwise the page is `404`. A `rev` starting with `-` is refused to avoid

−/// argument injection, the same guard [`commits_address`] uses.

− // Should not happen if resolves_to_commit returned true, but handle it.

− // Should not happen if resolves_to_commit returned true, but handle it.

− // Directories first, the shape of a file tree everywhere, and then by

− // name: what a reader scanning a page wants, rather than git's own

− // byte order.

− use super::accept_languages;

− use super::is_markdown;

− use super::resolve_tail;

− use super::split_compare_range;

− use super::usable_compare_end;

−use crate::AppState;

−use crate::comments;

−use crate::markdown;

−use crate::state_read;

−use crate::views;

−

−use super::readable_repository;

− /// The state filter: "all", "draft", "open", "closed", "merged", or empty for default.

− // Check if the diff is unavailable (merged/closed before snapshots were implemented)

− base_url: "", // filled later on in [`crate::views::comments::CommentListView`]

− let new_resolve_url =

− if old_status != status && status == crate::entities::patch_proposals::Status::Closed {

− // Open→Closed: will emit Resolve, need to generate and store the URL

− let state_guard = state_read(&data).await;

− let federation_enabled = crate::activitypub::enabled(&state_guard);

− let is_public = repository.visibility.label() == "public";

− drop(state_guard);

− if federation_enabled && is_public {

− let state_guard = state_read(&data).await;

− let urls = crate::activitypub::ApUrls::new(state_guard.public_url());

− Some(urls.activity(&owner.name, Uuid::new_v4()))

− } else {

− None

− }

− } else if old_status != status && status == crate::entities::patch_proposals::Status::Open {

− // Closed→Open: will emit Undo(Resolve), clear the URL

− None

− // No status change or same status: keep existing value

− old_resolve_url.clone()

− };

− // Insert Offer into user's activities (no delivery - tracker is local)

− // For now, we'll just log and redirect. A better UX would pass the error

− // through flash messages or query parameters.

− // Publish with user as signer, repo followers as delivery target

− // Publish with user as signer, repo followers as delivery target

− // Publish with user as signer, repo followers as delivery target

− // Check if the diff is unavailable (merged/closed before snapshots were implemented)

− base_url: "", // filled later on in [`crate::views::comments::CommentListView`]

−use crate::AppState;

−use crate::repositories;

−use crate::tickets;

−use crate::views;

−

−use super::readable_repository;

− // Label exists and belongs to this repository, proceed with deletion

−use crate::AppState;

−use crate::comments;

−use crate::markdown;

−use crate::state_read;

−use crate::views;

−

−use super::readable_repository;

− /// The state filter: "open", "closed", or absent for open tickets (the default).

− base_url: "", // filled later on in [`crate::views::comments::CommentListView`]

− // Publish with user as signer, repo followers as delivery target

− // Publish with user as signer, repo followers as delivery target

− // Publish with user as signer, repo followers as delivery target

− base_url: "", // filled later on in [`crate::views::comments::CommentListView`]

−use crate::AppState;

−use crate::state_read;

−use sea_orm::{ActiveModelTrait, DatabaseConnection, DbErr, EntityTrait, PaginatorTrait};

−use sea_orm::{ColumnTrait, QueryFilter};

−use crate::AppState;

−use crate::state_read;

−use crate::views;

−//! discovery, lazy keypair generation, and the federation gate (disabled → 404).

−/// Test 2: Same request without the Accept header → HTML profile (existing behaviour).

−/// Test 6: Non-federated spawn (no FROGUE_PUBLIC_URL) → actor and webfinger → 404.

−//! Permissions: author or repo owner can edit/delete, anyone logged in can comment.

− // Refused comments re-render the detail page with the error shown (200 status)

−/// Fills `owner/slug`'s bare repository with commits that have actual file changes.

−//! The compare view: shows the diff between two revisions (branches, tags, or commits).

−/// - branch `feat` at c2: c3 "Fork change" (append "from feat\n" to readme.txt), c4 "Add feature file" (feature.txt = "feature\n")

− // The patch page should still show the original merged content, not the new changes

−//! Phase 1 tests: Remote actor discovery via webfinger (now integrated with follow)

− // Alice follows bob@127.0.0.1:recorder_port (discovery happens automatically)

− // Connect to the database and verify the remote actor was cached with name and preferred_username

− [0x00u8, 0x01, 0x02, 0xFF, 0x00, 0x7F],

− // Check that the empty file message section doesn't have syntax highlighting spans

− // (We can't check the absence of everything, but we can check it doesn't crash)

−/// Test: Feed pagination - 21 notes shows 20 on page 0 with next link, 21st on page 1 with prev link

−use miette::IntoDiagnostic;

−use sea_orm::{ActiveModelTrait, Database, Set};

−use support::{Client, Server, free_port};

−

−//! These tests verify that patch proposal activities (Offer, Add, Resolve, Push)

−//! are correctly emitted to repository followers.

−/// Test 5: Creator deletes refs/patches/1 → PP closed. Stranger deletes → refused.

−/// Test 7: Private repo, stranger → refused at connection level (existing gate).

−/// Test 8: Mixed push (branch + patch ref) by a stranger → whole push refused by pre-receive.

−/// Test 1: Pushing a commit with a change-id to refs/patches creates a PP with that change-id.

−/// Test 2: Amending with the same change-id updates the existing PP instead of creating a new one.

−/// Test 4: Pushing a commit with a mismatched change-id to refs/patches/{n} is refused.

− // Alice (owner) can merge (will fail because no actual git refs, but should be 403 for others)

− // For now, just test that the endpoint exists and rejects non-owners

− // Alice (owner) can attempt to merge (will fail because no actual git refs exist)

− // but should get a redirect or error, not 403

− // The merge will fail because there are no actual git refs, but it should not be 403

− // We can't directly query the DB, but the test verifies the endpoint accepts it

− // The actual sanitization is tested in the markdown module

− // Should get 404 (not found) or 303 (redirect) depending on whether note exists

− // Note: The endpoint is /remote-notes/{id}/react, which doesn't have a user prefix

− // So Bob can try to react to it

− // For now, we'll just test that the endpoint exists and returns 404 for unknown commits

− // In the future, we'll push a real commit and verify it's served

−/// Verifies that requesting a repository page with Accept: text/html returns HTML, not JSON.

−/// Verifies that when federation is disabled (no FROGUE_PUBLIC_URL), all repository

−/// ActivityPub endpoints return 404.

−/// Test: RemoteActor follows alice using RFC 9421 signature → Accept(Follow) is delivered

− // The settings page has the repository tab bar, with Settings marked as current.

−//! TODO: still need to write more accurate tests, but my guess is that we would need to hook into russh. Maybe improve the tests with some timers?

−use frogue::activitypub::keys;

−

−/// Handle a connection with configurable failures for the first N POST requests.

−use miette::IntoDiagnostic;

−

−use frogue::config::*;

−

−use std::fs;

−use std::thread;

− /// Like [`Server::spawn`], but sets additional environment variables for the

− /// spawned process.

− // A database of its own, so the tests never touch a running dev server's

− // database.

− /// `GET`s `path` with `Accept: application/activity+json` for ActivityPub content negotiation.

− /// `GET`s `path` with `Accept: application/activity+json` and parses the JSON response.

− /// `POST`s `body` as JSON with fully custom headers (no default Content-Type).

− // resolvedBy is set to the repo owner when closed (we don't track who specifically closed it)

− // TODO: Once we have a way to create patches via the API, test the full document structure

− // For now, this test just verifies the route exists and handles 404 correctly

−/// Test that creating a ticket emits an Accept activity to repository followers.

−/// This verifies the Offer+Accept flow for local ticket creation.

−/// Helper to fetch a comment Note document with ActivityPub content negotiation.

− // Serve a Repository actor document with ticketsTrackedBy pointing to itself

−/// Test that when a remote tracker Accepts our Offer, the pending ticket is marked accepted.

−/// Test that when a remote tracker Rejects our Offer, the pending ticket is marked rejected.

−/// Test that our own repository actor document includes tracksTicketsFor and tracksPatchesFor = [self].

−/// Test that remote ticket submission is rejected when the tracker doesn't advertise tracksTicketsFor.

− // Set up a remote repository with a separate tracker that doesn't advertise tracksTicketsFor

−/// Test that outbound patch submission generates a Patch object with patch collection.

−/// Test that remote ticket creators are displayed with remote badge and link in WebUI.

− // Verify the author name is present (should be the remote actor's preferred_username or display name)

− // The RemoteActor serves a default actor with name "Remote User"

−/// Test that remote comment authors are displayed with remote badge and link in WebUI.

−/// Opens a ticket with the state and labels given, and returns the answer to read the

−/// address it landed on out of.

− // A markdown file with relative links to verify they get rewritten to tree URLs

− // When viewing a markdown file, relative links should be rewritten to tree URLs

− // Add unique constraint for (repository_id, number) to ensure patch numbers are unique per repository

− // Add unique constraint for (repository_id, source_ref) to ensure source refs are unique per repository

− // change update the existing patch proposal rather than creating a new one.

− // Unique per (repository_id, change_id) — NULLs never collide in SQLite's

− // partial unique index (only non-NULL rows participate), so plain-git

− // patch proposals with no change-id remain unaffected.

− // Add the `state` column to `tickets`: Open or Closed, defaults to Open.

− // This replaces the old system where "open" and "closed" were labels.

− // Follower relationships: which remote actors follow which local actors.

− // follow_activity_id is the ActivityPub Follow activity's id, for Undo matching.

− // Add invited_by column to users table (without FK constraint - SQLite limitation)

− // Following relationships: which local actors follow which remote actors.

− // This is the opposite direction of ap_followers.

− // follow_activity_id is our Follow activity's id, for matching Accept/Reject.

− // state tracks whether the follow is pending, accepted, or rejected.

− // object_url is the canonical ActivityPub ID (unique to prevent duplicates)

− // This follows the pattern from migration 000019 (ap_reactions rebuild).

− // The FTS5 triggers must be dropped before the rebuild and recreated after.

− // The ticket_search FTS index is rebuilt from the new table.

− // Revert to original schema (creator_id NOT NULL, no federation columns)

− // - Add content_format (default 'markdown', can be 'html' for remote content)

− // Table for tracking outbound Offers to remote trackers (round-trip client side).

− // we create a row here with status 'pending', record the Offer activity,

− // and deliver it. When the remote tracker Accepts or Rejects, we update

− // the status and (for Accept) the assigned_url from the Accept.result field.