Revise README content for CivicTech Waterloo Region

[BreakableHoodie]

Updated the README to reflect current activities and resources.

[Copilot]

Pull request overview

Updates the GitHub organization profile README to better reflect CivicTech Waterloo Region’s current mission and engagement links.

Changes:

• Replaces the “standby” message with a mission/intro sentence.
• Refreshes the resource links to website, upcoming events, and Slack.

---

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

[Copilot]

The Slack URL is a shared_invite link that can expire or be revoked, which may cause the org profile link to break over time. Consider linking to a stable redirect (e.g., a civictechwr.org/slack page) or another evergreen join mechanism instead of an invite token URL.

Suggested change

	- 💬 [Join us on Slack](https://join.slack.com/t/civictechwr/shared_invite/zt-2hk4c93hv-DEIbxR_z1xKj8cZmayVHTw)
	- 💬 [Join us on Slack](https://civictechwr.org/slack)

[BreakableHoodie]

Review — PR #7: Revise README content

Thanks for the cleanup — the new intro sentence is a big improvement over the placeholder text. A few things need to be addressed before merging.

🔴 Bug (blocker)

Wrong domain for Lu.ma events.
The line added reads: - 📅 [Upcoming events](https://luma.com/civictechwr)

luma.com is Luma AI (an NVIDIA company), not the event platform. The correct domain is lu.ma:

- 📅 [Upcoming events](https://lu.ma/civictechwr)

PR #6 gets this right — worth keeping consistent across the repo.

🟡 Regression — active-projects board link dropped

The in-progress projects board link was removed. For visitors landing on the org page, that's the fastest path to finding something to contribute to. Suggest restoring it:

- 🔨 [Active projects](https://github.com/orgs/CivicTechWR/projects/10/views/6?sliceBy%5Bvalue%5D=In+progress)

🟡 Slack invite token mismatch

The token in this PR (zt-2hk4c93hv-...) differs from the one in PR #6 (zt-2ldijjy0i-...). Slack invite links expire — please verify which one is current before merging.

⚠️ Merge conflict ahead

PR #6 also modifies profile/README.md. Recommend merging #6 first (it's older and more comprehensive), then rebasing this branch on top — you can fold the lu.ma fix into the rebase at the same time.