api: add CSV include_header flag + tests

[zensgit]

Summary

• Add include_header flag to CSV export (POST/GET)
• Core: add CsvExportConfig::with_include_header builder
• Tests: GET/POST include_header=false removes header
• Docs: README updates and cURL example

Testing

• Local: SQLX_OFFLINE=true cargo test --no-run (API)
• CI: API clippy + SQLx check expected green; jive-core build remains gated off for core_export

Notes

• core_export builds will still fail due to known jive-core issues; CI avoids enabling it.

[gemini-code-assist]

Summary of Changes

Hello @zensgit, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the API's CSV export capabilities by introducing a configurable include_header flag, allowing for more flexible data output. It also addresses critical API compilation issues, refines feature gating for CSV exports, and significantly improves the CI pipeline's diagnostic capabilities for SQLx. Additionally, it integrates new developer tooling and project maintenance configurations to streamline development workflows and ensure code quality.

Highlights

• CSV Export Functionality: Introduced an include_header flag for CSV exports (both POST and GET API endpoints) and added a corresponding with_include_header builder to CsvExportConfig in jive-core. This allows clients to control whether the CSV output includes a header row.
• API Stability & Feature Gating: Resolved API compile errors related to Option handling within currency modules and implemented feature gating for CSV streaming export under the core_export flag, ensuring consistent behavior with POST exports and preventing errors when the core path is active.
• CI & Developer Tooling Enhancements: Improved CI debuggability by configuring SQLx offline cache diffs to be uploaded as artifacts upon prepare --check failures. A new pre-commit Git hook was added to automate API linting (SQLx check + Clippy), and the Makefile was updated to support this and adjust jive-core build/test commands with specific feature flags.
• Project Configuration & Documentation: New project configurations were added, including .github/CODEOWNERS for streamlined code review assignments and .github/dependabot.yml for automated dependency updates. The AGENTS.md file was updated with comprehensive details on CSV export gating, SQLx metadata, feature tiers, and API developer shortcuts.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[Copilot]

Pull Request Overview

This pull request appears to add a CSV include_header flag functionality to the API with corresponding tests, documentation updates, and cURL examples. The PR adds a builder method for CSV export configuration and includes GET/POST endpoints that support the include_header parameter to control whether the header row is included in CSV exports.

Key changes include:

• Core functionality for CsvExportConfig::with_include_header builder
• API endpoint modifications to support include_header parameter
• Test coverage for both GET and POST scenarios with include_header=false
• Documentation updates and cURL examples

Reviewed Changes

Copilot reviewed 76 out of 445 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
TEST_TAG_SERVICE (2).md	Test documentation for tag management service implementation
TEST_SUMMARY_REPORT (2).md	Comprehensive test summary for 12 core services
TEST_SCHEDULED_TRANSACTION_SERVICE (2).md	Test report for scheduled transaction service
TEST_RULE_SERVICE (2).md	Test documentation for rule engine service
TEST_REPORT_SERVICE (2).md	Test report for report generation service
TEST_PAYEE_SERVICE (2).md	Test documentation for payee management service
TEST_NOTIFICATION_SERVICE (2).md	Test report for notification management service
TEST_BUDGET_SERVICE (2).md	Test documentation for budget management service
TECHNICAL_IMPLEMENTATION_REPORT (2).md	Technical architecture and implementation details
SERVICES_TEST_SUMMARY (2).md	Summary of all service testing results
README.md	Added CI badge and updated development instructions
QUICK_FIX_FLUTTER (2).md	Flutter environment setup and troubleshooting guide
PR_MERGE_REPORT_21_22_2025-09-19.md	Detailed report of PR #21 and #22 merges
PR_MERGE_REPORT_2025-09-19.md	PR #20 merge analysis and results
PR_DESCRIPTIONS/*.md	Multiple PR description templates and documentation
PHASE__REPORT.md	Various phase reports and progress tracking documents
Makefile	Updated build commands and added new helper targets
MAYBE_TO_JIVE_CONVERSION_COMPLETE (2).md	Complete conversion summary report

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

[nitpick] The CI badge URL points to the 'ci.yml' workflow, but the link text says 'Core CI (Strict)'. Consider updating the text to be more descriptive of what this badge represents, such as 'CI Status' or match the actual workflow name.

Suggested change

	[](https://github.com/zensgit/jive-flutter-rust/actions/workflows/ci.yml)
	[](https://github.com/zensgit/jive-flutter-rust/actions/workflows/ci.yml)

[Copilot]

[nitpick] The Makefile now includes '--no-default-features --features server' in multiple targets. Consider defining these flags as a variable at the top of the Makefile to avoid repetition and make it easier to maintain.

[Copilot]

[nitpick] The db-seed target uses '|| true' to ignore failures, which might mask actual errors. Consider checking if this is the intended behavior or if specific error handling would be more appropriate.

Suggested change

	@cd jive-api && ./scripts/migrate_local.sh || true
	@cd jive-api && ./scripts/migrate_local.sh

[gemini-code-assist]

Code Review

This pull request's title and description suggest a small feature addition for CSV exports, but the actual changes are a massive collection of unrelated items, including new CI/CD configurations, developer tooling, and a very large number of auto-generated reports and design documents (many in Chinese). This makes the PR impossible to review effectively and violates the principle of small, focused pull requests.

The most critical issue is the addition of dozens of report and documentation files. These are project artifacts, not source code, and should not be committed to the main repository. They bloat the codebase and pollute the git history.

I strongly recommend closing this PR. The useful changes (like the pre-commit hook, Makefile improvements, and CI configurations) should be extracted into separate, well-described pull requests. The documentation and report files should be stored in a more appropriate location, such as a wiki or a project management tool.

[gemini-code-assist]

This file, along with the numerous other report and documentation files added in this PR, should not be committed to the source code repository. These are project artifacts, not source code. Committing them pollutes the git history, makes the repository difficult to navigate, and unnecessarily increases its size. Such documents should be stored in a project management tool, a wiki, or a separate documentation repository.

[gemini-code-assist]

This CODEOWNERS file is overly verbose and difficult to maintain. Since all paths are assigned to the same owner (@huazhou), a single line * @huazhou would have the same effect and be much cleaner. The current file adds a lot of noise without providing any additional granularity in ownership.

* @huazhou

[gemini-code-assist]

The db-seed target's implementation is a bit misleading. It echoes '填充测试数据' (Populate test data), but the command only runs migrations. The subsequent echo suggests a manual SQL execution for creating a superadmin, which isn't really 'seeding' in a general sense. If the goal is to seed the database with test data, this target should execute a dedicated seed script. If it's just for migrations and admin creation, the name and message should be updated for clarity.