📖 [Docs]: Community defaults aligned with MSX baseline

.claude/CLAUDE.md

@@ -0,0 +1 @@
+@../AGENTS.md

.gitattributes

@@ -1,15 +1,11 @@
-# Needed for publishing of examples, build worker defaults to core.autocrlf=input.
-* text eol=autocrlf
+* text=auto eol=lf
 
-*.mof   text eol=crlf
-*.sh    text eol=lf
-*.svg   eol=lf
+*.bat text eol=crlf
+*.cmd text eol=crlf
 
-# Ensure any exe files are treated as binary
-*.exe binary
+*.gif binary
+*.ico binary
+*.jpeg binary
 *.jpg binary
-*.xl* binary
-*.pfx binary
+*.pdf binary
 *.png binary
-*.dll binary
-*.so  binary

.github/CODEOWNERS

@@ -1,50 +1 @@
-# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
-# Each line is a file pattern followed by one or more owners.
-
-# These owners will be the default owners for everything in
-# the repo. Unless a later match takes precedence,
-# @global-owner1 and @global-owner2 will be requested for
-# review when someone opens a pull request.
-* @PSModule/module-maintainers
-
-# Order is important; the last matching pattern takes the most
-# precedence. When someone opens a pull request that only
-# modifies JS files, only @js-owner and not the global
-# owner(s) will be requested for a review.
-# *.js    @js-owner
-
-# You can also use email addresses if you prefer. They'll be
-# used to look up users just like we do for commit author
-# emails.
-# *.go docs@example.com
-
-# Teams can be specified as code owners as well. Teams should
-# be identified in the format @org/team-name. Teams must have
-# explicit write access to the repository. In this example,
-# the octocats team in the octo-org organization owns all .txt files.
-# *.txt @octo-org/octocats
-
-# In this example, @doctocat owns any files in the build/logs
-# directory at the root of the repository and any of its
-# subdirectories.
-# /build/logs/ @doctocat
-
-# The `docs/*` pattern will match files like
-# `docs/getting-started.md` but not further nested files like
-# `docs/build-app/troubleshooting.md`.
-# docs/*  docs@example.com
-
-# In this example, @octocat owns any file in an apps directory
-# anywhere in your repository.
-# apps/ @octocat
-
-# In this example, @doctocat owns any file in the `/docs`
-# directory in the root of your repository and any of its
-# subdirectories.
-# /docs/ @doctocat
-
-# In this example, @octocat owns any file in the `/apps`
-# directory in the root of your repository except for the `/apps/github`
-# subdirectory, as its owners are left empty.
-# /apps/ @octocat
-# /apps/github
+* @MariusStorhaug

.github/CODE_OF_CONDUCT.md

@@ -13,60 +13,60 @@ While acknowledging differences in social norms, we all strive to meet our commu
 With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
 
 1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
-1. Engaging **kindly and honestly** with others.
-1. Respecting **different viewpoints** and experiences.
-1. **Taking responsibility** for our actions and contributions.
-1. Gracefully giving and accepting **constructive feedback**.
-1. Committing to **repairing harm** when it occurs.
-1. Behaving in other ways that promote and sustain the **well-being of our community**.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
 
 ## Restricted Behaviors
 
 We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
 
 1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
-1. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
-1. **Stereotyping or discrimination.** Characterizing anyone's personality or behavior on the basis of immutable identities or traits.
-1. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
-1. **Violating confidentiality.** Sharing or acting on someone's personal or private information without their permission.
-1. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
-1. Behaving in other ways that **threaten the well-being** of our community.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
 
 ### Other Restrictions
 
 1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
-1. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
-1. **Promotional materials.** Sharing marketing or other commercial content in a way that is outside the norms of the community.
-1. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
 
 ## Reporting an Issue
 
 Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
 
-When an incident does occur, it is important to report it promptly. To report a possible violation, email [psmodule@psmodule.io](mailto:psmodule@psmodule.io).
+When an incident does occur, it is important to report it promptly. To report a possible violation, email [support@psmodule.io](mailto:support@psmodule.io).
 
 Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
 
 ## Addressing and Repairing Harm
 
 If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
 
-1. Warning
-   1. Event: A violation involving a single incident or series of incidents.
-   1. Consequence: A private, written warning from the Community Moderators.
-   1. Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
-1. Temporarily Limited Activities
-   1. Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
-   1. Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
-   1. Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
-1. Temporary Suspension
-   1. Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
-   1. Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
-   1. Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
-1. Permanent Ban
-   1. Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
-   1. Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
-   1. Repair: There is no possible repair in cases of this severity.
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
 
 This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
 
@@ -78,6 +78,6 @@ This Code of Conduct applies within all community spaces, and also applies when
 
 This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
 
-Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/).
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
 
-For answers to common questions about Contributor Covenant, see the [FAQ](https://www.contributor-covenant.org/faq). [Translations](https://www.contributor-covenant.org/translations) are available. Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla's code of conduct team](https://github.com/mozilla/inclusion).
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).

.github/CONTRIBUTING.md

@@ -1,45 +1,38 @@
-<!--
-    https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors
--->
-
-# Welcome to PSModule contributing guide
-
-Thank you for investing your time in contributing to this project!
-
-Before you get started, please review the following guidelines:
-Read our [Code of Conduct](./CODE_OF_CONDUCT.md) to keep our community approachable and respectable.
-
-In this guide you will get an overview of the contribution workflow from opening an issue to get your contribution published.
-
-## New contributors
-
-To get an overview of the project, read the [PSModule readme](../profile/README.md).
-
-Here are some resources to help you get started with open source contributions:
-
-- [Finding ways to contribute to open source on GitHub](https://docs.github.com/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)
-- [Set up Git](https://docs.github.com/get-started/quickstart/set-up-git)
-- [GitHub flow](https://docs.github.com/get-started/quickstart/github-flow)
-- [Collaborating with pull requests](https://docs.github.com/github/collaborating-with-pull-requests)
-
-## Contribution guidelines
-
-![Contributing flow](../profile/contributionflow.png)
-
-1. Open an issue or indicate that you want any of the open issues, so others know what you are working on.
-1. Fork the repository.
-1. Create a branch from `main` and make your changes.
-   1. Write the tests showing the desired functionality first.
-   1. Write the code that makes the tests pass.
-1. Open a pull request towards `upstream/main` as a draft.
-   - Add any details using the PR template.
-   - Link the PR to the issue you opened by adding `- Fixes #<issue_number>` so that the issue gets associated and closed with the PR.
-1. **Review your own PR first!** When you are happy with it, mark it as "Ready for review".
-1. Review and address comments on your pull request.
-   - We do not want to close PRs directly if we disagree on a specific approach. Lets discuss it instead. We are happy to help you with your changes if there are some difficult points in the code or framework.
-   - Update your branch with the latest changes from `upstream/main` before your PR is merged.
-1. Once your pull request is approved, it will be merged and a new feature will be released immediately.
-
-> [!IMPORTANT]
-> In rare occation we might create a release branch and do a release from that branch, but that is more for bigger changes.
-> These branches might also run with a prerelease tag, so that we can test the changes before we release it to the public.
+# Contributing
+
+The affected repository's README and repository-local contribution guidance
+define its build, test, and validation steps. Follow those local instructions
+before this organization-wide fallback.
+
+## Before making a change
+
+- Review the repository's open issues and use the MSX
+  [issue process](https://msx.no/docs/Ways-of-Working/Issues/) to propose or
+  claim substantial work.
+- Read the repository's code of conduct and applicable PSModule and MSX
+  standards.
+- Keep each change focused on one deliverable.
+
+## Agent plugins
+
+The [MSX agent plugin marketplace](https://github.com/MSXOrg/docs/tree/main/.github/plugin)
+provides shared standards and workflow skills. The
+[PSModule process plugin](https://github.com/PSModule/Process-PSModule/tree/main/.github/plugin)
+provides initiative-specific guidance for Process-PSModule repositories.
+
+## Submit the change
+
+1. Create a short-lived branch from the repository's default branch.
+2. Make the smallest complete change and run the repository's relevant checks.
+3. Open a draft pull request and follow the MSX
+   [PR Format](https://msx.no/docs/Ways-of-Working/PR-Format/).
+4. Self-review the diff, request Copilot review explicitly, and address
+   in-scope feedback.
+5. Mark the pull request ready only after it satisfies the repository's review
+   gate.
+
+The canonical
+[Contribution Workflow](https://msx.no/docs/Ways-of-Working/Contribution-Workflow/)
+defines the complete delivery loop. Use the MSX
+[Review Etiquette](https://msx.no/docs/Ways-of-Working/Review-Etiquette/) when
+giving or responding to feedback.