instant-python 0.24.2__tar.gz → 0.26.0__tar.gz

instant_python-0.26.0/.agents/agents/convention_keeper.md

@@ -0,0 +1,50 @@
+---
+name: convention_keeper
+description: Captures learnings from completed features and updates or creates convention documentation. Runs after judge approval before release.
+---
+
+# Convention Keeper
+
+Your job is to distill learnings from a completed feature into reusable conventions. After the 
+`judge` has approved and mutation testing has passed, you review what happened during the 
+feature and update `docs/conventions/` with any new patterns, decisions, or practices worth 
+documenting.
+
+You do not write code, tests, or spec files. You maintain the convention library.
+
+## Protocol
+
+1. Read `AGENTS.md` (Repository knowledge map), `docs/agents/convention_guidelines.md` and the spec file, `docs/progress/tdd_<name>.md`, and `docs/progress/judge_<name>.md` for the completed feature.
+2. **Search the codebase for recurring, undocumented patterns.** A convention is a general pattern applied across the code, so the current feature is only a hint. Grep the wider codebase (`instant_python/`, `test/`) for the candidate pattern — repeated structures, helpers, naming schemes, arrangements — beyond the feature that surfaced it. Document only patterns that recur in more than one place or clearly generalize beyond the current feature.
+3. For each candidate, check if a relevant convention doc already exists in `docs/conventions/`.
+4. If the doc exists, extend or improve it with the new insight.
+5. If no doc exists, create a new one following the template in `docs/agents/convention_guidelines.md`.
+6. **Ask the human** to review and approve the new or updated convention files before finalizing.
+7. **Update the knowledge map**: After the human approves, add the new convention path to the repository knowledge map in `AGENTS.md` (the `docs/conventions/` tree). The knowledge map is the single discovery mechanism: agents read `AGENTS.md` to find conventions. NEVER edit any file under `.agents/agents/` — adding a convention must not change any subagent prompt.
+
+## Hard rules
+
+- NEVER edit `instant_python/`, `test/`, `docs/specs/`, or any file under `.agents/agents/`.
+- NEVER change the feature status in Linear.
+- NEVER write code or tests.
+- Each convention goes in its own standalone file, placed in the right area subfolder of `docs/conventions/` per the guideline. No bundling.
+- Conventions record general concepts and decisions about patterns (in tests, code, architecture, workflow) that apply across the code — never concrete cases tied to a specific feature, incident, or implementation detail. No feature names, no "during <issue>" stories, no narration of one particular implementation. Before documenting, verify the pattern recurs or generalizes beyond the feature that surfaced it; a practice applied once is not a convention.
+- Illustrate patterns with generic examples: use neutral, invented names (e.g. `a_name`, `a_value`, `_answers_for_a_scenario()`) — never the identifiers, constants, helper names, or file specifics of the feature being captured. Real files appear only in the "Real world examples" section as pointers.
+- When a convention doc already has a "Real world examples" section with a good set of pointers, do not add more examples unless they are truly helpful (e.g., they illustrate a genuinely new aspect). Avoid padding an already-complete examples section.
+- Always ask the human to approve new convention files.
+
+## Communication
+
+Your final output is **a single line**:
+
+```
+conventions updated -> docs/conventions/<area>/<name>.md
+```
+
+or if nothing new was found:
+
+```
+no new conventions
+```
+
+Never return file contents in chat.

{instant_python-0.24.2 → instant_python-0.26.0}/.agents/agents/judge.md

@@ -47,13 +47,13 @@ You have two gates: **review** (coverage, TDD discipline, code quality) and **mu
    - Evaluate code quality, simplicity and maintainability with **code_review** skill, and alignment with
      `AGENTS.md`'s Core Principles and Code Standards.
    - Evaluate security concerns using the **security_review** skill
-5. Run `make test`. Must be green.
+5. Run `task test`. Must be green.
 6. **If review passes**, run mutation testing:
    - Use the **mutation_testing** skill and `mutmut` as the mutation tool.
-   - The threshold is **100% on new/touched lines**. Scope the run to the feature with the dotted module pattern, never a filesystem path: `make mutate MUTATE_PATH="instant_python.<feature>.*"`. In mutmut 3.7 the positional arg filters mutant names, so a directory path like `instant_python/<feature>/` matches nothing and silently mutates the whole project.
+   - The threshold is **100% on new/touched lines**. Scope the run to the feature with the dotted module pattern, never a filesystem path: `task mutate MUTATE_PATH="instant_python.<feature>.*"`. In mutmut 3.7 the positional arg filters mutant names, so a directory path like `instant_python/<feature>/` matches nothing and silently mutates the whole project.
    - When the suite contains a pre-existing red test, mutmut aborts. Keep the run scoped and deterministic.
    - `len()` calls are never mutated and decorated functions (e.g. `@property`) are skipped; do not demand mutants on those lines — compensate with behavioral tests that exercise the public output.
-   - Review `make mutate` output and `mutmut show <id>` for surviving mutants.
+   - Review `task mutate` output and `mutmut show <id>` for surviving mutants.
    - For each surviving mutant, document: file, line, mutation applied, and what test is missing to kill it.
 7. Emit verdict.
 
@@ -102,7 +102,7 @@ CHANGES_REQUESTED -> docs/progress/judge_<name>.md
 
 - NEVER write or edit production code or tests in `instant_python/` or `test/` — you review,
   you don't implement.
-- Never approve with red tests or `make test` failing.
+- Never approve with red tests or `task test` failing.
 - Never approve if any requirement has no test coverage.
 - Never approve production code that no test demands.
 - Never edit the code. You say what fails, you do not fix it.

{instant_python-0.24.2 → instant_python-0.26.0}/.agents/agents/tdd_craftsman.md

@@ -49,7 +49,7 @@ REFACTOR  → clean up with the bar green: names, duplication, short functions
 2. Record in `docs/progress/current.md`: `Feature in progress: <name>` and the list of requirements `R1...R<n>` you will cover.
 3. Before starting the TDD cycle, check if the scenario requires a risky change (DB schema, API contract, service replacement). If so, use the **micro_steps_coach** skill to plan the expand-contract pattern first — then proceed with TDD.
 4. **For each requirement in order**, execute one or more Red-Green-Refactor cycles using Outside-In TDD:
-   a. **RED** — write a test in `test/` that encodes the functional requirement and verify it **fails** (`make unit`). Apply the **test_desiderata** skill to ensure the test is isolated, fast, specific, and behavioral. A test that passes on the first try proves nothing — adjust it or be suspicious.
+   a. **RED** — write a test in `test/` that encodes the functional requirement and verify it **fails** (`task test`). Apply the **test_desiderata** skill to ensure the test is isolated, fast, specific, and behavioral. A test that passes on the first try proves nothing — adjust it or be suspicious.
    b. **GREEN** — the minimum implementation in `instant_python/` that makes it pass.
    c. **REFACTOR** — with the bar green, apply the **xp_refactor** skill to eliminate duplication, improve naming, and simplify. Run tests again after every change.
    d. Append the cycle to `docs/progress/tdd_<name>.md` (which `R<n>`, which test, what minimum change).
@@ -57,7 +57,7 @@ REFACTOR  → clean up with the bar green: names, duplication, short functions
    - **Happy path and critical error scenarios** → start with a delivery acceptance test (TestClient, full stack). Then drive the application layer, then domain and infra.
    - **All other scenarios (edge cases, validation errors, etc.)** → write unit tests at the delivery layer (use case mocked) or application layer (ports mocked) as appropriate. Do not write acceptance tests for these.
 6. **Traceability**: every `R<n>` scenario must be covered by at least one concrete test. Write the `R<n> → test` map in `docs/progress/tdd_<name>.md`.
-7. Run `make test`. Green end to end.
+7. Run `task test`. Green end to end.
 8. **Do not mark `done` yourself.** The `judge` must review first.
 9. If the `leader` reinvokes you after the judge has approved and mutation testing has passed: change the Linear status to `Release` and move the summary to `docs/progress/history.md`.
 

{instant_python-0.24.2 → instant_python-0.26.0}/.agents/skills/mutation_testing/SKILL.md

@@ -46,7 +46,7 @@ TDD Workflow                    Mutation Testing Validation
 ## Reviewing a Mutation Results
 
 `mutmut` generates and runs the real mutants — there's no need to simulate them by hand. Use
-this process to go from a `make mutate` run to a reject/approve decision:
+this process to go from a `task mutate` run to a reject/approve decision:
 
 ### Step 1: Scope to What Changed
 
@@ -60,7 +60,7 @@ changed are relevant to this review.
 
 ### Step 2: Run and Read Results
 
-Run `make mutate`, then `uv run mutmut results` for the mutation score and the list of
+Run `task mutate`, then `uv run mutmut results` for the mutation score and the list of
 survived mutants (see Integration with mutmut below).
 
 ### Step 3: Classify Each Relevant Survived Mutant
@@ -171,8 +171,8 @@ if value is None:  # Mutating to == None has same effect
 ### Running mutmut
 
 ```bash
-# Always through the make target — never call mutmut directly
-make mutate
+# Always through the task target — never call mutmut directly
+task mutate
 
 # Under the hood, this runs:
 uv run mutmut run
@@ -185,11 +185,11 @@ on the dotted module path:
 uv run mutmut run "instant_python.module_name*"
 ```
 
-`make mutate` exposes this as the `MUTATE_PATH` var, so you don't have to call
+`task mutate` exposes this as the `MUTATE_PATH` var, so you don't have to call
 mutmut directly to scope a run:
 
 ```bash
-make mutate MUTATE_PATH="instant_python.module_name*"
+task mutate MUTATE_PATH="instant_python.module_name*"
 ```
 
 To derive the pattern from a changed file, drop the `.py` extension and replace `/` with `.`:

instant_python-0.26.0/.github/actions/setup_environment/action.yml

@@ -0,0 +1,26 @@
+name: Setup development environment
+
+inputs:
+  python-version:
+    description: 'Additional Python versions to install for multi-version testing (e.g. the tox matrix). Leave empty to use only the version pinned in mise.toml.'
+    required: false
+    default: ""
+outputs: {}
+runs:
+  using: composite
+  steps:
+    - name: 🧰 Setup mise
+      uses: jdx/mise-action@c2a87611a18de5b3828c5652fe268e992400cb5c # v4.3.0
+      with:
+        install: true
+        cache: true
+
+    - name: 🐍 Setup additional Python versions
+      if: inputs.python-version != ''
+      uses: actions/setup-python@v5
+      with:
+        python-version: ${{ inputs.python-version }}
+
+    - name: 📦 Install dependencies
+      run: task install
+      shell: bash

{instant_python-0.24.2 → instant_python-0.26.0}/.github/workflows/ci.yml

@@ -18,7 +18,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: 🛡️ Harden runner
-        uses: step-security/harden-runner@bf7454d06d71f1098171f2acdf0cd4708d7b5920 # v2.20.0
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
         with:
           egress-policy: audit
 
@@ -30,18 +30,18 @@ jobs:
           persist-credentials: false
 
       - name: 🛠️ Setup environment
-        uses: ./.github/actions/python_setup
+        uses: ./.github/actions/setup_environment
 
       - name: 🧐 Check linting
         id: check_lint
-        run: make check-lint
+        run: task check-lint
 
   format:
     name: format
     runs-on: ubuntu-latest
     steps:
       - name: 🛡️ Harden runner
-        uses: step-security/harden-runner@bf7454d06d71f1098171f2acdf0cd4708d7b5920 # v2.20.0
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
         with:
           egress-policy: audit
 
@@ -53,11 +53,11 @@ jobs:
           persist-credentials: false
 
       - name: 🛠️ Setup environment
-        uses: ./.github/actions/python_setup
+        uses: ./.github/actions/setup_environment
 
       - name: 🧐 Check code format
         id: check_format
-        run: make check-format
+        run: task check-format
 
   analyze-code-quality:
     name: analyze-code-quality
@@ -68,7 +68,7 @@ jobs:
 
     steps:
       - name: 🛡️ Harden runner
-        uses: step-security/harden-runner@bf7454d06d71f1098171f2acdf0cd4708d7b5920 # v2.20.0
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
         with:
           egress-policy: audit
 
@@ -102,7 +102,7 @@ jobs:
 
     steps:
       - name: 🛡️ Harden runner
-        uses: step-security/harden-runner@bf7454d06d71f1098171f2acdf0cd4708d7b5920 # v2.20.0
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
         with:
           egress-policy: audit
 
@@ -113,10 +113,10 @@ jobs:
           persist-credentials: false
 
       - name: 🛠️ Setup environment
-        uses: ./.github/actions/python_setup
+        uses: ./.github/actions/setup_environment
 
       - name: 🏃 Run secrets scanner
-        run: make secrets
+        run: task secrets
 
   audit:
     name: audit-dependencies
@@ -126,7 +126,7 @@ jobs:
 
     steps:
       - name: 🛡️ Harden runner
-        uses: step-security/harden-runner@bf7454d06d71f1098171f2acdf0cd4708d7b5920 # v2.20.0
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
         with:
           egress-policy: audit
 
@@ -137,17 +137,17 @@ jobs:
           persist-credentials: false
 
       - name: 🛠️ Setup environment
-        uses: ./.github/actions/python_setup
+        uses: ./.github/actions/setup_environment
 
       - name: 🏃 Run audit
-        run: make audit
+        run: task audit
 
   test:
     name: test
     runs-on: ubuntu-latest
     steps:
       - name: 🛡️ Harden runner
-        uses: step-security/harden-runner@bf7454d06d71f1098171f2acdf0cd4708d7b5920 # v2.20.0
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
         with:
           egress-policy: audit
 
@@ -158,7 +158,7 @@ jobs:
           persist-credentials: false
 
       - name: 🛠️ Setup environment
-        uses: ./.github/actions/python_setup
+        uses: ./.github/actions/setup_environment
 
       - name: 📦 Install test dependencies
         run: uv pip install pytest pytest-cov
@@ -180,7 +180,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: 🛡️ Harden runner
-        uses: step-security/harden-runner@bf7454d06d71f1098171f2acdf0cd4708d7b5920 # v2.20.0
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
         with:
           egress-policy: audit
 
@@ -191,7 +191,7 @@ jobs:
           persist-credentials: false
 
       - name: 🛠️ Setup environment
-        uses: ./.github/actions/python_setup
+        uses: ./.github/actions/setup_environment
         with:
           python-version: |
             3.10
@@ -200,4 +200,4 @@ jobs:
             3.13
 
       - name: 🏃 Run tox
-        run: make tox
+        run: task tox

{instant_python-0.24.2 → instant_python-0.26.0}/.github/workflows/pages.yml

@@ -18,7 +18,7 @@ jobs:
 
     steps:
       - name: 🛡️ Harden runner
-        uses: step-security/harden-runner@bf7454d06d71f1098171f2acdf0cd4708d7b5920 # v2.20.0
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
         with:
           egress-policy: audit
 
@@ -29,7 +29,7 @@ jobs:
           persist-credentials: false
 
       - name: 🛠️ Setup environment
-        uses: ./.github/actions/python_setup
+        uses: ./.github/actions/setup_environment
 
       - name: 📖 Build documentation
         run: uv run mkdocs build
@@ -71,10 +71,10 @@ jobs:
 
     steps:
       - name: 🛡️ Harden runner
-        uses: step-security/harden-runner@bf7454d06d71f1098171f2acdf0cd4708d7b5920 # v2.20.0
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
         with:
           egress-policy: audit
 
       - name: 🚀 Deploy to GitHub Pages
         id: deployment
-        uses: actions/deploy-pages@cd2ce8fcbc39b97be8ca5fce6e763baed58fa128 # v5
+        uses: actions/deploy-pages@368f82528645a54fb793d4d04e342629a3f51346 # v5

{instant_python-0.24.2 → instant_python-0.26.0}/.github/workflows/release.yml

@@ -17,7 +17,7 @@ jobs:
 
     steps:
       - name: 🛡️ Harden runner
-        uses: step-security/harden-runner@bf7454d06d71f1098171f2acdf0cd4708d7b5920 # v2.20.0
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
         with:
           egress-policy: audit
 
@@ -56,7 +56,7 @@ jobs:
 
     steps:
       - name: 🛡️ Harden runner
-        uses: step-security/harden-runner@bf7454d06d71f1098171f2acdf0cd4708d7b5920 # v2.20.0
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
         with:
           egress-policy: audit
 
@@ -68,10 +68,65 @@ jobs:
           ref: refs/tags/${{ needs.release.outputs.tag }}
 
       - name: 🛠️ Setup environment
-        uses: ./.github/actions/python_setup
+        uses: ./.github/actions/setup_environment
 
       - name: 🏃 Build package
-        run: uv build
+        run: task build
 
       - name: 🚀 Publish
         uses: pypa/gh-action-pypi-publish@release/v1
+
+  build-binaries:
+    name: Build binary (${{ matrix.target }})
+    needs:
+      - release
+    if: needs.release.outputs.released == 'true' || github.event_name == 'release'
+    strategy:
+      matrix:
+        include:
+          - runner: macos-14
+            target: aarch64-apple-darwin
+            ext: ""
+          - runner: ubuntu-latest
+            target: x86_64-unknown-linux-gnu
+            ext: ""
+          - runner: ubuntu-24.04-arm
+            target: aarch64-unknown-linux-gnu
+            ext: ""
+          - runner: windows-latest
+            target: x86_64-pc-windows-msvc
+            ext: ".exe"
+    runs-on: ${{ matrix.runner }}
+    permissions:
+      contents: write
+
+    steps:
+      - name: 🛡️ Harden runner
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
+        with:
+          egress-policy: audit
+
+      - name: 📥 Checkout the repository
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+        with:
+          fetch-depth: 0
+          persist-credentials: false
+          ref: refs/tags/${{ needs.release.outputs.tag }}
+
+      - name: 🦀 Setup Rust toolchain
+        uses: dtolnay/rust-toolchain@6bed0761d98439e5a578e2877258200ad565ba87 # stable
+        with:
+          targets: ${{ matrix.target }}
+
+      - name: 🛠️ Setup environment
+        uses: ./.github/actions/setup_environment
+
+      - name: 🏃 Build binary
+        env:
+          CARGO_BUILD_TARGET: ${{ matrix.target }}
+        run: uvx hatch build -t binary
+
+      - name: 📤 Upload release asset
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: gh release upload ${{ needs.release.outputs.tag }} dist/app/ipy-${{ matrix.target }}${{ matrix.ext }} --clobber

{instant_python-0.24.2 → instant_python-0.26.0}/.pre-commit-config.yaml

@@ -60,14 +60,16 @@ repos:
     hooks:
       - id: lint
         name: 🧹 Code Linter
-        entry: make lint
+        entry: task lint
         language: system
+        pass_filenames: false
         stages:
           - pre-push
 
       - id: format
         name: 🎨 Code Formatter
-        entry: make format
+        entry: task format
         language: system
+        pass_filenames: false
         stages:
           - pre-push

{instant_python-0.24.2 → instant_python-0.26.0}/AGENTS.md

@@ -111,21 +111,21 @@ Task management lives in the Linear project, not in a JSON file: the feature sta
 
 ## Tool usage
 
-**NEVER** call tools like `pytest`, `black`, `mypy`, or similar directly. Always use the corresponding `make` or `task` target.
+**NEVER** call tools like `pytest`, `black`, `mypy`, or similar directly. Always use the corresponding `task` target.
 
 ### Usage Rules
-1. **Testing**: When running tests, use `make unit`, `make integration`, `make acceptance` or `make test` as appropriate.
-2. **Formatting**: For formatting, use `make format` or `make check-format`.
-3. **Type Checking**: For type checking, use `make check-typing`.
-4. **Lint Checks**: For lint checks, use `make check-lint`.
-5. **Building**: For building or updating the app, use `make build` or `make update`.
-6. **Help**: If you are unsure which target to use, run `make help` to see all available options.
-7. **New Operations**: If a new operation is needed, prefer adding a new Makefile target rather than running a tool directly.
+1. **Testing**: When running tests, use `task test`.
+2. **Formatting**: For formatting, use `task format` or `task check-format`.
+3. **Type Checking**: For type checking, use `task check-typing`.
+4. **Lint Checks**: For lint checks, use `task check-lint`.
+5. **Building**: For building or updating the app, use `task build` or `task update`.
+6. **Help**: If you are unsure which target to use, run `task` (or `task --list-all`) to see all available options.
+7. **New Operations**: If a new operation is needed, prefer adding a new Taskfile target rather than running a tool directly.
 
 ### Good vs Bad Examples
 ```sh
-# Good: Use make target for unit tests
-make unit
+# Good: Use task target to run tests
+task test
 
 # Bad: Call pytest directly
 pytest tests
@@ -138,7 +138,7 @@ When working on this project:
 1. **Start every response with contemplation** 🌲
 2. **Take baby steps** - one test, one file, one change at a time 👣
 3. **Always write the failing test first** (TDD) ❌➡️✅
-4. **Use make targets** - never call tools directly 🔧
+4. **Use task targets** - never call tools directly 🔧
 5. **Keep code small and typed** - max 20 lines per method 📏
 6. **Show your thinking process** - be conversational and progressive 💭
 7. **Question everything** - assumptions, requirements, design choices ❓

{instant_python-0.24.2 → instant_python-0.26.0}/CHANGELOG.md

@@ -2,6 +2,98 @@
 
 <!-- version list -->
 
+## v0.26.0 (2026-09-08)
+
+### ✨ Features
+
+- **schema**: Remove year field and add missing built in features in ipy schema file
+  ([`f365f88`](https://github.com/dimanu-py/instant-python/commit/f365f88294745570c7cc7b5f7af9b2a613dc3d42))
+
+### ⚙️ Build System
+
+- Create installation script for Windows
+  ([`aee3d6e`](https://github.com/dimanu-py/instant-python/commit/aee3d6eac108569037c24687ef5a1925cc8eb58c))
+
+- Create installation script for Apple Silicon and Linux
+  ([`f431d2e`](https://github.com/dimanu-py/instant-python/commit/f431d2ec8c767be06dbd57a2c668f72c2678f9c2))
+
+- Bump click to fix vulnerability
+  ([`1c83b66`](https://github.com/dimanu-py/instant-python/commit/1c83b66ab31665dfe44a59221271767adb188249))
+
+- Bump python-semantic-release
+  ([`3e3c7b2`](https://github.com/dimanu-py/instant-python/commit/3e3c7b2c1d0c578184f3cb707d86d8d3fd1dc7e8))
+
+
+## v0.25.0 (2026-09-06)
+
+### ✨ Features
+
+- **config**: Not store configuration file when users decide to discard it
+  ([`e0c7998`](https://github.com/dimanu-py/instant-python/commit/e0c7998bfa38870d82e58c3c5b52a3e57fb2af0c))
+
+- **config**: Ask the user if they want to save the configuration or not
+  ([`89e95f9`](https://github.com/dimanu-py/instant-python/commit/89e95f9ecb2ca9ba548ae9c835bdea2c0b0e09ea))
+
+- **config**: Inject answers shummary formatter into real app command
+  ([`0556573`](https://github.com/dimanu-py/instant-python/commit/05565730c92ec8ac7b4269f4fc7dd4fb9c3753af))
+
+- **config**: Print dependency summary including production and development dependencies when
+  specified
+  ([`ca6652e`](https://github.com/dimanu-py/instant-python/commit/ca6652e66931ec0dc36859d8d91f7ac8ea65f8dd))
+
+- **config**: Print empty summary when no dependencies are selected
+  ([`5df6944`](https://github.com/dimanu-py/instant-python/commit/5df69442deb8f53895f53628e357c8ff691269eb))
+
+- **config**: Print git summary section
+  ([`9e97281`](https://github.com/dimanu-py/instant-python/commit/9e97281096fea1f98b05eef760b8ea9ff41c23d6))
+
+- **config**: Show selected built in features in template summary
+  ([`28e327c`](https://github.com/dimanu-py/instant-python/commit/28e327ce2d5d7127f8065572f6d195f7b00d905f))
+
+- **config**: Show summary for template configuration section supporting previous sections
+  ([`f4cc977`](https://github.com/dimanu-py/instant-python/commit/f4cc977fbfa06fbd742469c06e89a64908e6f6d3))
+
+- **config**: Show summary for general configuration section
+  ([`c2fc86b`](https://github.com/dimanu-py/instant-python/commit/c2fc86bb02d9d79c1b38a408cd4015ffd9a439f0))
+
+- **config**: Show review configuration summary title
+  ([`bb2d97d`](https://github.com/dimanu-py/instant-python/commit/bb2d97d4351d23423235210917c8c2b4144ae12d))
+
+- **config**: Include new answer formatter to print answers summary to the user
+  ([`e7dc03d`](https://github.com/dimanu-py/instant-python/commit/e7dc03d14b4e87b5021361858428a5eb396f4710))
+
+### 🪲 Bug Fixes
+
+- **config**: Remove override annotation to make library compatible with older python versions
+  ([`df71f74`](https://github.com/dimanu-py/instant-python/commit/df71f74155caec074ace285b96cce71ced950b3f))
+
+### ⚙️ Build System
+
+- Upgrade gitpython to a version that fixed vulnerabilities
+  ([`b224ae1`](https://github.com/dimanu-py/instant-python/commit/b224ae12c4ca49a73de44526366d5829655f6908))
+
+### ♻️ Refactoring
+
+- **config**: Remove 'year' field from ConfigSchema and compute it as a global env variable in Jinja
+  instead
+  ([`c76356b`](https://github.com/dimanu-py/instant-python/commit/c76356b34be61ef57154b505f626bb9cd2452b75))
+
+- **config**: Correct typo in internal validation method
+  ([`8f8acdc`](https://github.com/dimanu-py/instant-python/commit/8f8acdcc22b4a8fcde2b3759fe25d94b9de85cb9))
+
+- **config**: Build config schema before showing summary to avoid printing incorrect values
+  ([`8cc1c77`](https://github.com/dimanu-py/instant-python/commit/8cc1c77366acd882c4aa489b8564f9aaf6841823))
+
+- **config**: Let console wizard return ConfigSchema instead of primitives
+  ([`1e19771`](https://github.com/dimanu-py/instant-python/commit/1e19771ef7b3c2329c19548ba10e911560e1a93f))
+
+- **config**: Remove answers existing check since empty dict will be ignored directly
+  ([`1799a4d`](https://github.com/dimanu-py/instant-python/commit/1799a4daa9dcc8f784929abc17337ee8b2187c4f))
+
+- **config**: Substitue empty value with None only when it is a list
+  ([`ada43f5`](https://github.com/dimanu-py/instant-python/commit/ada43f5022c50d013043981129da568c2219b0ba))
+
+
 ## v0.24.2 (2026-08-07)
 
 ### 🪲 Bug Fixes

{instant_python-0.24.2 → instant_python-0.26.0}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: instant-python
-Version: 0.24.2
+Version: 0.26.0
 Summary: Instant boilerplate generation for Python projects
 Project-URL: documentation, https://dimanu-py.github.io/instant-python/
 Project-URL: repository, https://github.com/dimanu-py/instant-python/
@@ -264,6 +264,20 @@ commands like `ng new` or `create-react-app`, but for Python projects.
 
 </td></tr></table></div>
 
+## 🚀 Quick Start
+
+Once [installed](https://dimanu-py.github.io/instant-python/getting_started/installation/), generating a project takes two commands:
+
+```bash
+ipy config   # answer a few questions through an interactive wizard to create your ipy.yml configuration file
+ipy init     # generate the project from that configuration file
+```
+
+- `ipy config` asks you about your project (name, Python version, project manager, template, dependencies, and more) and writes an `ipy.yml` configuration file in the current directory.
+- `ipy init` reads that `ipy.yml` file and generates your new project.
+
+See the [First Steps](https://dimanu-py.github.io/instant-python/getting_started/first_steps/) guide for a full walkthrough.
+
 ## ✨ NEW ✨ Create Fully Customized Projects
 
 Take full control of your project generation! With **custom templates**, you can:

{instant_python-0.24.2 → instant_python-0.26.0}/README.md

@@ -31,6 +31,20 @@ commands like `ng new` or `create-react-app`, but for Python projects.
 
 </td></tr></table></div>
 
+## 🚀 Quick Start
+
+Once [installed](https://dimanu-py.github.io/instant-python/getting_started/installation/), generating a project takes two commands:
+
+```bash
+ipy config   # answer a few questions through an interactive wizard to create your ipy.yml configuration file
+ipy init     # generate the project from that configuration file
+```
+
+- `ipy config` asks you about your project (name, Python version, project manager, template, dependencies, and more) and writes an `ipy.yml` configuration file in the current directory.
+- `ipy init` reads that `ipy.yml` file and generates your new project.
+
+See the [First Steps](https://dimanu-py.github.io/instant-python/getting_started/first_steps/) guide for a full walkthrough.
+
 ## ✨ NEW ✨ Create Fully Customized Projects
 
 Take full control of your project generation! With **custom templates**, you can: