Skip to content

v1.1.0

Latest
Latest

Choose a tag to compare

View all tags
@xj63 xj63 released this 13 Sep 10:21
v1.1.0
dead451
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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 remain unchanged until they approve this behavior, and Fish upgrades may update the palette.
  • Zed / navigation and safety preferences: Add quit confirmation, close-on-repeated-panel-toggle behavior, smart-case search, editor sticky scroll, a six-line vertical navigation margin, and Markdown-only editor-width wrapping. Existing consumer configurations remain unchanged until approved; adopters should review scripted quit flows, panel shortcut expectations, reduced space in short panes, and visual wrapping before merging these settings.
  • Zed / reference filenames: Rename the commented repository references to settings.jsonc and keymap.jsonc so hosting and editing tools recognize their JSONC syntax. Consumer AI must still merge them into Zed's required settings.json and keymap.json target files; existing user configurations do not need to be renamed.
  • repository / module authoring protocol: Require official configuration references, preserve useful source comments, distinguish intent from syntax narration, and omit repeated upstream defaults unless a stability reason is documented. Existing modules have been reassessed against their tested application versions; future module authors receive a deterministic missing-guidance diagnostic and local semantic review handles source quality and default equivalence.
  • repository / consumer protocol: List every available Application Module in the human entry point so users and AI can select Fish, WezTerm, Neovim, Starship, or Zed without inspecting unrelated modules. Existing consumer configurations do not change.
  • nvim / module guidance: Remove empty user-extension placeholders and place update-checker and runtime-plugin preference explanations beside their settings. Existing runtime behavior does not change because the removed files contained no code.
  • WezTerm / module guidance: Explain the Linux/KDE blur and Windows backdrop conditions beside their settings. Existing WezTerm behavior does not change.
  • Starship / module guidance: Correctly label compact zero-width Git status markers as a Maintainer Preference rather than a reusable rule. Existing prompt behavior does not change.
  • Zed / module guidance: Remove inert empty proxy and context-server placeholders, then explain CLI window and Git tree behavior. Existing users with a proxy or context server should preserve their local value; other documented behavior is unchanged.
  • Fish / capability guidance: Explain when noproxy is useful and that it can break proxy-dependent network access. Existing Fish behavior does not change until the function is invoked.
  • Fish / validation guidance: Extend safe validation and inspection guidance to cover config.fish, conf.d, functions, and all optional tools. Existing Fish behavior does not change.
  • Fish / behavior and preferences: Expand the reference into the maintainer's sanitized daily setup with vi bindings, theme colors, guarded toolchain integrations, and command helpers. Existing consumers should review each optional dependency and name conflict before adopting anything; the former quiet greeting changes to an explicit dynamic greeting only when selected.
Assets 2
Loading