chore: add .github/FUNDING.yml — GitHub Sponsors

[satyakwok]

Adds GitHub Sponsors funding metadata so the "Sponsor" button surfaces on this repo. Operator's sponsor profile is now active.

Summary by CodeRabbit

• Chores
  • Enabled GitHub sponsorship support for the project.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds GitHub Sponsors funding metadata to the repository by configuring .github/FUNDING.yml with the sponsor handle satyakwok. This enables the GitHub Sponsors button on the repository.

Changes

GitHub Sponsor Configuration

Layer / File(s)	Summary
GitHub sponsor handle configuration .github/FUNDING.yml	GitHub Sponsors funding metadata is configured with the satyakwok sponsor account handle.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐰 A config so simple, a sponsor so sweet,
One line added makes the gift complete,
Satyakwok's name now shines in the light,
Supporting the work from morning to night! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description explains the purpose (surfacing Sponsor button) but omits the required Test plan and Related sections from the template.	Add a Test plan section with steps to verify the Sponsor button appears, and a Related section linking any relevant issues or documentation.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding a GitHub Sponsors funding configuration file with the operator's sponsor profile.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/funding-yml

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

.github/FUNDING.yml (1)

1-1: 💤 Low value

Username exists on GitHub. The configuration uses valid YAML syntax; for a single sponsor, the scalar format github: satyakwok is more idiomatic than the array format, though both work correctly.

✨ Optional: Use scalar syntax for single sponsor

-github: [satyakwok]
+github: satyakwok

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/FUNDING.yml at line 1, The FUNDING.yml currently lists the GitHub
sponsor as an array ("github: [satyakwok]"); change it to the scalar form by
replacing the array with a single scalar value for the github key (i.e., use
github: satyakwok) so the file remains valid YAML but uses the more idiomatic
scalar syntax for a single sponsor.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In @.github/FUNDING.yml:
- Line 1: The FUNDING.yml currently lists the GitHub sponsor as an array
("github: [satyakwok]"); change it to the scalar form by replacing the array
with a single scalar value for the github key (i.e., use github: satyakwok) so
the file remains valid YAML but uses the more idiomatic scalar syntax for a
single sponsor.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e55d2ba4-d2dd-49e5-88bf-a0f4a81a2e52

📥 Commits

Reviewing files that changed from the base of the PR and between 8098844 and 9f62d2f.

📒 Files selected for processing (1)

• .github/FUNDING.yml