v1.1.0

1.1.0

Fixed

• nvim / configuration comments: Explain the non-default two-space StyLua policy beside the TOML settings and document that the default column width is intentionally inherited. Formatting behavior is unchanged.

• Zed / configuration intent: Restore JSONC comments with per-setting intent, default comparisons, extension conditions, conflicts, maintainer-preference labels, and official references. Remove repeated panel and theme-mode defaults; effective behavior remains the same while local defaults can evolve naturally.

• Starship / configuration intent: Restore official Pure-preset provenance, default comparisons, right-prompt constraints, compact Git-status trade-offs, and runtime identity/privacy comments. Remove the redundant default Git-state format and make Python display activate only for a virtual environment; users who relied on project-file Python version detection should keep Starship's default detectors.

• nvim / configuration intent: Restore official starter provenance, default comparisons, bootstrap effects, plugin-version intent, disabled runtime capabilities, and theme conflicts beside the Lua settings. Remove redundant lazy.nvim defaults.lazy and defaults.version values, the StyLua column-width default, and generated LazyVim NEWS state; the lock file remains the deliberate plugin reproducibility boundary, while existing users keep the same effective plugin-loading and formatting behavior and regain their own news cursor.

• WezTerm / configuration intent: Restore default comparisons, intent, platform conditions, conflicts, and official-documentation comments; remove an unsupported deprecated KDE blur option, describe the remaining branch as generic Linux behavior, and make the Windows 11 backdrop effective with its required opacity. Linux users lose only the invalid blur request, while Windows users should review the newly effective transparent system material.

• Fish / configuration intent: Restore intent, condition, dependency, conflict, privacy, maintainer-preference labels, and official-documentation comments throughout the reference; guard interactive integrations and theme selection, and prevent file-owned paths from persisting as universal state. Rustup and Android integration comments now distinguish reusable guards from toolchain preferences. Existing consumers should review PATH precedence, project-managed JDK selection, optional application startup behavior, and custom key bindings before adopting the corrected behavior.

Removed

• Fish / AI-authored shortcut: Remove the gst Git-status abbreviation that originated in the initial AI example rather than the maintainer's configuration. Existing consumer configurations are not changed automatically; users who deliberately adopted the shortcut may keep it locally, while new consumers no longer receive an invented preference.
• Fish / machine-specific integrations: Remove the OrbStack startup script and LM Studio and Antigravity PATH additions from the general reference. Existing consumer configurations are not changed automatically; users who intentionally rely on these applications may retain their own local integration rather than inherit a maintainer-specific choice.
• Zed / provider-specific preferences: Remove registry agent installations, selected Google agent models/options, and the Copilot edit-prediction provider from the general reference. Existing consumer configurations are not changed automatically; users who intentionally use these services may retain their own settings, while new consumers should choose integrations from their installed tools and account preferences rather than inherit the maintainer's providers.

Added

• aerospace / module and preferences: Add a curated AeroSpace 0.21.3-Beta reference with startup behavior, focus-following pointer movement, Vim-style window control, numeric workspaces, and move-then-follow navigation. Default scalar settings and machine-specific launchers, monitor assignments, and application rules are omitted; existing consumer configurations remain unchanged until users review the shortcuts, Cmd-H behavior, pointer movement, version requirement, and conflicts.
• Zed / module and preferences: Add sanitized editor settings and a double-Shift file-finder keymap with Vim editing, Catppuccin/Monaspace presentation, panel layout, and diagnostics. Existing users should review every preference and verify extensions, font/theme availability, autosave behavior, and key conflicts before adopting it; no credentials, private endpoints, or local state are included.
• Starship / module and preferences: Add a sanitized two-sided prompt with compact Git state, command duration, and Python environment context. Existing users should review shell initialization, Unicode/font support, narrow-terminal behavior, and the intentionally collapsed Git status before adopting it.
• nvim / module and preferences: Add a sanitized LazyVim 8 reference with C/C++, Rust, and TOML extras, locked plugin revisions, and a transparent Catppuccin theme. Existing users should not replace another plugin manager wholesale and must approve first-start network/bootstrap effects and any optional language-tool installation.
• WezTerm / module and preferences: Add a sanitized cross-platform terminal reference with guarded window effects, Catppuccin styling, a Monaspace-first font fallback, and a hidden tab bar. Existing users should review visibility, navigation, font availability, compositor support, and platform-specific decoration effects before adopting it.

Changed

• repository / validation coverage: Parse every tracked Fish, TOML, and Lua Reference Configuration in the local test suite, provision the Lua syntax checker in CI, and refresh CI's pinned Fish validator to 4.9.3. Contributors now receive deterministic syntax feedback for complete modules instead of only Fish's root file and JSON references; no Consumer Configuration changes.
• repository / documentation: Update the architecture tree to match the implemented modules and workflows, generalize the root update-review prompt to every Application Module, add the full test suite to release preparation, and label the original Fish acceptance scenario as historical. Consumer behavior is unchanged; future maintainers and consumer AIs receive current entry points rather than Fish-only or pre-expansion guidance.
• repository / dependency-guidance protocol: Require every referenced font, theme, icon pack, extension, plugin, language server, command, application, and platform service to name its affected capability, availability check, acquisition behavior, and first-party source. Existing Consumer Configurations do not change; module authors and reviewers now treat vague optional-dependency prose as an Advisory Finding.
• Fish / tested version: Revalidate every tracked Fish reference with Fish 4.9.3 and update the documented and CI-pinned patch release. The 4.9.3 upstream change fixes macOS dead-key input and does not require Consumer Configuration migration.
• Zed / version review: Review relevant upstream changes through Zed 1.19.2 while retaining 1.18.1 as the last runtime-validated version because Zed has no non-interactive configuration validator. Consumer settings are unchanged; a future interactive schema check can advance the runtime claim.
• aerospace / dependency guidance: Clarify that the reference uses only AeroSpace's built-in commands and macOS Accessibility, with no font, theme, plugin, shell-command, or third-party application dependency. Consumer behavior is unchanged; excluded application launchers and routing rules remain environment-specific choices.
• Fish / dependency guidance: Map optional environment blocks, interactive integrations, the bundled Nord theme, and every command wrapper to their exact tools, availability checks, and first-party sources. Consumer behavior is unchanged; users can now select capabilities without guessing which software must be installed.
• nvim / dependency guidance: Distinguish automatically downloaded lazy.nvim plugins from external bootstrap tools, language servers, debuggers, StyLua, and optional Nerd Font rendering. Consumer behavior is unchanged; first startup and capability-specific installations are now explicit approval decisions.
• Starship / dependency guidance: Map prompt initialization, Git context, Bash-only Ble.sh support, Python environment display, and Unicode glyph rendering to their actual requirements. Consumer behavior is unchanged; no named font or Nerd Font is falsely required.
• WezTerm / dependency guidance: Name the Monaspace Frozen Fonts package, explain the macOS-only Menlo fallback, and clarify that Catppuccin Mocha is bundled with WezTerm rather than installed as a plugin. Consumer behavior is unchanged; font installation remains optional and separately approved.
• Zed / dependency guidance: Map the selected themes, icon theme, font family, and CargoTom server setting to the exact Catppuccin Blur, Catppuccin Icons, Monaspace Frozen Fonts, and CargoTom resources. Consumer behavior is unchanged; extensions and fonts are detected and approved independently.
• nvim / dependency checkpoint: Refresh the reviewed lock file to LazyVim 16.0.1 and lazy.nvim 11.17.5, including nvim-treesitter's incompatible main rewrite and current language integrations. Consumers remain unchanged until they approve an update; adopters now need Neovim 0.12, Tree-sitter CLI 0.26.1 or newer, and a parser update through :TSUpdate, followed by the documented health check.
• Fish / theme management: Replace the generated Nord-derived color-variable snapshot with Fish's native fish_config theme choose Nord mechanism. New consumers receive the Nord theme bundled with their installed Fish version rather than unconfirmed custom color differences; existing consumer configurations rema...

v1.0.0

1.0.0

Added

• repository: Add a deterministic Configuration Audit for known secrets, private identifiers, personal paths, supported configuration syntax, and Local Consumer State boundaries.
• repository: Add a versioned commit hook and pull-request workflow that delegate to the same repository check interface.
• repository / review protocol: Define a local AI Configuration Audit for tracked pull-request changes, with Blocking and Advisory findings recorded in the pull request. GitHub CI remains deterministic and no repository AI credential is required. Existing consumer configurations require no migration.
• Fish / module and guidance: Add the first runnable Fish Reference Configuration, a human entry point with a copyable AI prompt, and the eight-stage Consumer AI workflow. Users should adapt selected capabilities into their existing Fish configuration and record intent locally; no existing Consumer Configuration changes automatically.
• Fish / recovery and intent: Define exact Git and file-backup Recovery Paths plus the approved ignored .local/ fallback for Fish intent. Existing users need no migration; an AI should select the first viable intent location and never place configuration copies or credentials in clone-local state.
• repository / review protocol: Add a bounded local review-context command that emits only the tracked pull-request diff, Review Policy, and affected module guidance after deterministic checks pass. Local AI audits should use this command; no hosted AI service or credential is introduced.
• Fish / update protocol: Add Review Cursor-based, Fish-filtered change assessment and a read-only context command. Existing Consumer Configurations do not change automatically; their AI should present an impact report, obtain confirmation for behavior, dependency, or preference changes, and advance the cursor only after accepted changes validate.
• repository / consumer protocol: Define application-scoped update assessment, ancestry checks, module-removal handling, and required shared-protocol change information. Existing users need no migration; their AI should use the selected module's update guidance and stop on missing or divergent history.
• repository / consumer protocol: Make the natural-language Application Module contract discoverable and deterministically check target, prerequisite, validation, translation-source, privacy, syntax, and change-information obligations. Existing Fish users need no migration; future modules follow the same root-level, comment-first contract without a manifest.
• repository / consumer protocol: Publish the repeatable Semantic Version release procedure and the first stable Review Cursor. Existing Consumer Configurations do not change; fresh users may record v1.0.0, while existing users assess it from their earlier cursor before any edits.