wintersolve 0.3.0__tar.gz

wintersolve-0.3.0/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2026 WinterSolve Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+

wintersolve-0.3.0/PKG-INFO

@@ -0,0 +1,263 @@
+Metadata-Version: 2.4
+Name: wintersolve
+Version: 0.3.0
+Summary: Offline-first repository intelligence: understand, debug, document, and review any codebase from the terminal.
+Author: WinterSolve Contributors
+Maintainer: Harshit Kumar (harshitkrhere)
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/harshitkrhere/WinterSolve
+Project-URL: Repository, https://github.com/harshitkrhere/WinterSolve
+Project-URL: Documentation, https://github.com/harshitkrhere/WinterSolve/tree/main/docs
+Project-URL: Changelog, https://github.com/harshitkrhere/WinterSolve/blob/main/CHANGELOG.md
+Project-URL: Issues, https://github.com/harshitkrhere/WinterSolve/issues
+Keywords: cli,developer-tools,codebase-analysis,repository-analysis,static-analysis,security-scanning,secret-detection,onboarding,documentation,code-review,offline,repo-brain
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Documentation
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Security
+Classifier: Topic :: Utilities
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: typer>=0.12
+Requires-Dist: rich>=13.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: pytest-cov>=5.0; extra == "dev"
+Requires-Dist: mypy>=1.10; extra == "dev"
+Requires-Dist: ruff==0.16.8; extra == "dev"
+Requires-Dist: bandit>=1.7; extra == "dev"
+Requires-Dist: pre-commit>=3.7; extra == "dev"
+Provides-Extra: security
+Requires-Dist: bandit>=1.7; extra == "security"
+Provides-Extra: ai
+Requires-Dist: openai>=1.0; extra == "ai"
+Requires-Dist: anthropic>=0.18; extra == "ai"
+Provides-Extra: all
+Requires-Dist: bandit>=1.7; extra == "all"
+Requires-Dist: openai>=1.0; extra == "all"
+Requires-Dist: anthropic>=0.18; extra == "all"
+Dynamic: license-file
+
+<h1 align="center">WinterSolve</h1>
+
+<p align="center">
+  <strong>Understand any repository from the terminal. Offline, in seconds, no account.</strong>
+</p>
+
+<p align="center">
+  <a href="https://github.com/harshitkrhere/WinterSolve/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/harshitkrhere/WinterSolve/actions/workflows/ci.yml/badge.svg"></a>
+  <a href="https://github.com/harshitkrhere/WinterSolve/actions/workflows/codeql.yml"><img alt="CodeQL" src="https://github.com/harshitkrhere/WinterSolve/actions/workflows/codeql.yml/badge.svg"></a>
+  <a href="LICENSE"><img alt="MIT License" src="https://img.shields.io/badge/license-MIT-green.svg"></a>
+  <img alt="Python 3.10+" src="https://img.shields.io/badge/python-3.10%2B-blue.svg">
+  <a href="https://github.com/astral-sh/ruff"><img alt="Ruff" src="https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json"></a>
+  <img alt="mypy strict" src="https://img.shields.io/badge/mypy-strict-blue.svg">
+</p>
+
+You open a repository you have never seen. What is it, how do you run it, where
+are the tests, is anything risky, what should you look at first?
+
+`wintersolve brain .` answers all of that in one report: languages and stack,
+source and test layout, the commands you need, an architecture map, a security
+and privacy check, and a short list of risks and next actions. It reads files;
+it never phones home. Output is plain text you can paste into an issue,
+Markdown for a wiki, or JSON for your tooling.
+
+## Try it
+
+```bash
+pipx install wintersolve        # or: python -m pip install wintersolve
+cd path/to/any/project
+wintersolve brain .
+```
+
+Not on PyPI yet, or want the latest commit? `pipx install git+https://github.com/harshitkrhere/WinterSolve.git`
+
+## What you get
+
+Real output from running WinterSolve on its own repository (lightly trimmed;
+the [full report](examples/sample-reports/wintersolve-repo-brain.md) is in
+`examples/`):
+
+```text
+WinterSolve Repo Brain
+======================
+Project: WinterSolve
+Offline mode: yes
+
+Languages:
+  - Python: 38
+  - Markdown: 27
+  - PowerShell: 2
+Detected stack:
+  - GitHub Actions
+  - Python package
+  - pre-commit
+Source layout:
+  - src
+  - src/wintersolve
+  - src/wintersolve/modules
+  - src/wintersolve/providers
+  - src/wintersolve/workflows
+Documentation health:
+  - README contains the expected core sections.
+  - Core open-source hygiene files are present.
+Detected commands:
+  - install editable: `python -m pip install -e .` (pyproject.toml, medium)
+  - test: `python -m pytest` (pyproject.toml, medium)
+  - pipx: `pipx install wintersolve` (README.md, medium)
+Architecture map:
+  - docs: Project documentation; notable: docs/ARCHITECTURE.md, docs/COMMANDS.md, ...
+  - src: Application or library source code; notable: src/wintersolve/cli.py, ...
+  - tests: Automated tests; notable: tests/conftest.py, tests/test_cli.py, ...
+Security and privacy:
+  - Status: clear
+  - Files checked: 83
+  - Secret-like values are redacted before they appear in any report.
+  - Bandit ran on Python files (medium and high severity): 0 issue(s).
+Risks:
+  - None detected
+Next actions:
+  - Run the detected test command before making changes.
+  - Use `wintersolve explain <file>` on the most important source files.
+  - Use the architecture map as the first contributor onboarding guide.
+```
+
+On a repository with problems, the same report names them: a committed AWS
+key (redacted in the output), `eval()` on user input, SQL built from request
+data, a missing test directory, a README with no install section.
+
+## Commands
+
+| Command | What it does | Formats |
+| --- | --- | --- |
+| `wintersolve brain .` | Full project intelligence report (everything below, composed). | text, markdown, json |
+| `wintersolve scan .` | Quick health check from file names and marker files only. | text, markdown, json |
+| `wintersolve explain FILE` | What one file is, what it defines, what it depends on. | text |
+| `wintersolve debug --text "..."` | Likely causes and next steps for an error or stack trace. Also reads stdin. | text |
+| `wintersolve docs .` | Missing README sections and hygiene files; `--draft-readme` for a skeleton. | text |
+| `wintersolve review .` | Turns your uncommitted changes into review risks and a checklist. | text |
+
+Every command exits `0` on success, `1` if the analysis failed, and `2` for
+usage errors or targets that cannot be analyzed. Full reference:
+[docs/COMMANDS.md](docs/COMMANDS.md).
+
+A few things people do with it:
+
+```bash
+wintersolve brain . --format markdown --output REPO_BRAIN.md     # onboarding doc
+wintersolve brain . --format json | jq '.security.findings'       # feed a script
+pytest 2>&1 | wintersolve debug                                   # explain a failure
+wintersolve brain ~/code/some-repo --no-bandit                    # fastest possible
+```
+
+## Why WinterSolve
+
+- **Offline by default.** No API keys, no accounts, no telemetry, no update
+  checks. Safe to run on private code.
+- **Fast on real repositories.** One filesystem walk that prunes `node_modules`,
+  virtual environments, and build output before descending.
+- **Honest.** Heuristics are labelled as heuristics. The security section says
+  exactly which checks ran, and severity is earned: `high` only for unambiguous
+  token formats, never for "this line mentions a password".
+- **Structured.** Plain text that pastes cleanly, Markdown for wikis, JSON with
+  a `schema_version` for tools. Same commit, same report, every time.
+- **Small.** Two runtime dependencies (`typer`, `rich`), plain dataclasses,
+  strict typing, tests that run in seconds.
+
+## Use it in CI
+
+```yaml
+- run: python -m pip install wintersolve
+- run: wintersolve brain . --format markdown --output repo-brain.md
+- run: cat repo-brain.md >> "$GITHUB_STEP_SUMMARY"
+```
+
+The report shows up in the Actions job summary. A drop-in workflow and the
+recipe for failing a build on high-severity findings are in
+[docs/INTEGRATIONS.md](docs/INTEGRATIONS.md).
+
+## Installation
+
+| Method | Command |
+| --- | --- |
+| pipx (recommended) | `pipx install wintersolve` |
+| pip | `python -m pip install wintersolve` |
+| latest from GitHub | `pipx install git+https://github.com/harshitkrhere/WinterSolve.git` |
+| with Bandit for deeper Python checks | `pipx install "wintersolve[security]"` |
+
+Python 3.10 or newer, on Linux, macOS, or Windows. Details and troubleshooting:
+[docs/INSTALLATION.md](docs/INSTALLATION.md).
+
+## How it works
+
+```text
+cli.py  ->  modules/*.py (one analyzer each)  ->  frozen dataclasses  ->  report.py
+```
+
+Analyzers never print and never touch the network. `brain` calls all of them
+and composes one report. Adding an analyzer is a module, a renderer, a
+few lines in the CLI, and a test. See [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md).
+
+## What it is not
+
+WinterSolve is not an AI assistant and does not need one. It will not write your
+code, and its security scan is a first pass, not an audit. There is an optional
+provider interface for people who want to build AI features on top of redacted
+reports; the CLI never calls it.
+
+## Security and privacy
+
+WinterSolve reads the directory you point it at (skipping `.git`, caches,
+virtual environments, and dependency folders), runs `git status` for `review`,
+and optionally runs Bandit. That is the complete list. Anything that looks like
+a credential is redacted before it reaches a report, and `explain` refuses
+files outside the project root. Details: [docs/SECURITY_MODEL.md](docs/SECURITY_MODEL.md).
+Found a problem in WinterSolve itself? Please follow [SECURITY.md](SECURITY.md).
+
+## Development and tests
+
+```bash
+git clone https://github.com/harshitkrhere/WinterSolve.git && cd WinterSolve
+python -m venv .venv && source .venv/bin/activate      # Windows: .venv\Scripts\Activate.ps1
+python -m pip install -e ".[dev]"
+ruff check . && ruff format --check . && mypy && pytest
+```
+
+That last line is the whole quality gate, and it is exactly what CI runs on
+Linux, macOS, and Windows across Python 3.10 to 3.14. Tests use temporary
+fixture projects and finish in seconds.
+
+## Contributing
+
+Small contributions are the best ones here: a stack marker WinterSolve misses,
+a command it should have found, an error message it does not recognise, a
+false positive it should not raise. Each is a few lines plus a test.
+
+Start with [CONTRIBUTING.md](CONTRIBUTING.md), or [BEGINNER.md](BEGINNER.md)
+for a guided first week. Ideas and questions go in
+[Discussions](https://github.com/harshitkrhere/WinterSolve/discussions);
+bugs in [Issues](https://github.com/harshitkrhere/WinterSolve/issues).
+
+## Status
+
+Version 0.3.0, alpha. The command set is stable; report wording may still
+change between minor versions, and the JSON `schema_version` is bumped for any
+breaking change. See the [changelog](CHANGELOG.md) and the [roadmap](ROADMAP.md).
+
+If WinterSolve saved you time, a star helps other people find it.
+
+## License
+
+[MIT](LICENSE).

wintersolve-0.3.0/README.md

@@ -0,0 +1,211 @@
+<h1 align="center">WinterSolve</h1>
+
+<p align="center">
+  <strong>Understand any repository from the terminal. Offline, in seconds, no account.</strong>
+</p>
+
+<p align="center">
+  <a href="https://github.com/harshitkrhere/WinterSolve/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/harshitkrhere/WinterSolve/actions/workflows/ci.yml/badge.svg"></a>
+  <a href="https://github.com/harshitkrhere/WinterSolve/actions/workflows/codeql.yml"><img alt="CodeQL" src="https://github.com/harshitkrhere/WinterSolve/actions/workflows/codeql.yml/badge.svg"></a>
+  <a href="LICENSE"><img alt="MIT License" src="https://img.shields.io/badge/license-MIT-green.svg"></a>
+  <img alt="Python 3.10+" src="https://img.shields.io/badge/python-3.10%2B-blue.svg">
+  <a href="https://github.com/astral-sh/ruff"><img alt="Ruff" src="https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json"></a>
+  <img alt="mypy strict" src="https://img.shields.io/badge/mypy-strict-blue.svg">
+</p>
+
+You open a repository you have never seen. What is it, how do you run it, where
+are the tests, is anything risky, what should you look at first?
+
+`wintersolve brain .` answers all of that in one report: languages and stack,
+source and test layout, the commands you need, an architecture map, a security
+and privacy check, and a short list of risks and next actions. It reads files;
+it never phones home. Output is plain text you can paste into an issue,
+Markdown for a wiki, or JSON for your tooling.
+
+## Try it
+
+```bash
+pipx install wintersolve        # or: python -m pip install wintersolve
+cd path/to/any/project
+wintersolve brain .
+```
+
+Not on PyPI yet, or want the latest commit? `pipx install git+https://github.com/harshitkrhere/WinterSolve.git`
+
+## What you get
+
+Real output from running WinterSolve on its own repository (lightly trimmed;
+the [full report](examples/sample-reports/wintersolve-repo-brain.md) is in
+`examples/`):
+
+```text
+WinterSolve Repo Brain
+======================
+Project: WinterSolve
+Offline mode: yes
+
+Languages:
+  - Python: 38
+  - Markdown: 27
+  - PowerShell: 2
+Detected stack:
+  - GitHub Actions
+  - Python package
+  - pre-commit
+Source layout:
+  - src
+  - src/wintersolve
+  - src/wintersolve/modules
+  - src/wintersolve/providers
+  - src/wintersolve/workflows
+Documentation health:
+  - README contains the expected core sections.
+  - Core open-source hygiene files are present.
+Detected commands:
+  - install editable: `python -m pip install -e .` (pyproject.toml, medium)
+  - test: `python -m pytest` (pyproject.toml, medium)
+  - pipx: `pipx install wintersolve` (README.md, medium)
+Architecture map:
+  - docs: Project documentation; notable: docs/ARCHITECTURE.md, docs/COMMANDS.md, ...
+  - src: Application or library source code; notable: src/wintersolve/cli.py, ...
+  - tests: Automated tests; notable: tests/conftest.py, tests/test_cli.py, ...
+Security and privacy:
+  - Status: clear
+  - Files checked: 83
+  - Secret-like values are redacted before they appear in any report.
+  - Bandit ran on Python files (medium and high severity): 0 issue(s).
+Risks:
+  - None detected
+Next actions:
+  - Run the detected test command before making changes.
+  - Use `wintersolve explain <file>` on the most important source files.
+  - Use the architecture map as the first contributor onboarding guide.
+```
+
+On a repository with problems, the same report names them: a committed AWS
+key (redacted in the output), `eval()` on user input, SQL built from request
+data, a missing test directory, a README with no install section.
+
+## Commands
+
+| Command | What it does | Formats |
+| --- | --- | --- |
+| `wintersolve brain .` | Full project intelligence report (everything below, composed). | text, markdown, json |
+| `wintersolve scan .` | Quick health check from file names and marker files only. | text, markdown, json |
+| `wintersolve explain FILE` | What one file is, what it defines, what it depends on. | text |
+| `wintersolve debug --text "..."` | Likely causes and next steps for an error or stack trace. Also reads stdin. | text |
+| `wintersolve docs .` | Missing README sections and hygiene files; `--draft-readme` for a skeleton. | text |
+| `wintersolve review .` | Turns your uncommitted changes into review risks and a checklist. | text |
+
+Every command exits `0` on success, `1` if the analysis failed, and `2` for
+usage errors or targets that cannot be analyzed. Full reference:
+[docs/COMMANDS.md](docs/COMMANDS.md).
+
+A few things people do with it:
+
+```bash
+wintersolve brain . --format markdown --output REPO_BRAIN.md     # onboarding doc
+wintersolve brain . --format json | jq '.security.findings'       # feed a script
+pytest 2>&1 | wintersolve debug                                   # explain a failure
+wintersolve brain ~/code/some-repo --no-bandit                    # fastest possible
+```
+
+## Why WinterSolve
+
+- **Offline by default.** No API keys, no accounts, no telemetry, no update
+  checks. Safe to run on private code.
+- **Fast on real repositories.** One filesystem walk that prunes `node_modules`,
+  virtual environments, and build output before descending.
+- **Honest.** Heuristics are labelled as heuristics. The security section says
+  exactly which checks ran, and severity is earned: `high` only for unambiguous
+  token formats, never for "this line mentions a password".
+- **Structured.** Plain text that pastes cleanly, Markdown for wikis, JSON with
+  a `schema_version` for tools. Same commit, same report, every time.
+- **Small.** Two runtime dependencies (`typer`, `rich`), plain dataclasses,
+  strict typing, tests that run in seconds.
+
+## Use it in CI
+
+```yaml
+- run: python -m pip install wintersolve
+- run: wintersolve brain . --format markdown --output repo-brain.md
+- run: cat repo-brain.md >> "$GITHUB_STEP_SUMMARY"
+```
+
+The report shows up in the Actions job summary. A drop-in workflow and the
+recipe for failing a build on high-severity findings are in
+[docs/INTEGRATIONS.md](docs/INTEGRATIONS.md).
+
+## Installation
+
+| Method | Command |
+| --- | --- |
+| pipx (recommended) | `pipx install wintersolve` |
+| pip | `python -m pip install wintersolve` |
+| latest from GitHub | `pipx install git+https://github.com/harshitkrhere/WinterSolve.git` |
+| with Bandit for deeper Python checks | `pipx install "wintersolve[security]"` |
+
+Python 3.10 or newer, on Linux, macOS, or Windows. Details and troubleshooting:
+[docs/INSTALLATION.md](docs/INSTALLATION.md).
+
+## How it works
+
+```text
+cli.py  ->  modules/*.py (one analyzer each)  ->  frozen dataclasses  ->  report.py
+```
+
+Analyzers never print and never touch the network. `brain` calls all of them
+and composes one report. Adding an analyzer is a module, a renderer, a
+few lines in the CLI, and a test. See [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md).
+
+## What it is not
+
+WinterSolve is not an AI assistant and does not need one. It will not write your
+code, and its security scan is a first pass, not an audit. There is an optional
+provider interface for people who want to build AI features on top of redacted
+reports; the CLI never calls it.
+
+## Security and privacy
+
+WinterSolve reads the directory you point it at (skipping `.git`, caches,
+virtual environments, and dependency folders), runs `git status` for `review`,
+and optionally runs Bandit. That is the complete list. Anything that looks like
+a credential is redacted before it reaches a report, and `explain` refuses
+files outside the project root. Details: [docs/SECURITY_MODEL.md](docs/SECURITY_MODEL.md).
+Found a problem in WinterSolve itself? Please follow [SECURITY.md](SECURITY.md).
+
+## Development and tests
+
+```bash
+git clone https://github.com/harshitkrhere/WinterSolve.git && cd WinterSolve
+python -m venv .venv && source .venv/bin/activate      # Windows: .venv\Scripts\Activate.ps1
+python -m pip install -e ".[dev]"
+ruff check . && ruff format --check . && mypy && pytest
+```
+
+That last line is the whole quality gate, and it is exactly what CI runs on
+Linux, macOS, and Windows across Python 3.10 to 3.14. Tests use temporary
+fixture projects and finish in seconds.
+
+## Contributing
+
+Small contributions are the best ones here: a stack marker WinterSolve misses,
+a command it should have found, an error message it does not recognise, a
+false positive it should not raise. Each is a few lines plus a test.
+
+Start with [CONTRIBUTING.md](CONTRIBUTING.md), or [BEGINNER.md](BEGINNER.md)
+for a guided first week. Ideas and questions go in
+[Discussions](https://github.com/harshitkrhere/WinterSolve/discussions);
+bugs in [Issues](https://github.com/harshitkrhere/WinterSolve/issues).
+
+## Status
+
+Version 0.3.0, alpha. The command set is stable; report wording may still
+change between minor versions, and the JSON `schema_version` is bumped for any
+breaking change. See the [changelog](CHANGELOG.md) and the [roadmap](ROADMAP.md).
+
+If WinterSolve saved you time, a star helps other people find it.
+
+## License
+
+[MIT](LICENSE).

wintersolve-0.3.0/pyproject.toml

@@ -0,0 +1,161 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "wintersolve"
+dynamic = ["version"]
+description = "Offline-first repository intelligence: understand, debug, document, and review any codebase from the terminal."
+readme = "README.md"
+requires-python = ">=3.10"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [{ name = "WinterSolve Contributors" }]
+maintainers = [{ name = "Harshit Kumar (harshitkrhere)" }]
+keywords = [
+  "cli",
+  "developer-tools",
+  "codebase-analysis",
+  "repository-analysis",
+  "static-analysis",
+  "security-scanning",
+  "secret-detection",
+  "onboarding",
+  "documentation",
+  "code-review",
+  "offline",
+  "repo-brain",
+]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Environment :: Console",
+  "Intended Audience :: Developers",
+  "Operating System :: OS Independent",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.10",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Programming Language :: Python :: 3.14",
+  "Topic :: Software Development",
+  "Topic :: Software Development :: Documentation",
+  "Topic :: Software Development :: Quality Assurance",
+  "Topic :: Security",
+  "Topic :: Utilities",
+  "Typing :: Typed",
+]
+dependencies = [
+  "typer>=0.12",
+  "rich>=13.0",
+]
+
+[project.optional-dependencies]
+# Everything needed to run the quality gates locally (same as CI).
+dev = [
+  "pytest>=8.0",
+  "pytest-cov>=5.0",
+  "mypy>=1.10",
+  "ruff==0.16.8",  # pinned so local lint matches CI; Dependabot keeps it current
+  "bandit>=1.7",
+  "pre-commit>=3.7",
+]
+# Deeper Python static analysis inside `wintersolve brain`. Optional: the
+# heuristic scanner works without it, and the report says which one ran.
+security = ["bandit>=1.7"]
+# Client libraries for the optional AI provider examples. Never required.
+ai = ["openai>=1.0", "anthropic>=0.18"]
+all = ["bandit>=1.7", "openai>=1.0", "anthropic>=0.18"]
+
+[project.scripts]
+wintersolve = "wintersolve.cli:main"
+
+[project.urls]
+Homepage = "https://github.com/harshitkrhere/WinterSolve"
+Repository = "https://github.com/harshitkrhere/WinterSolve"
+Documentation = "https://github.com/harshitkrhere/WinterSolve/tree/main/docs"
+Changelog = "https://github.com/harshitkrhere/WinterSolve/blob/main/CHANGELOG.md"
+Issues = "https://github.com/harshitkrhere/WinterSolve/issues"
+
+[tool.setuptools.dynamic]
+version = { attr = "wintersolve.__version__" }
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+wintersolve = ["py.typed"]
+
+# ---------------------------------------------------------------------------
+# Quality tooling. `pip install -e ".[dev]"` gives you everything below.
+# ---------------------------------------------------------------------------
+
+[tool.ruff]
+target-version = "py310"
+line-length = 100
+src = ["src", "tests"]
+
+[tool.ruff.lint]
+select = [
+  "E",    # pycodestyle errors
+  "W",    # pycodestyle warnings
+  "F",    # pyflakes
+  "I",    # isort
+  "B",    # flake8-bugbear
+  "UP",   # pyupgrade
+  "C4",   # flake8-comprehensions
+  "DTZ",  # flake8-datetimez
+  "T10",  # flake8-debugger
+  "PTH",  # flake8-use-pathlib
+  "ERA",  # eradicate (commented-out code)
+  "PL",   # pylint
+  "TRY",  # tryceratops
+  "SIM",  # flake8-simplify
+  "RUF",  # ruff-specific rules
+  "ARG",  # unused arguments
+]
+ignore = [
+  "TRY003",  # Long messages in exceptions are fine for a CLI.
+  "PLR0913", # Analyzer functions legitimately take several inputs.
+]
+
+[tool.ruff.lint.per-file-ignores]
+"tests/**" = ["PLR2004"] # Magic numbers in assertions are readable.
+
+[tool.ruff.lint.isort]
+known-first-party = ["wintersolve"]
+
+[tool.ruff.format]
+quote-style = "double"
+indent-style = "space"
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "--strict-markers --strict-config -ra"
+filterwarnings = ["error::DeprecationWarning:wintersolve.*"]
+
+# No python_version pin: CI runs mypy on every supported interpreter, and a pin
+# makes mypy choke on third-party stubs that use newer syntax.
+[tool.mypy]
+strict = true
+warn_unreachable = true
+show_error_codes = true
+files = ["src/wintersolve", "tests"]
+
+# The AI SDKs are optional extras: treat them as opaque whether or not they
+# happen to be installed, so type checking gives the same answer everywhere.
+[[tool.mypy.overrides]]
+module = ["openai", "openai.*", "anthropic", "anthropic.*", "numpy", "numpy.*"]
+ignore_missing_imports = true
+follow_imports = "skip"
+
+[tool.coverage.run]
+source = ["wintersolve"]
+branch = true
+
+[tool.coverage.report]
+show_missing = true
+exclude_lines = [
+  "pragma: no cover",
+  "if TYPE_CHECKING:",
+  "if __name__ == .__main__.:",
+]

wintersolve-0.3.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

wintersolve-0.3.0/src/wintersolve/__init__.py

@@ -0,0 +1,13 @@
+"""WinterSolve: offline-first repository intelligence for developers.
+
+The public entry points are the ``wintersolve`` command (see ``wintersolve.cli``)
+and the analyzer functions in ``wintersolve.modules``, which return plain
+dataclasses you can render or serialise however you like.
+"""
+
+from wintersolve.logging_config import configure_logging, get_logger, set_log_level
+
+# Single source of truth for the version; pyproject.toml reads it at build time.
+__version__ = "0.3.0"
+
+__all__ = ["__version__", "configure_logging", "get_logger", "set_log_level"]

wintersolve-0.3.0/src/wintersolve/__main__.py

@@ -0,0 +1,6 @@
+"""Allow ``python -m wintersolve`` as an alternative to the ``wintersolve`` script."""
+
+from wintersolve.cli import main
+
+if __name__ == "__main__":
+    main()