## Summary
- Removes automated announcement posting to Threads (moving to manual cross-posting as part of social engagement strategy)
- Removes Peerlist from the manual posting reminder (moving to social engagement rather than product announcements)
- Updates system prompt and JSON schema descriptions to reflect the current set of platforms
## Test Plan
- [ ] Trigger an announcement and confirm Threads is no longer called
- [ ] Confirm the alert in the response no longer mentions Peerlist
- [ ] Confirm lint and build pass (verified locally)
✨ This issue was created with help from Hikari~ 🌸
Reviewed-on: #23
Co-authored-by: Hikari <hikari@nhcarrigan.com>
Co-committed-by: Hikari <hikari@nhcarrigan.com>
## Dependency Update
Updates **turbo** from `2.8.11` to `2.8.12`.
### Type
devDependencies
### Changelog
Updated from 2.8.11 to 2.8.12
---
✨ This PR was created by Minori, your friendly dependency updater! 🌸
Reviewed-on: #19
Reviewed-by: Naomi Carrigan <accounts@nhcarrigan.com>
Co-authored-by: Minori <minori@nhcarrigan.com>
Co-committed-by: Minori <minori@nhcarrigan.com>
## Summary
- Aligns the client with the NHCarrigan style guide (witch palette, Griffy/Kalam fonts, shared stylesheet)
- Fixes sanctions page to sort by case number descending
- Updates all Hikari image URLs to `cdn.nhcarrigan.com/hikari.png`
- Adds Support link to nav (https://support.nhcarrigan.com)
- Fixes Chat nav link to point to https://chat.nhcarrigan.com✨ This issue was created with help from Hikari~ 🌸
Reviewed-on: #21
Co-authored-by: Hikari <hikari@nhcarrigan.com>
Co-committed-by: Hikari <hikari@nhcarrigan.com>
## Summary
- Fixes the announcement API URL from `/announcement` to `/api/announcement`
- Adds three optional additional content text inputs (Parts 2–4) to the announcement modal
- The bot concatenates all non-empty content fields with double newlines before forwarding to the API
- Only the first content field and the category selector remain required
## Test Plan
- [ ] Run `/announcement` and verify the modal opens with four content fields and a category selector
- [ ] Submit with only the first content field filled — verify it sends correctly
- [ ] Submit with multiple content fields filled — verify they are concatenated in the API request
- [ ] Verify the API no longer returns HTTP 405
Reviewed-on: #20
Co-authored-by: Hikari <hikari@nhcarrigan.com>
Co-committed-by: Hikari <hikari@nhcarrigan.com>
Triggers a modal with a content text input and category select menu,
calls the announcement API, DMs generated copy as file attachments,
and replies ephemerally with the platform recap.
## Summary
- Adds `announceOnDiscourse` module to post announcements to the NHCarrigan Discourse support forum (category 16), tagged by announcement type
- Adds `chunkContent` utility to split long announcements at paragraph/line boundaries for Discord (2000 chars), Reddit (40,000 chars), and Discourse (32,000 chars); Reddit overflows chain as nested replies, Discord as sequential messages, Discourse as sequential replies
- Refactors the announcement route to run all platforms concurrently via `Promise.allSettled`, ensuring a failure on any one platform never blocks the others, with all results reported back
- Fixes generation failure response from incorrect `201` to `500`
✨ This PR was created with love from Hikari~ 🌸
Reviewed-on: #17
Co-authored-by: Hikari <hikari@nhcarrigan.com>
Co-committed-by: Hikari <hikari@nhcarrigan.com>
### Explanation
Makes my life so much easier.
### Issue
_No response_
### Attestations
- [x] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/)
- [x] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/).
- [x] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/).
### Dependencies
- [x] I have pinned the dependencies to a specific patch version.
### Style
- [x] I have run the linter and resolved any errors.
- [x] My pull request uses an appropriate title, matching the conventional commit standards.
- [x] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request.
### Tests
- [ ] My contribution adds new code, and I have added tests to cover it.
- [ ] My contribution modifies existing code, and I have updated the tests to reflect these changes.
- [ ] All new and existing tests pass locally with my changes.
- [ ] Code coverage remains at or above the configured threshold.
### Documentation
_No response_
### Versioning
Minor - My pull request introduces a new non-breaking feature.
Reviewed-on: #8
Co-authored-by: Naomi Carrigan <commits@nhcarrigan.com>
Co-committed-by: Naomi Carrigan <commits@nhcarrigan.com>
### Explanation
We can automate the heck out of announcements everywhere. Except LinkedIn, because that API looks agonising.
### Issue
_No response_
### Attestations
- [ ] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/)
- [ ] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/).
- [ ] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/).
### Dependencies
- [ ] I have pinned the dependencies to a specific patch version.
### Style
- [ ] I have run the linter and resolved any errors.
- [ ] My pull request uses an appropriate title, matching the conventional commit standards.
- [ ] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request.
### Tests
- [ ] My contribution adds new code, and I have added tests to cover it.
- [ ] My contribution modifies existing code, and I have updated the tests to reflect these changes.
- [ ] All new and existing tests pass locally with my changes.
- [ ] Code coverage remains at or above the configured threshold.
### Documentation
_No response_
### Versioning
_No response_
Reviewed-on: #6
Co-authored-by: Naomi Carrigan <commits@nhcarrigan.com>
Co-committed-by: Naomi Carrigan <commits@nhcarrigan.com>
hikari
minori
naomi