kash-shell 0.3.18__tar.gz → 0.3.21__tar.gz

{kash_shell-0.3.18 → kash_shell-0.3.21}/.copier-answers.yml

@@ -1,5 +1,5 @@
 # Changes here will be overwritten by Copier. Do not edit manually.
-_commit: v0.2.10
+_commit: v0.2.14
 _src_path: gh:jlevy/simple-modern-uv
 package_author_email: joshua@cal.berkeley.edu
 package_author_name: Joshua Levy

{kash_shell-0.3.18 → kash_shell-0.3.21}/.cursor/rules/general.mdc

@@ -3,11 +3,14 @@ description: General Guidelines
 globs: 
 alwaysApply: true
 ---
-# General Responses
+# Assistant Rules
 
-Remember you are a senior engineer and have a serious responsibility to be clear,
-factual, think step by step and be systematic, express expert opinion, and make use of
-the user's attention wisely.
+**Your fundamental responsibility:** Remember you are a senior engineer and have a
+serious responsibility to be clear, factual, think step by step and be systematic,
+express expert opinion, and make use of the user's attention wisely.
+
+**Rules must be followed:** It is your responsibility to carefully read these rules as
+well as Python or other language-specific rules included here.
 
 Therefore:
 
@@ -22,8 +25,8 @@ Therefore:
   it. It's your responsibility to suggest approaches that lead to better, simpler
   solutions.
 
-- Give thoughtful opinions on better/worse approaches, but never say "great idea!"
-  or "good job" or other non-essential banter or encouragement.
+- Give thoughtful opinions on better/worse approaches, but NEVER say "great idea!"
+  or "good job" or other compliments, encouragement, or non-essential banter.
   Your job is to give expert opinions and to solve problems, not to motivate the user.
 
 - Avoid gratuitous enthusiasm or generalizations.
@@ -50,18 +53,20 @@ Therefore:
   this is meaningless to anyone reading the code later.
   (Instead, describe in your message to the user any other contextual information.)
 
-- DO NOT use fancy headings like "===== STEP 1: ... =====" in comments
+- DO NOT use fancy or needlessly decorated headings like "===== MIGRATION TOOLS ====="
+  in comments
 
-- DO NOT scatter numbered steps in comments.
+- DO NOT number steps in comments.
   These are hard to maintain if the code changes.
-  Wrong: "// Step 3: Fetch the data from the cache" Correct: "// Now fetch the data from
-  the cache"
-
-## Using Emojis
+  NEVER DO THIS: "// Step 3: Fetch the data from the cache"\
+  This is fine: "// Now fetch the data from the cache"
 
 - DO NOT use emojis or special unicode characters like ① or • or – or — in comments.
 
 - Use emojis in output if it enhances the clarity and can be done consistently.
   You may use ✔︎ and ✘ to indicate success and failure, and ∆ and ‼︎ for user-facing
   warnings and errors, for example, but be sure to do it consistently.
-  But but do not use emojis gratuitously as it clutters the output.
+  DO NOT use emojis gratuitously in comments or output.
+  You may use then ONLY when they have clear meanings (like success or failure).
+  Unless the user says otherwise, avoid emojis and Unicode in comments as clutters the
+  output with little benefit.

{kash_shell-0.3.18 → kash_shell-0.3.21}/.cursor/rules/python.mdc

@@ -16,10 +16,10 @@ Always use full type annotations, generics, and other modern practices.
 
 ## Project Setup and Developer Workflows
 
-- This project has a modern pyproject.toml file and a Makefile.
-  Be sure you read and understand both.
+- Important: BE SURE you read and understand the project setup by reading the
+  pyproject.toml file and the Makefile.
 
-- Use uv for running all code and managing dependencies.
+- ALWAYS use uv for running all code and managing dependencies.
   Never use direct `pip` or `python` commands.
 
 - Use modern uv commands: `uv sync`, `uv run ...`, etc.
@@ -56,10 +56,13 @@ Always use full type annotations, generics, and other modern practices.
 - Be sure to resolve the pyright (basedpyright) linter errors as you develop and make
   changes.
 
-- If type checker errors are hard to resolve, check pyproject.toml to see if they are an
-  excessively pedantic error.
-  In special cases you may consider disabling it globally it in pyproject.toml but you
-  *must ask for confirmation* from the user before doing this.
+- If type checker errors are hard to resolve, you may add a comment `# pyright: ignore`
+  to disable Pyright warnings or errors but ONLY if you know they are not a real problem
+  and are difficult to fix.
+
+- In special cases you may consider disabling it globally it in pyproject.toml but YOU
+  MUST ASK FOR CONFIRMATION from the user before globally disabling lint or type checker
+  rules.
 
 - Never change an existing comment, pydoc, or a log statement, unless it is directly
   fixing the issue you are changing, or the user has asked you to clean up the code.
@@ -87,18 +90,27 @@ Always use full type annotations, generics, and other modern practices.
 - Use strif's `atomic_output_file` context manager when writing files to ensure output
   files are written atomically.
 
-- Use `uv add` and `uv sync` as needed to add dependencies.
+## Use Modern Python Practices
+
+- ALWAYS use `@override` decorators to override methods from base classes.
+  This is a modern Python practice and helps avoid bugs.
 
 ## Testing
 
-- Don't write one-off test code in extra files or within `if __name__ == "__main__":`
-  blocks. Instead, for simple tests, create simple test functions in the original file
-  below a `## Tests` comment.
-  This keeps the tests clear and close to the code.
+- For longer tests put them in a file like `tests/test_somename.py` in the `tests/`
+  directory (or `tests/module_name/test_somename.py` file for a submodule).
+
+- For simple tests, prefer inline functions in the original code file below a `## Tests`
+  comment. This keeps the tests easy to maintain and close to the code.
+  Inline tests should NOT import pytest or pytest fixtures as we do not want runtime
+  dependency on pytest.
+
+- DO NOT write one-off test code in extra files that are throwaway.
 
-- For longer tests `test_somename.py` in the `tests/` directory.
+- DO NOT put `if __name__ == "__main__":` just for quick testing.
+  Instead use the inline function tests and run them with `uv run pytest`.
 
-- Then you can run such tests with `uv run python -s src/.../path/to/test`
+- You can run such individual tests with `uv run pytest -s src/.../path/to/test`
 
 - Don't add docs to assertions unless it's not obvious what they're checking - the
   assertion appears in the stack trace.
@@ -106,16 +118,19 @@ Always use full type annotations, generics, and other modern practices.
   x is 5`. That is redundant.
   Just write `assert x == 5`.
 
+- DO NOT write trivial or obvious tests that are evident directly from code, such as
+  assertions that confirm the value of a constant setting.
+
 - NEVER write `assert False`. If a test reaches an unexpected branch and must fail
   explicitly, `raise AssertionError("Explanation")` instead.
   This is best typical best practice in Python since assertions can be removed with
   optimization.
 
-- Don't use pytest fixtures like parameterized tests or expected exception decorators
+- DO NOT use pytest fixtures like parameterized tests or expected exception decorators
   unless absolutely necessary in more complex tests.
-  It is often far simpler to use simple assertions and put the checks inside the test.
-  This is preferable because then we want simple tests in original source files but
-  don't want pytest dependencies at runtime.
+  It is typically simpler to use simple assertions and put the checks inside the test.
+  This is also preferable because then simple tests have no explicit pytest dependencies
+  and can be placed in code anywhere.
 
 ## Types and Type Annotations
 
@@ -147,7 +162,7 @@ Always use full type annotations, generics, and other modern practices.
     binary = "binary"
   ```
 
-## Guidelines for Formatting Literal strings
+## Guidelines for Literal Strings
 
 - For multi-line strings NEVER put multi-line strings flush against the left margin.
   ALWAYS use a `dedent()` function to make it more readable.
@@ -163,6 +178,22 @@ Always use full type annotations, generics, and other modern practices.
       """).strip()
   ```
 
+## Guidelines for Comments
+
+- Comments should be EXPLANATORY: Explain *WHY* something is done a certain way and not
+  just *what* is done.
+
+- Comments should be CONCISE: Remove all extraneous words.
+
+- DO NOT use comments to state obvious things or repeat what is evident from the code.
+  Here is an example of a comment that SHOULD BE REMOVED because it simply repeats the
+  code, which is distracting and adds no value:
+  ```python
+  if self.failed == 0:
+      # All successful
+      return "All tasks finished successfully"
+  ```
+
 ## Guidelines for Docstrings
 
 - Here is an example of the correct style for docstrings:
@@ -204,8 +235,9 @@ Always use full type annotations, generics, and other modern practices.
 - Docstrings *should* mention any key rationale or pitfalls when using the class or
   function.
 
-- Don't add pydocs that just repeat information obvious from the function, variable
-  names, or concise description.
+- Avoid obvious or repetitive docstrings.
+  Do NOT add pydocs that just repeat in English facts that are obvious from the function
+  name, variable name, or types.
   That is silly and obvious and makes the code longer for no reason.
 
 - Do NOT list args and return values if they're obvious.
@@ -220,11 +252,24 @@ Always use full type annotations, generics, and other modern practices.
 
 ## General Clean Coding Practices
 
-- When writing a class DO NOT blindly make delegation methods for consistency.
-  For exmaple DO NOT write methods like this:
+- Avoid writing trivial wrapper functions.
+  For example, when writing a class DO NOT blindly make delegation methods around public
+  member variables. DO NOT write methods like this:
   ```python
       def reassemble(self) -> str:
         """Call the original reassemble method."""
         return self.paragraph.reassemble()
   ```
   In general, the user can just call the enclosed objects methods, reducing code bloat.
+
+- If a function does not use a parameter, but it should still be present, you can use `#
+  pyright: ignore[reportUnusedParameter]` in a comment to suppress the linter warning.
+
+## Guidelines for Backward Compatibility
+
+- When changing code in a library or general function, if a change to an API or library
+  will break backward compatibility, MENTION THIS to the user.
+
+- DO NOT implement additional code for backward compatiblity (such as extra methods or
+  variable aliases or comments about backward compatibility) UNLESS the user has
+  confirmed that it is necessary.

{kash_shell-0.3.18 → kash_shell-0.3.21}/.github/workflows/ci.yml

@@ -42,7 +42,7 @@ jobs:
         uses: astral-sh/setup-uv@v5
         with:
           # Update this as needed:
-          version: "0.7.11"
+          version: "0.7.13"
           enable-cache: true
           python-version: ${{ matrix.python-version }}
 
@@ -56,7 +56,7 @@ jobs:
       #     python-version: ${{ matrix.python-version }}
 
       - name: Install all dependencies
-        run: uv sync --all-extras --dev
+        run: uv sync --all-extras
 
       - name: Run linting
         run: uv run python devtools/lint.py

{kash_shell-0.3.18 → kash_shell-0.3.21}/.github/workflows/publish.yml

@@ -25,7 +25,7 @@ jobs:
       - name: Install uv (official Astral action)
         uses: astral-sh/setup-uv@v5
         with:
-          version: "0.7.11"
+          version: "0.7.13"
           enable-cache: true
           python-version: "3.12"
 
@@ -33,7 +33,7 @@ jobs:
         run: uv python install
 
       - name: Install all dependencies
-        run: uv sync --all-extras --dev
+        run: uv sync --all-extras
 
       - name: Run tests
         run: uv run pytest
@@ -43,5 +43,8 @@ jobs:
       - name: Build package
         run: uv build
 
-      - name: Publish to PyPI (using uv)
-        uses: pypa/gh-action-pypi-publish@release/v1
+      - name: Publish to PyPI
+        run: uv publish --trusted-publishing always
+        # Although uv is newer and faster, the "official" publishing option is the one from PyPA,
+        # which uses twine. If desired, replace `uv publish` with:
+        # uses: pypa/gh-action-pypi-publish@release/v1

{kash_shell-0.3.18 → kash_shell-0.3.21}/Makefile

@@ -9,7 +9,7 @@
 default: agent-rules install lint test 
 
 install:
-	uv sync --all-extras --dev
+	uv sync --all-extras
 
 lint:
 	uv run python devtools/lint.py
@@ -18,7 +18,10 @@ test:
 	uv run pytest
 
 test-full:
-	ENABLE_TESTS_LLM=1 ENABLE_TESTS_INTEGRATION=1 uv run pytest
+	ENABLE_TESTS_ONLINE=1 ENABLE_TESTS_INTEGRATION=1 uv run pytest
+
+run: install lint test
+	uv run kash
 
 upgrade:
 	uv sync --upgrade --all-extras --dev

{kash_shell-0.3.18 → kash_shell-0.3.21}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: kash-shell
-Version: 0.3.18
+Version: 0.3.21
 Summary: The knowledge agent shell (core)
 Project-URL: Repository, https://github.com/jlevy/kash-shell
 Author-email: Joshua Levy <joshua@cal.berkeley.edu>
@@ -16,6 +16,7 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Classifier: Typing :: Typed
 Requires-Python: <4.0,>=3.11
+Requires-Dist: aiolimiter>=1.2.1
 Requires-Dist: anyio>=4.8.0
 Requires-Dist: audioop-lts>=0.2.1; python_version >= '3.13'
 Requires-Dist: cachetools>=5.5.2
@@ -50,6 +51,7 @@ Requires-Dist: pydantic>=2.10.6
 Requires-Dist: pydub>=0.25.1
 Requires-Dist: pygments>=2.19.1
 Requires-Dist: pyperclip>=1.9.0
+Requires-Dist: pyrate-limiter>=3.7.0
 Requires-Dist: python-dotenv>=1.0.1
 Requires-Dist: python-magic-bin>=0.4.14; platform_system == 'Windows'
 Requires-Dist: python-magic>=0.4.27; platform_system == 'Linux' or platform_system == 'Darwin'
@@ -115,7 +117,7 @@ the Python framework, a few core utilities, and the Kash command-line shell.
 Additional actions for handling more complex tasks like converting documents and
 transcribing, researching, or annotating videos, are in the
 [kash-docs](https://github.com/jlevy/kash-docs) and
-[kash-media](https://github.com/jlevy/kash-docs) packages, all available on PyPI and
+[kash-media](https://github.com/jlevy/kash-media) packages, all available on PyPI and
 quick to install via uv.
 
 ### Key Concepts

{kash_shell-0.3.18 → kash_shell-0.3.21}/README.md

@@ -43,7 +43,7 @@ the Python framework, a few core utilities, and the Kash command-line shell.
 Additional actions for handling more complex tasks like converting documents and
 transcribing, researching, or annotating videos, are in the
 [kash-docs](https://github.com/jlevy/kash-docs) and
-[kash-media](https://github.com/jlevy/kash-docs) packages, all available on PyPI and
+[kash-media](https://github.com/jlevy/kash-media) packages, all available on PyPI and
 quick to install via uv.
 
 ### Key Concepts

{kash_shell-0.3.18 → kash_shell-0.3.21}/development.md

@@ -17,11 +17,11 @@ The `Makefile` simply offers shortcuts to `uv` commands for developer convenienc
 
 ```shell
 # First, install all dependencies and set up your virtual environment.
-# This simply runs `uv sync --all-extras --dev` to install all packages,
+# This simply runs `uv sync --all-extras` to install all packages,
 # including dev dependencies and optional dependencies.
 make install
 
-# Run uv sync, lint, and test:
+# Run uv sync, lint, and test (and also generate agent rules):
 make
 
 # Build wheel:
@@ -66,6 +66,17 @@ source .venv/bin/activate
 
 See [uv docs](https://docs.astral.sh/uv/) for details.
 
+## Agent Rules
+
+See [.cursor/rules](.cursor/rules) for agent rules.
+These are written for [Cursor](https://www.cursor.com/) but are also used by other
+agents because the Makefile will generate `CLAUDE.md` and `AGENTS.md` from the same
+rules.
+
+```shell
+make agent-rules
+```
+
 ## IDE setup
 
 If you use VSCode or a fork like Cursor or Windsurf, you can install the following

{kash_shell-0.3.18 → kash_shell-0.3.21}/pyproject.toml

@@ -77,10 +77,12 @@ dependencies = [
     "pathspec>=0.12.1",
     "patch-ng>=1.18.1",
     "inquirerpy>=0.3.4",
-    # LLM essentials:
+    # LLM and API essentials:
     "tiktoken>=0.9.0",
     "openai>=1.66.3",
     "litellm>=1.63.11",
+    "pyrate-limiter>=3.7.0",
+    "aiolimiter>=1.2.1",
     # Basic text handling and web scraping:
     "readabilipy>=0.3.0",
     "markdownify>=0.13.1",
@@ -223,6 +225,7 @@ reportMissingParameterType = false
 reportUnannotatedClassAttribute = false
 reportUninitializedInstanceVariable = false
 reportCallInDefaultInitializer = false
+reportUntypedBaseClass = false
 # Make ignoring easier:
 reportIgnoreCommentWithoutRule = false
 reportUnnecessaryTypeIgnoreComment = false

kash_shell-0.3.18/src/kash/actions/core/markdownify.py → kash_shell-0.3.21/src/kash/actions/core/markdownify_html.py

@@ -11,13 +11,10 @@ from kash.web_content.web_extract_readabilipy import extract_text_readabilipy
 log = get_logger(__name__)
 
 
-@kash_action(
-    precondition=is_url_resource | has_html_body,
-    mcp_tool=True,
-)
-def markdownify(item: Item) -> Item:
+@kash_action(precondition=is_url_resource | has_html_body, mcp_tool=True)
+def markdownify_html(item: Item) -> Item:
     """
-    Converts a URL or raw HTML item to Markdown, fetching with the content
+    Converts raw HTML or the URL of an HTML page to Markdown, fetching with the content
     cache if needed. Also uses readability to clean up the HTML.
     """
 

{kash_shell-0.3.18 → kash_shell-0.3.21}/src/kash/commands/workspace/workspace_commands.py

@@ -23,14 +23,12 @@ from kash.exec import (
     resolve_locator_arg,
 )
 from kash.exec.action_registry import get_all_actions_defaults
-from kash.exec.fetch_url_metadata import fetch_url_metadata
+from kash.exec.fetch_url_items import fetch_url_item
 from kash.exec.precondition_checks import actions_matching_paths
 from kash.exec.precondition_registry import get_all_preconditions
-from kash.exec.preconditions import is_url_resource
 from kash.exec_model.shell_model import ShellResult
 from kash.local_server.local_url_formatters import local_url_formatter
 from kash.media_base import media_tools
-from kash.media_base.media_services import is_media_url
 from kash.model.items_model import Item, ItemType
 from kash.model.params_model import GLOBAL_PARAMS
 from kash.model.paths_model import StorePath, fmt_store_path
@@ -54,12 +52,11 @@ from kash.utils.common.format_utils import fmt_loc
 from kash.utils.common.obj_replace import remove_values
 from kash.utils.common.parse_key_vals import parse_key_value
 from kash.utils.common.type_utils import not_none
-from kash.utils.common.url import Url, is_url, parse_http_url
+from kash.utils.common.url import Url
 from kash.utils.errors import InvalidInput
 from kash.utils.file_formats.chat_format import tail_chat_history
 from kash.utils.file_utils.dir_info import is_nonempty_dir
 from kash.utils.file_utils.file_formats_model import Format
-from kash.utils.text_handling.doc_normalization import can_normalize
 from kash.web_content.file_cache_utils import cache_file
 from kash.workspaces import (
     current_ws,
@@ -189,85 +186,6 @@ def cache_content(*urls_or_paths: str, refetch: bool = False) -> None:
         PrintHooks.spacer()
 
 
-@kash_command
-def download(*urls_or_paths: str, refetch: bool = False, no_format: bool = False) -> ShellResult:
-    """
-    Download a URL or resource. Uses cached content if available, unless `refetch` is true.
-    Inputs can be URLs or paths to URL resources.
-    Creates both resource and document versions for text content.
-
-    :param no_format: If true, do not also normalize Markdown content.
-    """
-    ws = current_ws()
-    saved_paths = []
-
-    for url_or_path in urls_or_paths:
-        locator = resolve_locator_arg(url_or_path)
-        url: Url | None = None
-
-        # Get the URL from the locator
-        if not isinstance(locator, Path) and is_url(locator):
-            url = Url(locator)
-        elif isinstance(locator, StorePath):
-            url_item = ws.load(locator)
-            if is_url_resource(url_item):
-                url = url_item.url
-
-        if not url:
-            raise InvalidInput(f"Not a URL or URL resource: {fmt_loc(locator)}")
-
-        # Handle media URLs differently
-        if is_media_url(url):
-            log.message(
-                "URL is a media URL, so adding as a resource and will cache media: %s", fmt_loc(url)
-            )
-            store_path = ws.import_item(url, as_type=ItemType.resource, reimport=refetch)
-            saved_paths.append(store_path)
-            media_tools.cache_media(url)
-        else:
-            # Cache the content first
-            expiration_sec = 0 if refetch else None
-            cache_result = cache_file(url, expiration_sec=expiration_sec)
-            original_filename = Path(parse_http_url(url).path).name
-            mime_type = cache_result.content.headers and cache_result.content.headers.mime_type
-
-            # Create a resource item
-            resource_item = Item.from_external_path(
-                cache_result.content.path,
-                ItemType.resource,
-                url=url,
-                mime_type=mime_type,
-                original_filename=original_filename,
-            )
-            # For initial content, do not format or add frontmatter.
-            store_path = ws.save(resource_item, no_frontmatter=True, no_format=True)
-            saved_paths.append(store_path)
-            select(store_path)
-
-            # Also create a doc version for text content if we want to normalize formatting.
-            if resource_item.format and can_normalize(resource_item.format) and not no_format:
-                doc_item = Item.from_external_path(
-                    cache_result.content.path,
-                    ItemType.doc,
-                    url=url,
-                    mime_type=mime_type,
-                    original_filename=original_filename,
-                )
-                # Now use default formatting and frontmatter.
-                doc_store_path = ws.save(doc_item)
-                saved_paths.append(doc_store_path)
-                select(doc_store_path)
-
-    print_status(
-        "Downloaded %s %s:\n%s",
-        len(saved_paths),
-        plural("item", len(saved_paths)),
-        fmt_lines(saved_paths),
-    )
-
-    return ShellResult(show_selection=True)
-
-
 @kash_command
 def history(max: int = 30, raw: bool = False) -> None:
     """
@@ -536,10 +454,14 @@ def save_clipboard(
 
 
 @kash_command
-def fetch_metadata(*files_or_urls: str, refetch: bool = False) -> ShellResult:
+def fetch_url(*files_or_urls: str, refetch: bool = False) -> ShellResult:
     """
-    Fetch metadata for the given URLs or resources. Imports new URLs and saves back
-    the fetched metadata for existing resources.
+    Fetch content and metadata for the given URLs or resources, saving to the
+    current workspace.
+
+    Imports new URLs and saves back the fetched metadata for existing resources.
+    Also saves a resource item with the content of the URL, either HTML, text, or
+    of any other type.
 
     Skips items that already have a title and description, unless `refetch` is true.
     Skips (with a warning) items that are not URL resources.
@@ -552,7 +474,7 @@ def fetch_metadata(*files_or_urls: str, refetch: bool = False) -> ShellResult:
     store_paths = []
     for locator in locators:
         try:
-            fetched_item = fetch_url_metadata(locator, refetch=refetch)
+            fetched_item = fetch_url_item(locator, refetch=refetch)
             store_paths.append(fetched_item.store_path)
         except InvalidInput as e:
             log.warning(

{kash_shell-0.3.18 → kash_shell-0.3.21}/src/kash/config/colors.py

@@ -139,14 +139,15 @@ web_light_translucent = SimpleNamespace(
     bg_header=hsl_to_hex("hsla(188, 42%, 70%, 0.2)"),
     bg_alt=hsl_to_hex("hsla(39, 24%, 90%, 0.3)"),
     bg_alt_solid=hsl_to_hex("hsla(39, 24%, 97%, 1)"),
-    bg_selected=hsl_to_hex("hsla(188, 44%, 94%, 0.95)"),
+    bg_meta_solid=hsl_to_hex("hsla(39, 24%, 94%, 1)"),
+    bg_selected=hsl_to_hex("hsla(188, 21%, 94%, 0.9)"),
     text=hsl_to_hex("hsl(188, 39%, 11%)"),
     code=hsl_to_hex("hsl(44, 38%, 23%)"),
     border=hsl_to_hex("hsl(188, 8%, 50%)"),
     border_hint=hsl_to_hex("hsla(188, 8%, 72%, 0.3)"),
     border_accent=hsl_to_hex("hsla(305, 18%, 65%, 0.85)"),
     hover=hsl_to_hex("hsl(188, 12%, 84%)"),
-    hover_bg=hsl_to_hex("hsla(188, 44%, 94%, 1)"),
+    hover_bg=hsl_to_hex("hsla(188, 18%, 97%, 1)"),
     hint=hsl_to_hex("hsl(188, 11%, 65%)"),
     hint_strong=hsl_to_hex("hsl(188, 11%, 46%)"),
     hint_gentle=hsl_to_hex("hsla(188, 11%, 65%, 0.2)"),
@@ -165,14 +166,15 @@ web_light_translucent = SimpleNamespace(
 web_dark_translucent = SimpleNamespace(
     primary=hsl_to_hex("hsl(188, 40%, 62%)"),
     primary_light=hsl_to_hex("hsl(188, 50%, 72%)"),
-    secondary=hsl_to_hex("hsl(188, 12%, 65%)"),
-    tertiary=hsl_to_hex("hsl(188, 7%, 40%)"),
+    secondary=hsl_to_hex("hsl(188, 12%, 70%)"),
+    tertiary=hsl_to_hex("hsl(188, 7%, 45%)"),
     bg=hsl_to_hex("hsla(220, 14%, 7%, 0.95)"),
     bg_solid=hsl_to_hex("hsl(220, 14%, 7%)"),
     bg_header=hsl_to_hex("hsla(188, 42%, 20%, 0.3)"),
     bg_alt=hsl_to_hex("hsla(220, 14%, 12%, 0.5)"),
-    bg_alt_solid=hsl_to_hex("hsl(220, 14%, 12%)"),
-    bg_selected=hsl_to_hex("hsla(188, 12%, 50%, 0.95)"),
+    bg_alt_solid=hsl_to_hex("hsl(220, 15%, 16%)"),
+    bg_meta_solid=hsl_to_hex("hsl(220, 14%, 25%)"),
+    bg_selected=hsl_to_hex("hsla(188, 13%, 33%, 0.95)"),
     text=hsl_to_hex("hsl(188, 10%, 90%)"),
     code=hsl_to_hex("hsl(44, 38%, 72%)"),
     border=hsl_to_hex("hsl(188, 8%, 25%)"),

{kash_shell-0.3.18 → kash_shell-0.3.21}/src/kash/config/text_styles.py

@@ -277,6 +277,8 @@ EMOJI_HELP = "?"
 
 EMOJI_ACTION = "⛭"
 
+EMOJI_TASK = "⚒"
+
 EMOJI_COMMAND = "⧁"  # More ideas: ⦿⧁⧀⦿⦾⟐⦊⟡
 
 EMOJI_SHELL = "⦊"

{kash_shell-0.3.18 → kash_shell-0.3.21}/src/kash/docs/markdown/topics/a1_what_is_kash.md

@@ -34,7 +34,7 @@ the Python framework, a few core utilities, and the Kash command-line shell.
 Additional actions for handling more complex tasks like converting documents and
 transcribing, researching, or annotating videos, are in the
 [kash-docs](https://github.com/jlevy/kash-docs) and
-[kash-media](https://github.com/jlevy/kash-docs) packages, all available on PyPI and
+[kash-media](https://github.com/jlevy/kash-media) packages, all available on PyPI and
 quick to install via uv.
 
 ### Key Concepts