Fixup some links (#1157)

- http:s//qlty.sh/d/* URLs are supported for shorter documentation jump
URLs
- Fix URLs to plugins
- More qltyai -> qltysh updates

.qlty/qlty.toml

@@ -9,8 +9,8 @@
 #
 # Try Qlty Cloud: https://qlty.sh
 #
-# For a guide to configuration, visit https://qlty.sh/docs/config
-# Or for a full reference, visit https://qlty.sh/docs/qlty-toml
+# For a guide to configuration, visit https://qlty.sh/d/config
+# Or for a full reference, visit https://qlty.sh/d/qlty-toml
 config_version = "0"
 
 exclude_patterns = [

README.md

@@ -99,7 +99,11 @@ Contributions require agreeing to our [Contributor License Agreement](https://gi
 
 ## License
 
-Qlty CLI is licensed under the Functional Source License (FSL). More details are available in LICENSE.md.
+Qlty CLI is licensed under a version of the Functional Source License (FSL). Qlty CLI is free to use, modify, and distribute in accordance with the FSL.
+
+This codebase transitions into Open Source via a Delayed Open Source Publication (DOSP). More details are available in LICENSE.md.
+
+Licenses for code incorporated into Qlty CLI can be found in the docs/licenses folder.
 
 ## Acknowledgments
 

plugins/linters/actionlint/README.md

@@ -28,16 +28,16 @@ Actionlint will be automatically enabled by `qlty init` if a `.github/actionlint
 
 ## Configuration files
 
--   [`.github/actionlint.yaml`](https://github.com/rhysd/actionlint/blob/main/docs/config.md#configuration-file)
+- [`.github/actionlint.yaml`](https://github.com/rhysd/actionlint/blob/main/docs/config.md#configuration-file)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Actionlint.
 
 ## Links
 
--   [Actionlint on GitHub](https://github.com/rhysd/actionlint)
--   [Actionlint plugin definition](https://github.com/qltyai/plugins/tree/main/linters/actionlint)
--   [Actionlint releases](https://github.com/rhysd/actionlint/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Actionlint on GitHub](https://github.com/rhysd/actionlint)
+- [Actionlint plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/actionlint)
+- [Actionlint releases](https://github.com/rhysd/actionlint/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/bandit/README.md

@@ -28,16 +28,16 @@ Bandit will be automatically enabled when python files are present.
 
 ## Configuration files
 
--   [`.bandit`](https://bandit.readthedocs.io/en/latest/config.html)
+- [`.bandit`](https://bandit.readthedocs.io/en/latest/config.html)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Bandit.
 
 ## Links
 
--   [Bandit on GitHub](https://github.com/pycqa/bandit)
--   [Bandit plugin definition](https://github.com/qltyai/plugins/tree/main/linters/bandit)
--   [Bandit releases](https://github.com/pycqa/bandit/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Bandit on GitHub](https://github.com/pycqa/bandit)
+- [Bandit plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/bandit)
+- [Bandit releases](https://github.com/pycqa/bandit/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/black/README.md

@@ -24,10 +24,10 @@ black = "X.Y.Z"
 
 ## Links
 
--   [Black on GitHub](https://github.com/psf/black)
--   [Black plugin definition](https://github.com/qltyai/plugins/tree/main/linters/black)
--   [Black releases](https://github.com/psf/black/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Black on GitHub](https://github.com/psf/black)
+- [Black plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/black)
+- [Black releases](https://github.com/psf/black/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/checkov/README.md

@@ -28,16 +28,16 @@ Checkov will be automatically enabled by `qlty init` if a `.checkov.yaml` config
 
 ## Configuration files
 
--   [`.checkov.yaml`](https://github.com/bridgecrewio/checkov?tab=readme-ov-file#configuration-using-a-config-file)
+- [`.checkov.yaml`](https://github.com/bridgecrewio/checkov?tab=readme-ov-file#configuration-using-a-config-file)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Checkov.
 
 ## Links
 
--   [Checkov on GitHub](https://github.com/bridgecrewio/checkov)
--   [Checkov plugin definition](https://github.com/qltyai/plugins/tree/main/linters/checkov)
--   [Checkov releases](https://github.com/bridgecrewio/checkov/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Checkov on GitHub](https://github.com/bridgecrewio/checkov)
+- [Checkov plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/checkov)
+- [Checkov releases](https://github.com/bridgecrewio/checkov/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/dotenv-linter/README.md

@@ -24,10 +24,10 @@ dotenv-linter = "X.Y.Z"
 
 ## Links
 
--   [Dotenv-linter on GitHub](https://github.com/dotenv-linter/dotenv-linter)
--   [Dotenv-linter plugin definition](https://github.com/qltyai/plugins/tree/main/linters/dotenv-linter)
--   [Dotenv-linter releases](https://github.com/dotenv-linter/dotenv-linter/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Dotenv-linter on GitHub](https://github.com/dotenv-linter/dotenv-linter)
+- [Dotenv-linter plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/dotenv-linter)
+- [Dotenv-linter releases](https://github.com/dotenv-linter/dotenv-linter/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/eslint/README.md

@@ -28,16 +28,16 @@ ESLint will be automatically enabled by `qlty init` if a `.eslintrc` configurati
 
 ## Configuration files
 
--   [`.eslintrc`](https://eslint.org/docs/latest/use/configure/configuration-files)
+- [`.eslintrc`](https://eslint.org/docs/latest/use/configure/configuration-files)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running ESLint.
 
 ## Links
 
--   [ESLint on GitHub](https://github.com/eslint/eslint)
--   [ESLint plugin definition](https://github.com/qltyai/plugins/tree/main/linters/eslint)
--   [ESLint releases](https://github.com/eslint/eslint/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [ESLint on GitHub](https://github.com/eslint/eslint)
+- [ESLint plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/eslint)
+- [ESLint releases](https://github.com/eslint/eslint/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/flake8/README.md

@@ -29,16 +29,16 @@ Flake8 will be automatically enabled by `qlty init` if a `.flake8` configuration
 
 ## Configuration files
 
--   [`.flake8`](https://flake8.pycqa.org/en/latest/user/configuration.html#configuration-locations)
+- [`.flake8`](https://flake8.pycqa.org/en/latest/user/configuration.html#configuration-locations)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Flake8.
 
 ## Links
 
--   [Flake8 on GitHub](https://github.com/pycqa/flake8)
--   [Flake8 plugin definition](https://github.com/qltyai/plugins/tree/main/linters/flake8)
--   [Flake8 releases](https://flake8.pycqa.org/en/latest/release-notes/index.html)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Flake8 on GitHub](https://github.com/pycqa/flake8)
+- [Flake8 plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/flake8)
+- [Flake8 releases](https://flake8.pycqa.org/en/latest/release-notes/index.html)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/gitleaks/README.md

@@ -28,16 +28,16 @@ Gitleaks will be automatically enabled by `qlty init` if a `.gitleaks.toml` conf
 
 ## Configuration files
 
--   [`.gitleaks.toml`](https://github.com/gitleaks/gitleaks/tree/master?tab=readme-ov-file#configuration)
+- [`.gitleaks.toml`](https://github.com/gitleaks/gitleaks/tree/master?tab=readme-ov-file#configuration)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Gitleaks.
 
 ## Links
 
--   [Gitleaks on GitHub](https://github.com/gitleaks/gitleaks)
--   [Gitleaks plugin definition](https://github.com/qltyai/plugins/tree/main/linters/gitleaks)
--   [Gitleaks releases](https://github.com/gitleaks/gitleaks/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Gitleaks on GitHub](https://github.com/gitleaks/gitleaks)
+- [Gitleaks plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/gitleaks)
+- [Gitleaks releases](https://github.com/gitleaks/gitleaks/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/google-java-format/README.md

@@ -24,10 +24,10 @@ google-java-format = "X.Y.Z"
 
 ## Links
 
--   [Google-java-format on GitHub](https://github.com/google/google-java-format)
--   [Google-java-format plugin definition](https://github.com/qltyai/plugins/tree/main/linters/google-java-format)
--   [Google-java-format releases](https://github.com/google/google-java-format/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Google-java-format on GitHub](https://github.com/google/google-java-format)
+- [Google-java-format plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/google-java-format)
+- [Google-java-format releases](https://github.com/google/google-java-format/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/hadolint/README.md

@@ -28,16 +28,16 @@ Hadolint will be automatically enabled by `qlty init` if a `.hadolint.yaml` conf
 
 ## Configuration files
 
--   [`.hadolint.yaml`](https://github.com/hadolint/hadolint?tab=readme-ov-file#configure)
+- [`.hadolint.yaml`](https://github.com/hadolint/hadolint?tab=readme-ov-file#configure)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Hadolint.
 
 ## Links
 
--   [Hadolint on GitHub](https://github.com/hadolint/hadolint)
--   [Hadolint plugin definition](https://github.com/qltyai/plugins/tree/main/linters/hadolint)
--   [Hadolint releases](https://github.com/hadolint/hadolint/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Hadolint on GitHub](https://github.com/hadolint/hadolint)
+- [Hadolint plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/hadolint)
+- [Hadolint releases](https://github.com/hadolint/hadolint/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/markdownlint/README.md

@@ -28,16 +28,16 @@ Markdownlint will be automatically enabled by `qlty init` if a `.markdownlint.js
 
 ## Configuration files
 
--   [`.markdownlint.json`](https://github.com/DavidAnson/markdownlint?tab=readme-ov-file#config)
+- [`.markdownlint.json`](https://github.com/DavidAnson/markdownlint?tab=readme-ov-file#config)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Markdownlint.
 
 ## Links
 
--   [Markdownlint on GitHub](https://github.com/davidanson/markdownlint)
--   [Markdownlint plugin definition](https://github.com/qltyai/plugins/tree/main/linters/markdownlint)
--   [Markdownlint releases](https://github.com/DavidAnson/markdownlint/blob/main/CHANGELOG.md)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Markdownlint on GitHub](https://github.com/davidanson/markdownlint)
+- [Markdownlint plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/markdownlint)
+- [Markdownlint releases](https://github.com/DavidAnson/markdownlint/blob/main/CHANGELOG.md)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/osv-scanner/README.md

@@ -28,16 +28,16 @@ Osv-scanner will be automatically enabled by `qlty init` if a `osv-scanner.toml`
 
 ## Configuration files
 
--   [`osv-scanner.toml`](https://google.github.io/osv-scanner/configuration/#configure-osv-scanner)
+- [`osv-scanner.toml`](https://google.github.io/osv-scanner/configuration/#configure-osv-scanner)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Osv-scanner.
 
 ## Links
 
--   [Osv-scanner on GitHub](https://github.com/google/osv-scanner)
--   [Osv-scanner plugin definition](https://github.com/qltyai/plugins/tree/main/linters/osv-scanner)
--   [Osv-scanner releases](https://github.com/google/osv-scanner/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Osv-scanner on GitHub](https://github.com/google/osv-scanner)
+- [Osv-scanner plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/osv-scanner)
+- [Osv-scanner releases](https://github.com/google/osv-scanner/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/prettier/README.md

@@ -28,16 +28,16 @@ Prettier will be automatically enabled by `qlty init` if a `.prettier.yaml` conf
 
 ## Configuration files
 
--   [`.prettierrc`](https://prettier.io/docs/en/configuration)
+- [`.prettierrc`](https://prettier.io/docs/en/configuration)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Prettier.
 
 ## Links
 
--   [Prettier on GitHub](https://github.com/prettier/prettier)
--   [Prettier plugin definition](https://github.com/qltyai/plugins/tree/main/linters/prettier)
--   [Prettier releases](https://github.com/prettier/prettier/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Prettier on GitHub](https://github.com/prettier/prettier)
+- [Prettier plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/prettier)
+- [Prettier releases](https://github.com/prettier/prettier/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/rubocop/README.md

@@ -28,16 +28,16 @@ Rubocop will be automatically enabled by `qlty init` if a `.rubocop.yml` configu
 
 ## Configuration files
 
--   [`.rubocop.yml`](https://docs.rubocop.org/rubocop/1.63/configuration.html)
+- [`.rubocop.yml`](https://docs.rubocop.org/rubocop/1.63/configuration.html)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Rubocop.
 
 ## Links
 
--   [Rubocop on GitHub](https://github.com/rubocop/rubocop)
--   [Rubocop plugin definition](https://github.com/qltyai/plugins/tree/main/linters/rubocop)
--   [Rubocop releases](https://github.com/rubocop/rubocop/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Rubocop on GitHub](https://github.com/rubocop/rubocop)
+- [Rubocop plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/rubocop)
+- [Rubocop releases](https://github.com/rubocop/rubocop/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/ruby-stree/README.md

@@ -23,16 +23,16 @@ ruby-stree will be automatically enabled by `qlty init` if a `.streerc` configur
 
 ## Configuration files
 
--   [`.streerc`](https://github.com/ruby-syntax-tree/syntax_tree?tab=readme-ov-file#configuration)
+- [`.streerc`](https://github.com/ruby-syntax-tree/syntax_tree?tab=readme-ov-file#configuration)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running ruby-stree.
 
 ## Links
 
--   [syntax_tree on GitHub](https://github.com/ruby-syntax-tree/syntax_tree)
--   [ruby-stree plugin definition](https://github.com/qltyai/plugins/tree/main/linters/ruby-stree)
--   [syntax_tree releases](https://github.com/ruby-syntax-tree/syntax_tree/tags)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [syntax_tree on GitHub](https://github.com/ruby-syntax-tree/syntax_tree)
+- [ruby-stree plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/ruby-stree)
+- [syntax_tree releases](https://github.com/ruby-syntax-tree/syntax_tree/tags)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/ruff/README.md

@@ -28,16 +28,16 @@ Ruff will be automatically enabled by `qlty init` if a `ruff.toml` configuration
 
 ## Configuration files
 
--   [`ruff.toml`](https://github.com/astral-sh/ruff?tab=readme-ov-file#configuration)
+- [`ruff.toml`](https://github.com/astral-sh/ruff?tab=readme-ov-file#configuration)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Ruff.
 
 ## Links
 
--   [Ruff on GitHub](https://github.com/astral-sh/ruff)
--   [Ruff plugin definition](https://github.com/qltyai/plugins/tree/main/linters/ruff)
--   [Ruff releases](https://github.com/astral-sh/ruff/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Ruff on GitHub](https://github.com/astral-sh/ruff)
+- [Ruff plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/ruff)
+- [Ruff releases](https://github.com/astral-sh/ruff/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/rustfmt/README.md

@@ -28,16 +28,16 @@ Rustfmt will be automatically enabled by `qlty init` if a `.rustfmt.toml` config
 
 ## Configuration files
 
--   [`.rustfmt.toml`](https://github.com/rust-lang/rustfmt?tab=readme-ov-file#configuring-rustfmt)
+- [`.rustfmt.toml`](https://github.com/rust-lang/rustfmt?tab=readme-ov-file#configuring-rustfmt)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Rustfmt.
 
 ## Links
 
--   [Rustfmt on GitHub](https://github.com/rust-lang/rustfmt)
--   [Rustfmt plugin definition](https://github.com/qltyai/plugins/tree/main/linters/rustfmt)
--   [Rustfmt releases](https://github.com/rust-lang/rustfmt/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Rustfmt on GitHub](https://github.com/rust-lang/rustfmt)
+- [Rustfmt plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/rustfmt)
+- [Rustfmt releases](https://github.com/rust-lang/rustfmt/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License
 

plugins/linters/semgrep/README.md

@@ -28,16 +28,16 @@ Semgrep will be automatically enabled by `qlty init` if a `.semgrep.yaml` config
 
 ## Configuration files
 
--   [`.semgrep.yaml`](https://semgrep.dev/docs/writing-rules/overview/)
+- [`.semgrep.yaml`](https://semgrep.dev/docs/writing-rules/overview/)
 
 To keep your project tidy, you can move configuration files into `.qlty/configs` and Qlty will find and use them when running Semgrep.
 
 ## Links
 
--   [Semgrep on GitHub](https://github.com/semgrep/semgrep)
--   [Semgrep plugin definition](https://github.com/qltyai/plugins/tree/main/linters/semgrep)
--   [Semgrep releases](https://github.com/semgrep/semgrep/releases)
--   [Qlty's open source plugin definitions](https://github.com/qltyai/plugins)
+- [Semgrep on GitHub](https://github.com/semgrep/semgrep)
+- [Semgrep plugin definition](https://github.com/qltysh/qlty/tree/main/plugins/linters/semgrep)
+- [Semgrep releases](https://github.com/semgrep/semgrep/releases)
+- [Qlty's open source plugin definitions](https://github.com/qltysh/qlty/tree/main/plugins/linters)
 
 ## License