[Contracts] Add stale contract human follow-up notification

[mattsoh]

Summary of the problem

Sometimes contracts get forgotten (maybe by the ops team or by the contract signees)

Describe your changes

Send a reminder after 1 month to HCB Ops to see if a follow up is required.

[Copilot]

Pull request overview

This PR adds an automated “stale contract” reminder for Fiscal Sponsorship contracts that remain in the sent state, intended to prompt HCB Ops follow-up after ~1 month, and also updates the receipt-upload email to include a fallback raw link.

Changes:

• Add Contract::OperationsUpdateJob and a new Contract::PartyMailer#operations_update action/subject for HCB-party notifications.
• Schedule the operations update 1 month after a Fiscal Sponsorship contract transitions to sent, plus a MaintenanceTasks backfill for existing sent contracts.
• Add a fallback “copy/paste link” block to the receipt attachment email partial.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
app/views/canonical_pending_transaction_mailer/_attach_receipt.html.erb	Adds a fallback receipt-upload link under the button.
app/tasks/maintenance/schedule_contract_operations_updates_task.rb	Backfills scheduling for existing sent Fiscal Sponsorship contracts.
app/models/contract/party.rb	Adds a new email subject helper for operations update notifications.
app/models/contract/fiscal_sponsorship.rb	Introduces OPERATIONS_UPDATE_AFTER and schedules the operations update on transition to sent.
app/mailers/contract/party_mailer.rb	Adds a new operations_update mailer action selecting an operations_update_* template.
app/jobs/contract/operations_update_job.rb	Enqueues the operations update notification when the contract is still sent.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

Suppressed comments (2)

app/jobs/contract/operations_update_job.rb:18

• This introduces a new delayed notification path (job + scheduling callback) but there’s no spec coverage ensuring (1) the job only emails when the contract is still sent?, and (2) sending a fiscal sponsorship contract enqueues the operations update job with the intended delay. Adding an RSpec example around Contract::OperationsUpdateJob (and/or the Contract::FiscalSponsorship callback) would help prevent regressions and accidental spam.

    def perform(contract)
      return unless contract.sent?

      party = contract.party(:hcb)
      return if party.nil?

      Contract::PartyMailer.with(party:).operations_update.deliver_later
    end

app/mailers/contract/party_mailer.rb:31

• operations_update sets template_name: "operations_update_#{@party.role}", but there are no corresponding view templates under app/views/contract/party_mailer/ (unlike the existing remind_* templates). This will raise ActionView::MissingTemplate when the job tries to send the email. Add at least operations_update_hcb.html.erb (since the job targets party(:hcb)) or adjust the mailer to use an existing template naming scheme that’s actually present.

    def operations_update
      mail to: @party.email,
           subject: @party.operations_update_email_subject,
           template_name: "operations_update_#{@party.role}"
    end

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[garyhtou]

I would actually separate this from the concept of a contract party. I would have this live in the contract itself. This is because contract parties are intended to be generic and work for all types of parties, including the organizer, co-signer, and HCB operations. Instead, what we're looking for here is stale contracts, and I would say that it's more of a contract-level concept rather than per party. My recommendation is that you move this to the contract mailer.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.