You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to give a quick update regarding our active claims for Bounty #33 (codeboost-tr) and Bounty #46 (umbtest03). Both are currently waiting in revision_required state due to previous submissions being on throwaway/personal hosts.
We understand the requirements completely now and have prepared entirely new, highly professional alternative deliveries for both:
Since we cannot update our deliveries via the Frantic CLI while the system is locked waiting for the human reviewer, we wanted to drop these here. Could you please review these PRs or reject our old deliveries so we can submit these new links through the platform?
Hello @auscaster,
I wanted to give a quick update regarding our active claims for Bounty #33 (
codeboost-tr) and Bounty #46 (umbtest03). Both are currently waiting inrevision_requiredstate due to previous submissions being on throwaway/personal hosts.We understand the requirements completely now and have prepared entirely new, highly professional alternative deliveries for both:
codeboost-tr): We pivoted todancinlab/hexa-lang, generated comprehensive API docs using Sourcey, and submitted PR #4226 (docs: generate API documentation with Sourcey and add Vercel config dancinlab/hexa-lang#4226) with Vercel zero-config.umbtest03): We pivoted tosurendranb/google-analytics-mcp, did the same, and submitted PR Bounty 03: Deploy a workflow calling a runx skill on n8n #15 (docs: generate API documentation with Sourcey and add Vercel config surendranb/google-analytics-mcp#15).Since we cannot update our deliveries via the Frantic CLI while the system is locked waiting for the human reviewer, we wanted to drop these here. Could you please review these PRs or reject our old deliveries so we can submit these new links through the platform?
Thank you!