### Pilot applications (card 0264). Named in src/bot/flows/pilot.ts. A person applies in a private
### chat with the bot (the website's pilot button opens /start pilot), and the approver reads the
### application in his own private chat, with two buttons. The applicant's Telegram ID and
### username come from their account, never typed. $links is the group links the bot read, one
### per line, as the bot normalized them; no other text of the applicant reaches a message.

## The applicant's private chat.

pilot-closed = Applications for the WardForth pilot are not open right now.
# The privacy notice comes before any link is accepted (GitHub review of PR 362), and says only
# what docs/data-handling/privacy-policy.md and the code support: what the application holds,
# who receives it, a pointer for the retention (the policy states no pilot period yet; open
# question on card 0264), and the contact route. $url is the privacy policy's address and
# $address the contact for questions about data, the settings /privacy shows; while they are
# not set the flow answers pilot-closed instead.
pilot-ask-links =
    Thanks for your interest in the WardForth pilot.

    Before you apply: the application holds your Telegram ID and username, which I take from your account so you don't need to type them, the language I answer you in, the group links you send, and when it arrived. It goes to the person at WardForth who approves pilot applications, in a private chat with this bot.
    Retention: see the privacy policy, { $url }
    Questions and requests about your data: { $address }. /privacy shows both again.

    To apply, send me the link to the group you want to test, or up to five links, one per line. A public group's link looks like t.me/name, a private group's invite link like t.me/+abc.
# $max is the most links one application holds.
pilot-links-invalid = I couldn't find a group link in that. Send links like t.me/name or t.me/+abc, at most { $max }.
pilot-received = Thank you. Your application is sent, and you will hear from me here once it has been read.
pilot-pending = Your application is already waiting to be read. You will hear from me here.
pilot-unavailable = I couldn't pass your application on just now. Please try again later.
pilot-approved = Good news: you are in the WardForth pilot. Send /start here to get the link that adds me to your group, and use it in the group you applied with. When I am an administrator there, the pilot is switched on for that group.
pilot-declined = Thank you for applying to the WardForth pilot. Your group was not chosen this time. You are welcome to apply again later.

## The approver's private chat.

# $user is a mention of the applicant, $id their Telegram user ID. $has-username is yes when
# $username, without the @, is passed. $count is the number of links, $links the links.
pilot-review = New pilot application from { $user }
    Telegram ID: { $id }
    Username: { $has-username ->
        [yes] @{ $username }
       *[no] none
    }
    { $count ->
        [one] Group link:
       *[other] Group links ({ $count }):
    }
    { $links }

    Approve lets the applicant add and activate the bot, so the processing agreement should be signed before you tap it (docs/pilot/onboarding.md, section 1.4).
pilot-approve-button = Approve
pilot-decline-button = Decline
pilot-desk-approved = Approved. The applicant with Telegram ID { $id } is now a holder and has been told how to add and activate the bot. The grant is created when one of the groups is activated.
pilot-desk-declined = Declined. The applicant with Telegram ID { $id } has been told, and the application is deleted.
# The decision is committed, but the message to the applicant was refused or its outcome is
# unknown (a timeout or a lost connection), so the approver passes it on by hand.
pilot-desk-approved-unreached = Approved. The applicant with Telegram ID { $id } is now a holder, but I could not confirm that my message reached them. Please tell them yourself to send /start to me for the link that adds me to their group. The grant is created when one of the groups is activated.
# The applicant's first held customer is not active: /start would give a link for it, which
# activation refuses, so nothing is approved yet.
pilot-desk-customer-inactive = Not approved yet. The applicant with Telegram ID { $id } already holds a customer that is not active, and /start would give them a link for that customer, which activation refuses. Reactivate that customer or remove the holder by hand, then tap Approve again; the application stays open.
pilot-desk-declined-unreached = Declined, and the application is deleted. I could not confirm that my message reached the applicant with Telegram ID { $id }, so please tell them yourself.
pilot-desk-closed = That application is no longer open: it was decided already or has expired.
# $title is the group's title, $chat its chat ID. $kind is public or invite; $link the link used.
pilot-desk-granted = Pilot grant created for { $title } (chat ID { $chat }), from { $kind ->
        [public] the public link { $link }
       *[invite] a slot of the invite link { $link }
    }.
pilot-desk-grant-failed = The pilot grant step failed for { $title } (chat ID { $chat }) after its activation. Check whether this group applied, and if it did, create the grant by hand.
# Both tries of the grant failed, and marking the group's link used failed too: the link is
# still open, so a manual grant now could be followed by an automatic one for another group.
pilot-desk-grant-unrecorded = The pilot grant step failed for { $title } (chat ID { $chat }) after its activation, and I could not mark its pilot link as used either, so the link is still open. Do not create the grant by hand until that link is marked used in the database (pilot.application_link): while it is open, another group of the same customer could take it.