Document package sources for self update

[Mirochill]

Pull Request Check List

Resolves: #10633

• Added tests for changed code.
• Updated documentation for changed code.

Summary:

• Document that poetry self commands use a system pyproject.toml in Poetry's configuration directory.
• Clarify that poetry self update reads package sources from that system project, not from the current project's pyproject.toml.
• Link the [[tool.poetry.source]] format to the package sources documentation.

Validation:

• git diff --check
• rg -n "system project|configuration#config-directory|repositories/#package-sources|tool\.poetry\.source|current project.*self update|preserves existing" docs\cli.md

Not run locally: documentation build, tests, or pre-commit.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

Deploy preview for website ready!

Project:	website
Status:	✅  Deploy successful!
Preview URL:	https://website-iywdr5p70-python-poetry.vercel.app
Latest Commit:	9788c1d

Deployed with vercel-action

[radoering]

@sourcery-ai review

[sourcery-ai]

Hey - I've found 3 issues

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="docs/cli.md" line_range="957-960" />
<code_context>
 {{% note %}}
-The `self install` command works similar to the [`install` command](#install). However,
-it is different in that the packages managed are for Poetry's runtime environment.
+The `self install` command works similar to the [`install` command](#install).
+However, it is different in that the packages managed are for Poetry's runtime environment.
 {{% /note %}}
</code_context>
<issue_to_address>
**nitpick (typo):** Consider changing "works similar to" to "works similarly to" for grammatical correctness.

Because "works" needs an adverb here, please change this to "works similarly to the [`install` command]" for grammatical accuracy.

```suggestion
{{% note %}}
The `self install` command works similarly to the [`install` command](#install).
However, it is different in that the packages managed are for Poetry's runtime environment.
{{% /note %}}
```
</issue_to_address>

### Comment 2
<location path="docs/cli.md" line_range="1032" />
<code_context>
 {{% note %}}
-The `self sync` command works similar to the [`sync` command](#sync). However,
-it is different in that the packages managed are for Poetry's runtime environment.
+The `self sync` command works similar to the [`sync` command](#sync).
+However, it is different in that the packages managed are for Poetry's runtime environment.
 {{% /note %}}
</code_context>
<issue_to_address>
**nitpick (typo):** Use "similarly" instead of "similar" after "works".

“Works similarly to the [`sync` command]” is the idiomatic phrasing; “works similar to” is ungrammatical in standard English.

```suggestion
The `self sync` command works similarly to the [`sync` command](#sync).
```
</issue_to_address>

### Comment 3
<location path="docs/cli.md" line_range="1046" />
<code_context>
 The `self update` command updates Poetry version in its current runtime environment.

 {{% note %}}
</code_context>
<issue_to_address>
**suggestion (typo):** Clarify "updates Poetry version" by adding an article or possessive.

Rephrase as "updates the Poetry version" or "updates Poetry's version" for grammatical completeness and clarity.

```suggestion
The `self update` command updates the Poetry version in its current runtime environment.
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.