Migrate to OpenPhysical organization and release v2.0.0

Major changes:
- Update all repository references from mistial-dev to OpenPhysical
- Reorganize documentation structure (move docs to docs/ directory)
- Enhance README with professional tone and clear technical focus
- Add comprehensive badge collection for project status
- Update pre-commit configuration with specific commit hashes
- Fix all markdown linting and editorconfig violations
- Polish policy language for inclusivity while maintaining firm boundaries
- Move humor elements to appropriate context in FAQ

Author: mistial-dev

.editorconfig

@@ -14,7 +14,7 @@ indent_size = 2
 
 # Markdown files
 [*.md]
-max_line_length = 120
+max_line_length = 160
 trim_trailing_whitespace = true
 
 # YAML files
@@ -27,4 +27,4 @@ indent_size = 2
 
 # Package.json
 [package.json]
-indent_size = 2
+indent_size = 2

.gitattributes

@@ -20,4 +20,4 @@
 
 # Archives
 *.zip binary
-*.tar.gz binary
+*.tar.gz binary

.github/ISSUE_TEMPLATE/config.yml

@@ -11,4 +11,4 @@ contact_links:
     about: Understand the policy principles before contributing
   - name: Implementation Examples
     url: https://github.com/mistial-dev/BoundedContributionPolicy/blob/main/EXAMPLES.md
-    about: See how others have implemented the policy
+    about: See how others have implemented the policy

.github/ISSUE_TEMPLATE/policy_clarification.md

@@ -31,4 +31,5 @@ Explain the project type or situation where this clarification would be helpful:
 Any thoughts on how this should be implemented or potential challenges.
 
 ---
-**Note:** This repository focuses on practical improvements to the Bounded Contribution Policy framework. Please ensure your issue relates to policy implementation, clarification, or supporting resources.
+**Note:** This repository focuses on practical improvements to the Bounded Contribution Policy framework.
+Please ensure your issue relates to policy implementation, clarification, or supporting resources.

.github/PULL_REQUEST_TEMPLATE.md

@@ -37,6 +37,7 @@ Describe the specific modifications made and why.
 - [ ] Checked for unintended consequences
 
 ### Quality Assurance
+
 - [ ] All markdown files pass linting (`npm run lint:md`)
 - [ ] Line lengths follow project guidelines
 - [ ] Links are functional and point to correct resources
@@ -90,8 +91,8 @@ Steps for reviewers to verify the changes:
 ---
 **Policy Compliance:** This contribution follows the [Bounded Contribution Policy](../CODE_OF_CONDUCT.md) with focus on technical value and project relevance.
 
-<!-- 
-For maintainers: Remember the "Sir, this is a Wendy's" principle - 
-keep discussions focused on the practical aspects of policy implementation 
+<!--
+For maintainers: Remember the "Sir, this is a Wendy's" principle -
+keep discussions focused on the practical aspects of policy implementation
 rather than philosophical debates about contribution policies in general.
 -->

.github/workflows/markdown-lint.yml

@@ -9,44 +9,44 @@ on:
 jobs:
   pre-commit:
     runs-on: ubuntu-latest
-    
+
     steps:
     - name: Checkout repository
       uses: actions/checkout@v4
-      
+
     - name: Setup Python
       uses: actions/setup-python@v5
       with:
         python-version: '3.x'
-        
+
     - name: Setup Node.js
       uses: actions/setup-node@v4
       with:
         node-version: '18'
         cache: 'npm'
-        
+
     - name: Install npm dependencies
       run: npm ci
-      
+
     - name: Run pre-commit
       uses: pre-commit/action@v3.0.1
-      
+
   verify:
     runs-on: ubuntu-latest
     needs: pre-commit
-    
+
     steps:
     - name: Checkout repository
       uses: actions/checkout@v4
-        
+
     - name: Verify policy file exists
       run: |
         if [ ! -f "CODE_OF_CONDUCT.md" ]; then
           echo "❌ CODE_OF_CONDUCT.md (Bounded Contribution Policy) is missing"
           exit 1
         fi
         echo "✅ Bounded Contribution Policy found"
-        
+
     - name: Check for broken internal links
       run: |
         echo "Checking for broken internal markdown links..."
@@ -55,4 +55,4 @@ jobs:
           echo "❌ Found references to old BOUNDED_CONTRIBUTION_POLICY.md file"
           exit 1
         fi
-        echo "✅ No broken internal links found"
+        echo "✅ No broken internal links found"

.gitignore

@@ -26,4 +26,4 @@ logs
 
 # Temporary files
 *.tmp
-*.temp
+*.temp

.markdownlint.json

@@ -15,4 +15,4 @@
   "MD036": false,
   "MD040": false,
   "MD041": false
-}
+}

.pre-commit-config.yaml

@@ -1,6 +1,6 @@
 repos:
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v4.6.0
+    rev: 3e8a8703264a2f4a69428a0aa4dcb512790b2c8c  # v6.0.0
     hooks:
       - id: trailing-whitespace
       - id: end-of-file-fixer
@@ -10,20 +10,16 @@ repos:
       - id: mixed-line-ending
         args: ['--fix=lf']
 
-  - repo: https://github.com/igorshubovych/markdownlint-cli
-    rev: v0.41.0
+  - repo: https://github.com/DavidAnson/markdownlint-cli2
+    rev: d7a4f7cf4914d3bffb9b83bdbc45fd2a00c91ff9  # v0.18.1
     hooks:
-      - id: markdownlint
+      - id: markdownlint-cli2
         args: [--config, .markdownlint.json]
         exclude: node_modules
 
-  - repo: https://github.com/nvuillam/markdown-table-formatter
-    rev: v1.6.0
-    hooks:
-      - id: markdown-table-formatter
-
   - repo: https://github.com/editorconfig-checker/editorconfig-checker.python
-    rev: '2.7.3'
+    rev: 61529b21391331d7cfd1f191df6293534a1fd79a  # 3.4.0
     hooks:
       - id: editorconfig-checker
-        alias: ec
+        alias: ec
+        exclude: node_modules

CODE_OF_CONDUCT.md

@@ -1,42 +1,55 @@
 # Bounded Contribution Policy
 
-**Version 1.2.0** | [Changelog](docs/CHANGELOG.md)
+**Version 2.0.0** | [Changelog](docs/CHANGELOG.md)
 
 ## Our Standards
 
-This project is dedicated to building and maintaining a specific technical product. To support that goal, all contributions and discussions must align with the following principles:
+This project welcomes technical contributions from people of all backgrounds. We focus on building and maintaining specific technical products.
+To help everyone contribute effectively, all discussions and contributions should align with these principles:
 
 ### Project Relevance
 
-All contributions must directly support the project's technical goals. Off-topic discussions, regardless of intent, are out of scope.
+All contributions must directly support the project's technical goals.
+Off-topic discussions, regardless of intent, are out of scope.
 
 ### Individual Evaluation
 
-Contributions are evaluated individually, based on their technical value and relevance to the project. Personal identity, background, seniority, or organizational affiliation do not factor into acceptance decisions.
+Each contribution is evaluated based on its technical merit and relevance to the project.
+Personal identity, background, seniority, or organizational affiliation do not factor into acceptance decisions.
 
 ### Focused Communication
 
-Discussions should be clear, concise, and directly related to the problem at hand. Extended commentary or general debate is discouraged unless it advances the project's technical objectives.
+Discussions should be clear, concise, and directly related to the problem at hand.
+Extended commentary or general debate is discouraged unless it advances the project's technical objectives.
 
 ### Constructive Interaction
 
-Feedback should be specific, actionable, and directed toward improving the work. General critique without context or suggested improvements is not helpful to the project.
+Feedback must be specific, actionable, and directed toward improving the work.
+General critique without technical context or suggested improvements does not advance the project.
 
-Appropriate humor that reinforces project focus (such as gentle redirects to scope) is welcome when it maintains professional tone and supports productive collaboration.
+Appropriate humor that reinforces project focus (such as gentle redirects to scope) is welcome
+when it maintains professional tone and supports productive collaboration.
 
 ### Maintainer Discretion
 
-Project maintainers are not obligated to respond to all input. Engagement is prioritized based on project needs, technical relevance, and available resources.
+Project maintainers are not obligated to respond to all input.
+Engagement is prioritized based on project needs, technical relevance, and available resources.
 
 ### Neutral Environment
 
-This project maintains a neutral technical focus. Social, political, or ideological discussions are outside the project's scope. Participation must reflect this technical orientation.
+This project maintains a neutral technical focus.
+Social, political, or ideological discussions are outside the project's scope.
+All participation must reflect this technical orientation.
 
 ## Enforcement
 
-These principles will be applied consistently. Violations may result in rejection of contributions, removal of access, or other actions deemed necessary by project maintainers to maintain project focus.
+These principles are applied consistently to all participants.
+Violations will result in rejection of contributions, removal of access,
+or other actions necessary to maintain project focus.
 
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that do not align with this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues,
+and other contributions that do not align with this Code of Conduct,
+and will communicate reasons for moderation decisions when appropriate.
 
 ## Scope
 
@@ -48,4 +61,5 @@ This Code of Conduct applies within all project spaces, including but not limite
 
 ## Purpose
 
-The Bounded Contribution Policy provides a framework for maintaining focused, productive technical collaboration by establishing clear boundaries around project scope and contribution evaluation criteria.
+The Bounded Contribution Policy provides a framework for maintaining focused, productive technical collaboration
+by establishing clear boundaries around project scope and contribution evaluation criteria.