work in progress

.github/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "1.2.0"
+}

.github/CODEOWNERS

@@ -0,0 +1,79 @@
+# This is a comment.
+# 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.
+# *       @global-owner1 @global-owner2
+
+# 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-experts  #This is an inline comment.
+
+# 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 [email protected]
+
+# 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
+
+# Terraform Files
+# *.tf                                    @terraform-experts
+# .terraform-docs.yaml                    @terraform-experts
+
+# SQL Files
+# *.sql                                   @sql-experts
+# *.sqlproj                               @sql-experts
+
+# SSIS Files
+# *.dtsx                                  @ssis-experts
+# *.params                                @ssis-experts
+# *.conmgr                                @ssis-experts
+# *.database                              @ssis-experts
+# *.dtproj                                @ssis-experts
+
+# 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/*  [email protected]
+
+# 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, any change inside the `/scripts` directory
+# will require approval from @doctocat or @octocat.
+# /scripts/ @doctocat @octocat
+
+# In this example, @octocat owns any file in a `/logs` directory such as
+# `/build/logs`, `/scripts/logs`, and `/deeply/nested/logs`. Any changes
+# in a `/logs` directory will require approval from @octocat.
+# **/logs @octocat
+
+# 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
+
+# Technical Steering Committee should be in charge of reviewing any changes
+# to automations (because they should be centralized, shared, and standardized)
+# as well as changes to key governance and control files or documents
+# .github/*                      @tsc

.github/ISSUE_TEMPLATE/bug-report---.md

@@ -6,17 +6,22 @@ labels: bug
 ---
 
 ## Describe the bug
+
 A clear and concise description of what the bug is.
 
 ### Steps to reproduce
+
 Steps to reproduce the behavior.
 
 ### Expected behavior
+
 A clear and concise description of what you expected to happen.
 
 ### Environment
- - OS: [e.g. Arch Linux]
- - Other details that you think may affect.
+
+- OS: [e.g. Arch Linux]
+- Other details that you think may affect.
 
 ### Additional context
-Add any other context about the problem here.
+
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature-request---.md

@@ -6,10 +6,13 @@ labels: enhancement
 ---
 
 ## Summary
+
 Brief explanation of the feature.
 
 ### Basic example
+
 Include a basic example or links here.
 
 ### Motivation
-Why are we doing this? What use cases does it support? What is the expected outcome?
+
+Why are we doing this? What use cases does it support? What is the expected outcome?

.github/dependabot.yml

@@ -0,0 +1,11 @@
+version: 2
+updates:
+  - package-ecosystem: 'github-actions'
+    directory: '/.github/workflows'
+    schedule:
+      interval: 'daily'
+    labels:
+      - '📦 Dependencies'
+      - '🚀 CI/CD'
+    commit-message:
+      prefix: 'chore(deps-ci): Update GHA Dependencies'

.github/pr-scope-labeler.yml

@@ -0,0 +1,71 @@
+# This file is used to configure the PR Scope Labeler action
+# in .github/workflows/pr-controls.yml
+💻 Source:
+  - changed-files:
+      - any-glob-to-any-file:
+          - src/**
+
+🧪 Tests:
+  - changed-files:
+      - any-glob-to-any-file:
+          - tests/**
+          - vitest*config*.ts
+          - .env.test
+
+📝 Documentation:
+  - changed-files:
+      - any-glob-to-any-file:
+          - docs/**
+          - README*
+          - images/**
+
+🐳 Build:
+  - changed-files:
+      - any-glob-to-any-file:
+          - .dockerignore
+          - Dockerfile
+          - docker-compose.yml
+          - .nvmrc
+          - .swcrc
+          - tsconfig*.json
+
+⚙️ Configuration:
+  - changed-files:
+      - any-glob-to-any-file:
+          - .dockerignore
+          - .editorconfig
+          - .env*
+          - .eslintignore
+          - .eslintrc
+          - .gitignore
+          - .npmignore
+          - .npmrc
+          - .nvmrc
+          - .prettierignore
+          - .swcrc
+          - .yamllint.yml
+          - '*config*.ts'
+          - '*.config.mjs'
+          - tsconfig*.json
+
+📦 Dependencies:
+  - changed-files:
+      - any-glob-to-any-file:
+          - package.json
+          - package-lock.json
+
+🚀 CI/CD:
+  - changed-files:
+      - any-glob-to-any-file:
+          - .github/workflows/**
+          - .github/dependabot.yml
+          - .github/pr-scope-labeler.yml
+
+🔧 Github Configuration:
+  - changed-files:
+      - any-glob-to-any-file:
+          - .github/ISSUE_TEMPLATE/**
+          - .github/CODEOWNERS
+          - .github/PULL_REQUEST_TEMPLATE.md
+          - .github/settings.yml
+          - .github/workflows/repo-gov.yml

.github/release-please-config.json

@@ -0,0 +1,23 @@
+{
+  "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json",
+  "release-search-depth": 400,
+  "group-pull-request-title-pattern": "chore${scope}: Release ${component} v${version}",
+  "pull-request-title-pattern": "chore${scope}: Release ${component} v${version}",
+  "packages": {
+    ".": {
+      "pull-request-title-pattern": "chore${scope}: Release v${version}",
+      "tag-separator": "@",
+      "include-v-in-tag": true,
+      "changelog-path": "CHANGELOG.md",
+      "release-type": "simple",
+      "bump-minor-pre-major": false,
+      "bump-patch-for-minor-pre-major": false,
+      "draft": false,
+      "prerelease": false,
+      "exclude-paths": [".github"],
+      "include-component-in-tag": false,
+      "extra-files": []
+    }
+  },
+  "plugins": []
+}

.github/settings.yml

@@ -0,0 +1,142 @@
+# See https://github.com/marketplace/actions/manage-administrative-repository-settings-from-pull-requests for details
+collaborators:
+  # Especially useful if the repository is private or part of an organization
+
+settings:
+  # Useful if you have default repo settings you wish to apply when creating a new repo
+
+labels:
+  # Useful to blow out a lot of standard labels and make busy PR / Issue screens easier on eyes
+  # Colors can be researched at https://hexcolor16.com
+  - name: bug
+    description: Bug identified
+    color: D73A4A
+    new_name: 🐞 Bug
+
+  - name: documentation
+    description: Improvements or additions to documentation
+    color: 228AFF # 0075ca
+    new_name: 📝 Documentation
+
+  - name: duplicate
+    description: This issue or pull request already exists
+    color: 7A5901 # cfd3d7
+    new_name: 💩 Duplicate
+
+  - name: enhancement
+    description: Feature added in the PR
+    color: A2EEEF
+    new_name: ✅ Feature
+
+  - name: 'good first issue'
+    description: Good for newcomers
+    color: 7057ff
+    new_name: 👶 Good First Issue
+
+  - name: 'help wanted'
+    description: Extra attention is needed
+    color: 008672
+    new_name: 🆘 Help Wanted
+
+  - name: invalid
+    description: This doesn't seem right
+    color: E4E669
+    new_name: 🚫 Invalid
+
+  - name: question
+    description: Further information is requested
+    color: D876E3
+    new_name: ❓ Question
+
+  - name: wontfix
+    description: This will not be worked on
+    color: FFFFFF
+    new_name: 🙅‍♂️ Wontfix
+
+  - name: ⚠️ Breaking Change
+    description: Breaking change in the PR
+    color: F1F800
+
+  - name: 🐳 Build
+    description: Indicates the change is related to the build
+    color: 0FD4DA
+
+  - name: 🚀 CI/CD
+    description: Indicates the change is related to CI/CD workflows
+    color: FF4D4D
+
+  - name: ⚙️ Configuration
+    description: Indicates the scope is related to the configuration
+    color: BDBDBD
+
+  - name: 📦 Dependencies
+    description: Pull requests that update a dependency file
+    color: 228AFF
+
+  - name: 👀 Feature Requested
+    description: Request for a feature
+    color: 07D90A
+
+  - name: 🕵🏻 Fix
+    description: Fix applied in the PR
+    color: F4D03F
+
+  - name: 🔧 Github Configuration
+    description: Indicates the change is related to github settings
+    color: '555555'
+
+  - name: 💻 Source
+    description: Indicates the scope is related to the own service logic
+    color: FDC720
+
+  - name: 🧪 Tests
+    description: Indicates the scope is related to the tests
+    color: 088E26
+
+  - name: 🤩 size/xs
+    description: Pull request size XS
+    color: 27AE60
+
+  - name: 🥳 size/s
+    description: Pull request size S
+    color: 2ECC71
+
+  - name: 😎 size/m
+    description: Pull request size M
+    color: F1C40F
+
+  - name: 😖 size/l
+    description: Pull request size L
+    color: F39C12
+
+  - name: 🤯 size/xl
+    description: Pull request size XL
+    color: E67E22
+
+  - name: ignore-for-release
+    description: Ignore pull request for a new release
+    color: EDEDED
+
+  - name: 'autorelease: tagged'
+    description: Used by release-please to indicate a release has been tagged
+    color: EDEDED
+
+  - name: 'autorelease: pending'
+    description: Used by release-please to indicate a release is pending
+    color: EDEDED
+
+branch_protections:
+  # Great if you have standards of practice to require certain checks before merging PRs
+
+environments:
+  # Useful if you have a multi-stage deployment process and want to enforce certain checks before deploying to production
+
+secrets:
+  # Useful if you have a standard set of secrets you want to ensure are always present in the repository
+
+variables:
+  # Useful if you have a standard set of environment variables you want to ensure are always present in the repository
+
+batch_file_operations:
+  # Useful if you have a standard set of files you want to ensure are always present in the repository
+  # or if you want to centrally manage common / shared files across multiple repositories