Waterfront Toronto procurement (Bonfire) — publishes awarded contracts directly

Part of #103. Blocked on #103's keyspace and terms-of-use decisions.

## What exists

Waterfront Toronto partners with **Bonfire** — `https://waterfrontoronto.bonfirehub.ca`. All opportunities over **$100,000** are on the portal. Methods: Tenders, RFP, RFQ, Prequalification (PQ), and **Advanced Contract Award Notices (ACANs)**.

Crucially, it also publishes on its own site:

- **Awarded Contracts** — `https://www.waterfrontoronto.ca/opportunities/procurement/awarded-contracts`
- Current Opportunities — `https://www.waterfrontoronto.ca/opportunities/procurement/current-opportunities`
- Vendors of Record

## Why it is unusual and worth a look early

Two reasons this is a better first Bonfire target than TCHC (#107):

1. **It publishes awards on its own website**, outside the commercial portal. That likely sidesteps the platform terms-of-use question in #103 entirely — the awarded-contracts page is Waterfront Toronto's own publication.
2. **ACANs are a procurement type we hold nothing like.** An Advance Contract Award Notice announces an *intended* sole-source award and invites challenge before it is made. Our `noncompetitive` table records sole-source awards after the fact; an ACAN is the contestable window before one. That is a genuinely different fact.

## Caveat

Waterfront Toronto is a **partnered** corporation — tri-government (City, Ontario, Canada), not wholly City-owned. Whether it belongs in a *Toronto Bids* archive is a scoping judgement, not a technical one. Worth settling in #103 alongside TRCA and Pan Am Centre, which have the same shape.

## Sources

- https://www.waterfrontoronto.ca/opportunities/procurement
- https://www.waterfrontoronto.ca/opportunities/procurement/awarded-contracts
- https://www.waterfrontoronto.ca/opportunities/procurement/current-opportunities

Start with #103, then review Waterfront Toronto’s procurement, awarded-contracts, and current-opportunities pages. Determine whether this partnered corporation belongs in the archive and resolve the keyspace and terms-of-use decisions identified in #103; completion means the scope and implementation path are settled before work begins.

Written by the indexing model from the issue text.