🔄 changes: Case Study Contacts Csv Itrvt8#68
Draft
communityfix[bot] wants to merge 16 commits into
Draft
Conversation
🚀 Release: master ⬅️ staging
🚀 Release: master ⬅️ staging
🚀 Release: master ⬅️ staging
🚀 Release: master ⬅️ staging
🚀 Release: master ⬅️ staging
Researched public outreach contacts (email, LinkedIn, website) for the implementers behind all 64 CommunityFix case studies. One row per case study, with a confidence rating, notes, and supporting source URLs. Row 22 (Antwerp) is a placeholder pending in-progress research. https://claude.ai/code/session_01N9D1mrG7QppT3SmVTQdFKh
Replaces the placeholder with researched public contact details for the City of Antwerp environmental department. https://claude.ai/code/session_01N9D1mrG7QppT3SmVTQdFKh
One folder per case-study contact under outreach/, each with a README plus language-appropriate (FR/EN) email chains, LinkedIn notes, and contact-form messages where applicable. Benefit-framing revisions land in a follow-up commit. https://claude.ai/code/session_01N9D1mrG7QppT3SmVTQdFKh
Adds the 'helps others avoid mistakes / find what works / a better world' message to first-touch messages and a short clause to follow-ups. Partial batch; remaining folders land as the revision agents complete. https://claude.ai/code/session_01N9D1mrG7QppT3SmVTQdFKh
Final coverage pass: benefit line now present in every first-touch message and follow-up across all 63 contact folders (FR/EN). https://claude.ai/code/session_01N9D1mrG7QppT3SmVTQdFKh
mathix420
added a commit
that referenced
this pull request
Jul 1, 2026
* 🐛 fix(moderation): recover nodes stranded in pending Nodes could end up stuck `pending` with no auto-moderation, forcing a manual admin "Re-moderate" (seen in prod for issue #68 and case studies #65 / #78). Two independent causes, two fixes. 1. Trigger boundary has no safety net. `triggerModeration` fires the moderation Workflow best-effort and swallows failures; if the run is never created (transient error / missing binding) or dies before a verdict, the node sits `pending` forever with nothing to recover it. Add `review:reconcile-pending`, an hourly scheduled task that finds nodes pending > 30 min with no terminal verdict since their last edit and re-submits them to the durable Workflow. The decision-action + grace-window guards skip nodes that are deliberately pending (flagged uncertain / awaiting author info) or still in flight. 2. Case-study approval was coupled to enrichment. `curate` + `finalize` ran together under one Promise.all, so a curate/location failure threw out of the run *before* the approval committed, reverting the case study to `pending` (what stranded #65). Split it like the issue pipeline: `finalizeCaseStudy` commits the approval first, then a best-effort `enrichCaseStudy` pass (curate ∥ location, each guarded) runs after. Curation now lands as its own `curate` audit log. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * 🔧 chore(moderation): satisfy diff-scoped fallow complexity gate The two functions introduced by the previous commit tripped `fallow audit`'s new-only CRAP gate. Refactor both under threshold (no suppressions): - applyCaseStudyCurate: extract the field-cleaning into `compact` / `cleanRows` null-strippers and the embed text into `curatedCaseStudyText`, leaving the function a flat patch-builder. `Metric`/`Source`/`LinkRow` are a required key plus optionals, so stripping nulls is equivalent to the old explicit per-field reconstruction. - review:reconcile-pending: fold the two stuck-node queries into one UNION helper (`findStuckPending`) so the task callback is a short fetch → fire → log. verdict: pass · 0 introduced complexity/duplication/dead-code findings. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * 🎨 style(moderation): run formatter on pipelines.ts `vize fmt` (the CI format:check gate) reflowed the extracted `compact` helper signature. No behavior change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a comprehensive CSV file containing contact information for 65+ case study implementers across various sustainability and circular economy initiatives. The data includes outreach contacts for organizations implementing waste reduction, urban heat mitigation, reusable packaging, and community resilience programs.
Key Changes
• ✨ New Contact Database: Added
case-study-contacts.csvwith 65 rows of implementer contact data• 📊 Comprehensive Fields: Includes case study IDs, implementer details, locations, outcomes, contact organizations, personnel, roles, and communication channels
• 🌍 Global Coverage: Contacts span multiple countries including US, France, Belgium, UK, Chile, and more
• 🔍 Research Metadata: Each entry includes confidence levels, notes, and source verification
• 📧 Multi-Channel Contacts: Email addresses, LinkedIn profiles, and websites where available
• 🏛️ Diverse Organizations: Government agencies, municipalities, nonprofits, and private companies
Review Notes
Please pay attention to:
The CSV structure looks well-organized for outreach campaigns and follow-up research on sustainability program implementations.