Add repository-local community guidance

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: MariusStorhaug

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,164 @@
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the
+dignity, rights, and contributions of all individuals, regardless of
+characteristics including race, ethnicity, caste, color, age, physical
+characteristics, neurodiversity, disability, sex or gender, gender identity or
+expression, sexual orientation, language, philosophy or religion, national or
+social origin, socio-economic position, level of education, or other status.
+The same privileges of participation are extended to everyone who participates
+in good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our
+community's expectations for positive behavior. We also understand that our
+words and actions may be interpreted differently than we intend based on
+culture, background, or native language.
+
+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**.
+
+## 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.
+
+### 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.
+
+## 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).
+
+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 community spaces after the
+      period is over.
+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.
+
+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.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public or other
+spaces. Examples of representing our community include using an official email
+address, posting via an official social media account, or acting as an
+appointed representative at an online or offline event.
+
+## Attribution
+
+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/).
+
+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).

.github/CONTRIBUTING.md

@@ -0,0 +1,54 @@
+# Contributing
+
+Thank you for investing your time in contributing to this repository.
+Read the [Code of Conduct](CODE_OF_CONDUCT.md) before participating, and read
+[`AGENTS.md`](../AGENTS.md) for the full guidance chain and documentation
+references.
+
+## Before you start
+
+1. Read [`README.md`](../README.md) to understand what Process-PSModule does.
+2. Familiarize yourself with the
+   [repository standard](https://psmodule.io/Process-PSModule/reference/repository-standard/).
+3. Check the open issues and pull requests to avoid duplicate work.
+
+## Workflow
+
+This project follows the
+[MSX contribution workflow](https://msx.no/docs/Ways-of-Working/Contribution-Workflow/):
+
+1. Open or pick up an issue that describes the change.
+2. Create a branch from `main` following the
+   `<type>/<issue>-<short-slug>` convention.
+3. Make small, focused commits and push often.
+4. Open a **draft pull request** as soon as the change has a basic shape.
+5. Run the **Copilot review loop** until it reports a clean round. File an issue
+   for out-of-scope findings.
+6. Mark the pull request ready for review and enable auto-merge.
+
+For branching details, see
+[Branching and Merging](https://msx.no/docs/Ways-of-Working/Branching-and-Merging/).
+
+## Pull requests
+
+- Keep pull requests small and focused on a single deliverable.
+- Follow the
+  [commit conventions](https://msx.no/docs/Ways-of-Working/Commit-Conventions/).
+- Follow the
+  [pull request format](https://msx.no/docs/Ways-of-Working/PR-Format/).
+
+## Issues
+
+Use GitHub Issues to report bugs, request features, or propose improvements.
+Follow the
+[issue format](https://msx.no/docs/Ways-of-Working/Issues/Process/Format/).
+
+## Code standards
+
+PowerShell and GitHub Actions in this repository follow the
+[PSModule framework guidance](https://psmodule.io/Process-PSModule/) and the
+[MSX coding standards](https://msx.no/docs/Coding-Standards/).
+
+## Questions
+
+Follow the repository's [support guidance](SUPPORT.md).

.github/SECURITY.md

@@ -0,0 +1,22 @@
+# Security Policy
+
+## Supported versions
+
+Only the latest release is supported. Security fixes are released only for the
+latest version.
+
+## Reporting a vulnerability
+
+Do not disclose a suspected or confirmed vulnerability through a public issue,
+pull request, or discussion.
+
+Report the vulnerability through the repository's **Security** tab by creating
+a private security advisory. If that option is unavailable, email
+[psmodule@psmodule.io](mailto:psmodule@psmodule.io).
+
+Include the affected repository and version, a clear description of the
+vulnerability and its impact, steps to reproduce it, and any proof of concept
+or suggested mitigation.
+
+We handle reports privately, investigate them, and coordinate a fix and
+disclosure with the reporter where possible.

.github/SUPPORT.md

@@ -0,0 +1,22 @@
+# Support
+
+## PSModule support
+
+For help with Process-PSModule, open an issue in this repository. Issues let
+maintainers and other users collaborate on a solution.
+
+For matters that are not suitable for a public issue, contact
+[psmodule@psmodule.io](mailto:psmodule@psmodule.io).
+
+To contribute, see the repository's [contributing guide](CONTRIBUTING.md).
+
+## Security vulnerabilities
+
+Do not report security vulnerabilities through GitHub Issues. Follow the
+repository's [security policy](SECURITY.md) instead.
+
+## PowerShell Gallery support
+
+For PowerShell Gallery support, contact
+[cgadmin@microsoft.com](mailto:cgadmin@microsoft.com) or open an issue in
+[PowerShell/PowerShellGallery](https://github.com/PowerShell/PowerShellGallery/issues).