aias 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 259563157827385f1beba2d991c459efdf4c746a66413bd7ff8d67604d628444
+  data.tar.gz: e3ce1c92696ae6875aa5638f1e131d08b90ec50883589bf00ea7b8a2ee47ed2a
+SHA512:
+  metadata.gz: 5fc0091d9f866e3c18853413e5fdcb75d71af405e1bb2828bfa4115bc88d60cf5b1f56082c396cbea5ac89be78f788b17250e9b14951d0af87f0cc91b7c1b3f5
+  data.tar.gz: a8d6042f18018b9756d673101a0ed19f6e6bdeea5c95cf2ecc8908e38890fb41ddc802ccf33892150ae75a7c4f4615e3908b2f3208363906566cb4fbb9438197

data/.envrc

@@ -0,0 +1 @@
+export RR=`pwd`

data/.github/workflows/deploy-github-pages.yml

@@ -0,0 +1,52 @@
+name: Deploy Documentation to GitHub Pages
+on:
+  push:
+    branches:
+      - main
+      - develop
+    paths:
+      - "docs/**"
+      - "mkdocs.yml"
+      - ".github/workflows/deploy-github-pages.yml"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  pages: write
+  id-token: write
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: 3.x
+
+      - name: Install dependencies
+        run: |
+          pip install mkdocs
+          pip install mkdocs-material
+          pip install mkdocs-macros-plugin
+          pip install mike
+
+      - name: Configure Git
+        run: |
+          git config --local user.email "action@github.com"
+          git config --local user.name "GitHub Action"
+
+      - name: Deploy to GitHub Pages
+        run: |
+          if [ "${{ github.ref }}" = "refs/heads/main" ]; then
+            echo "Deploying from main branch"
+            mkdocs gh-deploy --force --clean
+          else
+            echo "Deploying from develop branch"
+            mkdocs gh-deploy --force --clean
+          fi

data/.ruby-version

@@ -0,0 +1 @@
+4.0.2

data/CHANGELOG.md

@@ -0,0 +1,140 @@
+# AIAS Change Log
+
+The AI Assistant Scheduler
+
+## [Unreleased]
+
+## [0.1.0] 2026-03-24
+
+### refactor(cli): split monolithic CLI into per-command files
+
+Moved each of the twelve CLI commands into its own file under
+`lib/aias/cli/` (e.g. `cli/update.rb`, `cli/add.rb`). The main
+`cli.rb` is now a slim skeleton containing shared helpers, map aliases,
+and `require_relative` calls. Zeitwerk is configured to ignore the
+`cli/` subdirectory so the files are loaded explicitly rather than
+autoloaded as constants.
+
+Test suite split to match: shared helpers extracted into
+`test/cli_test_case.rb`; each command has its own `test/test_cli_*.rb`
+file. The monolithic `test/test_cli.rb` is removed.
+
+### fix(cli): fix `c_l_i` namespace appearing in `aias help` output
+
+Thor's `help` instance method takes `subcommand` as a positional
+argument but the override declared it as a keyword argument
+(`subcommand: false`). Ruby passed `{subcommand: false}` — a truthy
+hash — to Thor's positional parameter, causing `formatted_usage` to
+prepend the snake-cased class name (`c_l_i`) to every command in the
+help table. Fixed by changing the signature to match Thor's:
+`def help(command = nil, subcommand = false)`.
+
+### feat(cli): add `aias version` command
+
+Prints the installed gem version. Accessible as `aias version`,
+`aias -v`, or `aias --version`.
+
+### refactor: extract shared modules and classes
+
+- `Aias::BlockParser` — shared `extract_block` / `strip_block` helpers
+  used by both `CrontabManager` and `EnvFile`; eliminates ~60 lines of
+  duplication
+- `Aias::Paths` — single source of truth for all filesystem paths
+  (`SCHEDULE_DIR`, `SCHEDULE_CFG`, `SCHEDULE_LOG`, `SCHEDULE_ENV`,
+  `AIA_CONFIG`)
+- `Aias::ScheduleConfig` — extracted from `CLI#install`; manages
+  `prompts.dir` key in `~/.config/aia/schedule/aia.yml` with full test
+  coverage
+
+### fix(job_builder): double-quote paths in generated cron entries
+
+Paths embedded in cron command strings are now wrapped in double quotes
+inside the single-quoted shell string. Prevents failures when prompts
+directory, log directory, or config file paths contain spaces.
+
+### fix(crontab_manager): distinguish missing crontab from read failure
+
+`crontab -l` exits non-zero both when the user has no crontab and when
+a real error occurs. `read_crontab` now returns `""` only on the "no
+crontab for" message and raises `Aias::Error` for any other failure,
+preventing silent crontab overwrites on read errors.
+
+### fix(prompt_scanner): tighten `grep` invocation
+
+Added `--include=*.md` and `-m 1` flags to the `grep -rl` call.
+Limits candidate files to Markdown and stops reading each file after
+the first `schedule:` match, reducing I/O on large prompts directories.
+
+### fix(security): create directories with mode 0700, env file with 0600
+
+All `FileUtils.mkdir_p` calls now pass `mode: 0o700`. `EnvFile#write`
+applies `chmod 0600` on every write so API keys in `env.sh` are never
+world-readable, even if `umask` is permissive.
+
+### docs: rewrite README for CLI users
+
+- Removed the "Public API" section (internal Ruby classes belong in the
+  full documentation site, not the README)
+- Added "Usage" section with the full `aias help` output
+- Rewrote "How It Works" in user-facing terms; no internal class names
+- Key Features table: stripped per-feature descriptions; names only
+- Added link to full documentation site under the logo
+- CLI Commands table: added `aias version`
+- Fixed stale single-test example (referenced deleted `test_cli.rb`)
+
+### docs: update `docs/index.md` to match README structure
+
+- Key Features: names only, no inline descriptions
+- Added "Commands" section with full `aias help` output
+- Rewrote "How It Works" in user-facing terms
+
+### docs: add "Understanding Cron and Crontab" guide
+
+New `docs/guides/understanding-cron.md` for users unfamiliar with cron.
+Covers: what cron is; what a crontab is; reading a five-field cron
+expression; how `aias` owns its block without disturbing other entries;
+why cron strips the environment and how `aias install` solves it;
+essential `crontab` commands; checking job logs; macOS Full Disk Access
+note. Cross-linked from `guides/cron-environment.md`.
+
+### feat(cli): add `aias add PATH` command
+
+Installs or replaces a single prompt's cron job without touching any other
+installed entries. Useful when you have edited one prompt and want it
+scheduled immediately without re-scanning the entire prompts directory.
+
+- `PromptScanner#scan_one(path)` — parses a single file by path; raises
+  `Aias::Error` for missing files, files outside the prompts directory, or
+  prompts with no `schedule:` in their frontmatter
+- `CrontabManager#add_job(cron_line, prompt_id)` — upserts one entry into
+  the aias-managed crontab block; existing entries for the same prompt ID
+  are replaced cleanly; all other entries are left untouched
+- Full validation (schedule syntax, parameter defaults, `aia` binary) runs
+  before any crontab write, consistent with `aias update`
+
+### docs: add `aias add` command documentation
+
+- New `docs/cli/add.md` — full command reference with upsert semantics,
+  worked examples, prompt ID derivation, options table, and exit codes
+- Updated `docs/cli/index.md` — command count, table row, and
+  `--prompts-dir` example
+- Updated `docs/reference/api.md` — `CLI#add`, `PromptScanner#scan_one`,
+  and `CrontabManager#add_job` API entries
+- Updated `README.md` — command table, `aias add` section, and Public API
+  entries for all three new methods
+
+### chore(gemspec): update summary and description
+
+- Summary sharpened to lead with the "no config file" differentiator
+- Description rewritten as a `<<~DESC` heredoc covering the full feature
+  set: `update`, `add`, schedule formats, runtime model, log location
+
+### refactor(prompts): rewrite `code_health_check` example prompt
+
+Replaced a passive checklist with an active review prompt that runs
+commands, reads files, and reports findings directly rather than generating
+to-do items for the user to complete manually.
+
+## [0.1.0] - 2026-03-23
+
+- Initial release

data/COMMITS.md

@@ -0,0 +1,196 @@
+---
+url: https://www.conventionalcommits.org/en/v1.0.0/
+title: Conventional Commits
+description: A specification for adding human and machine readable meaning to commit messages
+access_date: 2025-07-31T20:51:29.000Z
+current_date: 2025-07-31T20:51:29.601Z
+---
+
+# Conventional Commits
+
+A specification for adding human and machine readable meaning to commit messages
+
+ Quick Summary Full Specification Contribute
+
+# Conventional Commits 1.0.0
+
+## Summary
+
+The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages.
+
+The commit message should be structured as follows:
+
+---
+
+```
+<type>[optional scope]: <description>
+
+[optional body]
+
+[optional footer(s)]
+
+```
+
+---
+
+The commit contains the following structural elements, to communicate intent to the consumers of your library:
+
+1. **fix:** a commit of the _type_ `fix` patches a bug in your codebase (this correlates with `PATCH` in Semantic Versioning).
+2. **feat:** a commit of the _type_ `feat` introduces a new feature to the codebase (this correlates with `MINOR` in Semantic Versioning).
+3. **BREAKING CHANGE:** a commit that has a footer `BREAKING CHANGE:`, or appends a `!` after the type/scope, introduces a breaking API change (correlating with `MAJOR` in Semantic Versioning). A BREAKING CHANGE can be part of commits of any _type_.
+4. _types_ other than `fix:` and `feat:` are allowed, for example @commitlint/config-conventional (based on the Angular convention) recommends `build:`, `chore:`,`ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, and others.
+5. _footers_ other than `BREAKING CHANGE: <description>` may be provided and follow a convention similar to git trailer format.
+
+Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic Versioning (unless they include a BREAKING CHANGE). A scope may be provided to a commit’s type, to provide additional contextual information and is contained within parenthesis, e.g., `feat(parser): add ability to parse arrays`.
+
+## Examples
+
+### Commit message with description and breaking change footer
+
+```
+feat: allow provided config object to extend other configs
+
+BREAKING CHANGE: `extends` key in config file is now used for extending other config files
+
+```
+
+### Commit message with `!` to draw attention to breaking change
+
+```
+feat!: send an email to the customer when a product is shipped
+
+```
+
+### Commit message with scope and `!` to draw attention to breaking change
+
+```
+feat(api)!: send an email to the customer when a product is shipped
+
+```
+
+### Commit message with both `!` and BREAKING CHANGE footer
+
+```
+chore!: drop support for Node 6
+
+BREAKING CHANGE: use JavaScript features not available in Node 6.
+
+```
+
+### Commit message with no body
+
+```
+docs: correct spelling of CHANGELOG
+
+```
+
+### Commit message with scope
+
+```
+feat(lang): add Polish language
+
+```
+
+### Commit message with multi-paragraph body and multiple footers
+
+```
+fix: prevent racing of requests
+
+Introduce a request id and a reference to latest request. Dismiss
+incoming responses other than from latest request.
+
+Remove timeouts which were used to mitigate the racing issue but are
+obsolete now.
+
+Reviewed-by: Z
+Refs: #123
+
+```
+
+## Specification
+
+The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
+
+1. Commits MUST be prefixed with a type, which consists of a noun, `feat`, `fix`, etc., followed by the OPTIONAL scope, OPTIONAL `!`, and REQUIRED terminal colon and space.
+2. The type `feat` MUST be used when a commit adds a new feature to your application or library.
+3. The type `fix` MUST be used when a commit represents a bug fix for your application.
+4. A scope MAY be provided after a type. A scope MUST consist of a noun describing a section of the codebase surrounded by parenthesis, e.g., `fix(parser):`
+5. A description MUST immediately follow the colon and space after the type/scope prefix. The description is a short summary of the code changes, e.g., _fix: array parsing issue when multiple spaces were contained in string_.
+6. A longer commit body MAY be provided after the short description, providing additional contextual information about the code changes. The body MUST begin one blank line after the description.
+7. A commit body is free-form and MAY consist of any number of newline separated paragraphs.
+8. One or more footers MAY be provided one blank line after the body. Each footer MUST consist of a word token, followed by either a `:<space>` or `<space>#` separator, followed by a string value (this is inspired by the git trailer convention).
+9. A footer’s token MUST use `-` in place of whitespace characters, e.g., `Acked-by` (this helps differentiate the footer section from a multi-paragraph body). An exception is made for `BREAKING CHANGE`, which MAY also be used as a token.
+10. A footer’s value MAY contain spaces and newlines, and parsing MUST terminate when the next valid footer token/separator pair is observed.
+11. Breaking changes MUST be indicated in the type/scope prefix of a commit, or as an entry in the footer.
+12. If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon, space, and description, e.g.,_BREAKING CHANGE: environment variables now take precedence over config files_.
+13. If included in the type/scope prefix, breaking changes MUST be indicated by a`!` immediately before the `:`. If `!` is used, `BREAKING CHANGE:` MAY be omitted from the footer section, and the commit description SHALL be used to describe the breaking change.
+14. Types other than `feat` and `fix` MAY be used in your commit messages, e.g., _docs: update ref docs._
+15. The units of information that make up Conventional Commits MUST NOT be treated as case sensitive by implementors, with the exception of BREAKING CHANGE which MUST be uppercase.
+16. BREAKING-CHANGE MUST be synonymous with BREAKING CHANGE, when used as a token in a footer.
+
+## Why Use Conventional Commits
+
+* Automatically generating CHANGELOGs.
+* Automatically determining a semantic version bump (based on the types of commits landed).
+* Communicating the nature of changes to teammates, the public, and other stakeholders.
+* Triggering build and publish processes.
+* Making it easier for people to contribute to your projects, by allowing them to explore a more structured commit history.
+
+## FAQ
+
+### How should I deal with commit messages in the initial development phase?
+
+We recommend that you proceed as if you’ve already released the product. Typically _somebody_, even if it’s your fellow software developers, is using your software. They’ll want to know what’s fixed, what breaks etc.
+
+### Are the types in the commit title uppercase or lowercase?
+
+Any casing may be used, but it’s best to be consistent.
+
+### What do I do if the commit conforms to more than one of the commit types?
+
+Go back and make multiple commits whenever possible. Part of the benefit of Conventional Commits is its ability to drive us to make more organized commits and PRs.
+
+### Doesn’t this discourage rapid development and fast iteration?
+
+It discourages moving fast in a disorganized way. It helps you be able to move fast long term across multiple projects with varied contributors.
+
+### Might Conventional Commits lead developers to limit the type of commits they make because they’ll be thinking in the types provided?
+
+Conventional Commits encourages us to make more of certain types of commits such as fixes. Other than that, the flexibility of Conventional Commits allows your team to come up with their own types and change those types over time.
+
+### How does this relate to SemVer?
+
+`fix` type commits should be translated to `PATCH` releases. `feat` type commits should be translated to `MINOR` releases. Commits with `BREAKING CHANGE` in the commits, regardless of type, should be translated to `MAJOR` releases.
+
+### How should I version my extensions to the Conventional Commits Specification, e.g. `@jameswomack/conventional-commit-spec`?
+
+We recommend using SemVer to release your own extensions to this specification (and encourage you to make these extensions!)
+
+### What do I do if I accidentally use the wrong commit type?
+
+#### When you used a type that’s of the spec but not the correct type, e.g. `fix` instead of `feat`
+
+Prior to merging or releasing the mistake, we recommend using `git rebase -i` to edit the commit history. After release, the cleanup will be different according to what tools and processes you use.
+
+#### When you used a type _not_ of the spec, e.g. `feet` instead of `feat`
+
+In a worst case scenario, it’s not the end of the world if a commit lands that does not meet the Conventional Commits specification. It simply means that commit will be missed by tools that are based on the spec.
+
+### Do all my contributors need to use the Conventional Commits specification?
+
+No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they’re merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
+
+### How does Conventional Commits handle revert commits?
+
+Reverting code can be complicated: are you reverting multiple commits? if you revert a feature, should the next release instead be a patch?
+
+Conventional Commits does not make an explicit effort to define revert behavior. Instead we leave it to tooling authors to use the flexibility of _types_ and _footers_ to develop their logic for handling reverts.
+
+One recommendation is to use the `revert` type, and a footer that references the commit SHAs that are being reverted:
+
+```
+revert: let us never again speak of the noodle incident
+
+Refs: 676104e, a215868
+
+```

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2026 Dewayne VanHoozer
+
+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.

data/README.md

@@ -0,0 +1,249 @@
+# aias - AI Assistant (AIA) Scheduler
+
+> [!INFO]
+> See the [CHANGELOG](CHANGELOG.md) for the latest changes.
+
+<br>
+<table>
+<tr>
+<td width="40%" align="center" valign="top">
+<img src="docs/assets/images/logo.jpg" alt="aias"><br>
+<em>"Schedule. Batch. Execute."</em><br><br>
+<a href="https://madbomber.github.io/aias">Full Documentation</a>
+</td>
+<td width="60%" valign="top">
+<h2>Key Features</h2>
+
+- Natural Language Scheduling
+- Zero Configuration
+- Reliable Cron Environment
+- MCP Server Support
+- Per-Prompt Overrides
+- Schedule-Specific Config
+- Single-Prompt Control
+- Full Sync on Update
+- Safe Validation
+- Rich Inspection Commands
+</td>
+</tr>
+</table>
+
+Schedule [AIA](https://github.com/madbomber/aia) prompts as cron jobs. Add a `schedule:` key to any prompt's YAML frontmatter — `aias update` does the rest.
+
+No separate configuration file. No daemon. The OS cron daemon runs each job as a fresh `aia` process.
+
+## Installation
+
+```bash
+gem install aias
+```
+
+Or add to your `Gemfile`:
+
+```ruby
+gem "aias"
+```
+
+**Requirements:** Ruby >= 3.2, the `aia` CLI installed and reachable in your login shell, `AIA_PROMPTS_DIR` set to your prompts directory.
+
+## Usage
+
+```
+$ aias help
+Commands:
+  aias add PATH              # Add (or replace) a single scheduled prompt in the crontab
+  aias check                 # Diff view: scheduled prompts vs what is installed
+  aias clear                 # Remove all aias-managed crontab entries
+  aias dry-run               # Show what `update` would write without touching the crontab
+  aias help [COMMAND]        # Describe available commands or one specific command
+  aias install [PATTERN...]  # Capture PATH, API keys, and env vars into ~/.config/aia/schedule/env.sh
+  aias last [N]              # Show last-run time for installed jobs (default 5)
+  aias list                  # List all installed aias cron jobs
+  aias next [N]              # Show next scheduled run time for installed jobs (default 5)
+  aias remove PROMPT_ID      # Remove a single scheduled prompt from the crontab
+  aias show PROMPT_ID        # Show the installed crontab entry for a single prompt
+  aias uninstall             # Remove managed env block from ~/.config/aia/schedule/env.sh
+  aias update                # Scan prompts, regenerate all crontab entries, and install
+  aias version               # Print the aias version
+
+Options:
+  -p, [--prompts-dir=PROMPTS_DIR]  # Prompts directory (overrides AIA_PROMPTS__DIR / AIA_PROMPTS_DIR env vars)
+```
+
+## Quick Start
+
+**1. Capture your environment (once):**
+
+```bash
+aias install
+```
+
+**2. Add a schedule to any prompt's frontmatter:**
+
+```yaml
+---
+schedule: "0 8 * * *"
+description: Morning briefing
+---
+Summarize what happened overnight in the Ruby and AI ecosystems.
+```
+
+**3. Validate and install:**
+
+```bash
+aias update
+```
+
+**4. Verify:**
+
+```bash
+aias list
+aias check
+```
+
+## Environment Setup
+
+Cron runs with a minimal environment — no Ruby version manager, no API keys, no user-defined variables. `aias install` solves this by capturing your current shell environment into `~/.config/aia/schedule/env.sh`, which is sourced before every scheduled job.
+
+### What gets captured automatically
+
+| Variable group | Examples | Why |
+|---|---|---|
+| `PATH` | rbenv shims, Homebrew, gem bin dirs | `aia` and MCP server binaries must be findable |
+| `*_API_KEY` | `ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, etc. | LLM provider authentication |
+| `AIA_*` | `AIA_PROMPTS__DIR`, `AIA_MODEL`, etc. | AIA runtime configuration |
+| `LANG`, `LC_ALL` | `en_US.UTF-8` | Ruby UTF-8 string handling |
+
+### MCP server credentials
+
+If your scheduled prompts use MCP servers, those servers may need their own credentials — auth tokens, configuration paths, or other variables that are not covered by the defaults. Pass glob patterns to `aias install` to capture them:
+
+```bash
+# GitHub MCP server (needs a personal access token)
+aias install 'GITHUB_*'
+
+# Homebrew MCP server
+aias install 'HOMEBREW_*'
+
+# Multiple patterns at once
+aias install 'GITHUB_*' 'HOMEBREW_*'
+```
+
+Check the documentation for each MCP server you use to identify the variables it reads, then add the corresponding pattern. Re-run `aias install` any time you add a new API key, install a new MCP server binary, or change your Ruby version.
+
+## CLI Commands
+
+| Command | Description |
+|---|---|
+| `aias install [PATTERN...]` | Capture PATH, API keys, and env vars into `env.sh`. Run once before scheduling. |
+| `aias update` | Scan prompts, regenerate all crontab entries, install. Primary command. |
+| `aias add PATH` | Add or replace a single prompt's cron job without touching others. |
+| `aias remove PROMPT_ID` | Remove a single prompt's cron job. Aliases: `rm`, `delete`. |
+| `aias check` | Diff view: prompts with `schedule:` vs what is installed. |
+| `aias list` | Report all installed jobs: prompt ID, schedule, log file. |
+| `aias dry-run` | Show what `update` would write without touching the crontab. |
+| `aias show PROMPT_ID` | Show the installed crontab entry for a single prompt. |
+| `aias next [N]` | Show next scheduled run time for installed jobs (default 5). |
+| `aias last [N]` | Show last-run time for installed jobs (default 5). |
+| `aias clear` | Remove all aias-managed crontab entries. Non-aias entries untouched. |
+| `aias uninstall` | Remove the managed env block from `env.sh`. |
+| `aias version` | Print the installed aias version. |
+
+### `aias add PATH`
+
+Installs or replaces the cron job for a single prompt file. All other installed jobs are left untouched. Errors immediately if the file has no `schedule:` in its frontmatter or fails validation.
+
+```bash
+aias add ~/.prompts/standup.md
+# aias: added standup (every weekday at 9:00am (0 9 * * 1-5))
+
+aias add ~/.prompts/drafts/idea.md
+# aias [error] 'drafts/idea' has no schedule: in its frontmatter
+```
+
+Use `add` when you want to schedule a single new prompt without re-scanning the entire prompts directory. Use `update` to synchronise everything at once.
+
+### Global Option
+
+`--prompts-dir PATH` (alias `-p`) overrides the `AIA_PROMPTS__DIR` / `AIA_PROMPTS_DIR` environment variables for any command that reads prompt files:
+
+```bash
+aias --prompts-dir ~/work/prompts update
+aias -p ~/work/prompts dry-run
+aias -p ~/work/prompts check
+```
+
+## Schedule Format
+
+The `schedule:` value accepts a standard cron expression, a `@`-shorthand keyword, or a natural language string. Natural language parsing is provided by the [fugit](https://github.com/floraison/fugit) gem.
+
+```yaml
+schedule: "0 8 * * *"                    # cron expression
+schedule: "@daily"                        # @ shorthand
+schedule: "every day at 8am"             # natural language
+schedule: "every weekday at 9am"         # natural language
+schedule: "every monday at 9am"          # natural language
+schedule: "every monday through friday at 9am"  # natural language
+schedule: "every 6 hours"               # natural language
+schedule: "every 30 minutes"            # natural language
+schedule: "every 1st of the month at midnight"  # natural language
+schedule: "every day at 9am in America/New_York"  # with timezone
+```
+
+Natural language strings are resolved to cron expressions at install time. Use `aias dry-run` to preview the resolved expression before installing. See [Scheduling Prompts](docs/guides/scheduling-prompts.md) for the full reference including all supported patterns, limitations, and a quick-reference table.
+
+Once a prompt has been scheduled and resides in the crontab you **cannot** remove it just by deleting or commenting out the `schedule:` line. Run `aias update` (full sync) or `aias remove PROMPT_ID` to remove it.
+
+
+## Validation
+
+Before installing, `aias` validates each scheduled prompt:
+
+- **Schedule syntax** — cron expression or natural language must be parseable
+- **Parameter completeness** — all `parameters:` keys must have default values (interactive input is impossible in cron)
+- **AIA binary** — `aia` must be locatable in PATH or a known version-manager shim directory (`~/.rbenv/shims`, `~/.rvm/bin`, `~/.asdf/shims`, `/opt/homebrew/bin`)
+
+Invalid prompts are warned and excluded. The remaining valid prompts are installed.
+
+## Logging
+
+Each job logs to `~/.config/aia/schedule/logs/<prompt_id>.log`. stdout and stderr are combined and overwrite the log on each run.
+
+```
+~/.config/aia/schedule/logs/
+  daily_digest.log
+  reports/
+    weekly.log
+```
+
+## How It Works
+
+```
+Prompt file with schedule: in YAML frontmatter
+         │
+         ▼
+aias update scans prompts directory for schedule: keys
+         │
+         ▼
+Each prompt is validated: schedule syntax, parameter defaults, aia binary
+         │
+         ▼
+A cron entry is written for each valid prompt
+         │
+         ▼
+OS cron daemon runs each job on schedule:
+  source env.sh && aia [--prompts-dir DIR] prompt_id > log 2>&1
+```
+
+## Development
+
+```bash
+bin/setup                                     # install dependencies
+bundle exec rake test                         # run all tests
+bundle exec ruby -Ilib:test test/test_aias.rb # run a single test file
+bin/console                                   # interactive REPL
+```
+
+## License
+
+[MIT](LICENSE.txt)