fix: fix demo comments

Author: min

AGENTS.md

@@ -0,0 +1,34 @@
+# Repository Guidelines
+
+## Project Structure & Module Organization
+- `src/cryptoservice/`: core package with async services, storage, and models grouped by domain (clients, services, storage, utils).
+- `tests/`: pytest suite mirroring package layout; async fixtures live in `tests/__init__.py`.
+- `docs/` and `mkdocs.yml`: MkDocs-driven documentation.
+- `scripts/`: automation helpers such as `prepare_release.py` for versioning and release branches.
+- `demo/` and `examples/`: runnable usage samples; keep them in sync with public APIs when adding features.
+
+## Build, Test, and Development Commands
+- `python3 -m pip install -e .[dev-all]`: install project plus dev tools (via uv or pip).
+- `ruff format && ruff check`: format/lint code to repository standards.
+- `pytest -v --cov=src/cryptoservice`: run the async test suite with coverage details.
+- `python3 scripts/prepare_release.py <version> --auto --push`: create release branch, run tests, tag, and push once the tree is clean.
+
+## Coding Style & Naming Conventions
+- Python ≥3.10 with async-first design; prefer `async/await` and type hints everywhere.
+- Follow Ruff defaults: 120-character lines, double quotes, spaces for indentation.
+- Keep modules small and feature-focused; filenames use snake_case, classes use PascalCase, constants uppercase.
+- Run `ruff check --fix` before committing to catch security and style issues early.
+
+## Testing Guidelines
+- Tests rely on `pytest`, `pytest-asyncio`, and coverage; new code should include async tests mirroring service behavior.
+- Name test files `tests/test_*.py`; structure tests to reflect module boundaries (e.g., `services` tests in `tests/test_services.py`).
+- For regression coverage, add parametrized cases rather than duplicating fixtures; update expected artifacts in `data/` sparingly and document any large fixtures.
+
+## Commit & Pull Request Guidelines
+- Use Conventional Commits (`feat`, `fix`, `docs`, `chore`, etc.); release commits are generated by `prepare_release.py`.
+- PRs should explain motivation, link issues, and list manual verification (tests run, docs updated). Include screenshots or logs when touching demos.
+- Keep PRs focused: refactors separate from feature work; update docs/examples alongside code changes.
+
+## Security & Configuration Tips
+- Secrets live in `.env` (e.g., `BINANCE_API_KEY`, `BINANCE_API_SECRET`); never commit real credentials.
+- When adding integrations, document required environment variables in `docs/` and provide safe defaults for local runs.

CLAUDE.md

@@ -11,7 +11,7 @@ This is a Python cryptocurrency data processing package called `cryptoservice` t
 - Historical data processing and analysis
 - Database storage with SQLite
 
-The project is currently at version 1.10.0 and supports Python >=3.10,<3.13.
+The project is currently at version 1.11.1 and supports Python >=3.10,<3.13.
 
 ## Architecture
 
@@ -178,3 +178,29 @@ The project organizes data in structured directories:
 - `data/exports/`: Exported numpy arrays organized by universe, timeframe, and data type
 - `data/categories/`: Symbol category CSV files with timestamps
 - Export format: `univ_{params}/1d/{metric_type}/YYYYMMDD.npy` and `.pkl` files for symbols
+
+## Release Management
+
+The project includes a custom release script for version management:
+```bash
+# Prepare a new release (updates version, changelog, tests, commits, tags)
+python3 scripts/prepare_release.py 1.12.0 --auto --push
+
+# Options:
+# --auto: Full workflow (test, commit, tag)
+# --push: Push to remote repository
+# --skip-tests: Skip running tests
+# --skip-changelog: Skip changelog generation
+```
+
+This script:
+- Updates version in `pyproject.toml` and `src/cryptoservice/__init__.py`
+- Generates changelog entries from commit history
+- Creates release branch, commits changes, and creates git tags
+- Optionally pushes to remote repository
+
+# important-instruction-reminders
+Do what has been asked; nothing more, nothing less.
+NEVER create files unless they're absolutely necessary for achieving your goal.
+ALWAYS prefer editing an existing file to creating a new one.
+NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.

demo/define_universe.py

@@ -28,7 +28,7 @@
 T2_MONTHS = 1  # 1个月重平衡频率
 T3_MONTHS = 1  # 1个月最小合约存在时间
 # TOP_K = 160  # Top 160合约 (与 TOP_RATIO 二选一)
-TOP_RATIO = 0.1  # 选择Top 80%的合约
+TOP_RATIO = 0.1  # 选择Top 10%的合约
 DELAY_DAYS = 7  # 延迟7天
 QUOTE_ASSET = "USDT"  # 只使用USDT永续合约