Develop to main

.agent/local-agent.example.json

@@ -0,0 +1,10 @@
+{
+  "repo": "ktalpay/CarbonOps-Parser",
+  "source_root": "/Users/oxygen/dev/CarbonOps/Parser/Source/CarbonOps-Parser",
+  "agents_root": "/Users/oxygen/FutureOps/Agents/CarbonOps-Parser",
+  "base_branch": "develop",
+  "validation_mode": "minimal",
+  "python_bin": "python",
+  "runner_script_path": "/Users/oxygen/dev/CarbonOps/Parser/Source/CarbonOps-Parser/scripts/local_codex_task_runner.py",
+  "log_directory": "/Users/oxygen/FutureOps/Agents/CarbonOps-Parser/.logs"
+}

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @ktalpay

.github/ISSUE_TEMPLATE/bug_report.md

@@ -10,6 +10,10 @@ assignees: ""
 
 Describe the issue briefly.
 
+## Production Scope
+
+- [ ] This report does not claim broader production, compliance, legal, source-owner, or carbon-accounting correctness.
+
 ## Checklist
 
 - [ ] I have not included confidential data, credentials, or private source files.
@@ -40,3 +44,6 @@ Describe the issue briefly.
 
 
 ## Actual Result
+
+
+## Validation Tried

.github/ISSUE_TEMPLATE/documentation_request.md

@@ -0,0 +1,33 @@
+---
+name: Documentation request
+about: Request a documentation correction, clarification, or new docs page
+title: "[Docs]: "
+labels: documentation
+assignees: ""
+---
+
+## Summary
+
+Describe the documentation change.
+
+## Affected Page
+
+Link to the page or section.
+
+## Suggested Change
+
+Describe the requested wording, example, or explanation.
+
+## Implementation Target
+
+- [ ] Python
+- [ ] .NET
+- [ ] Docs
+- [ ] Database
+- [ ] Shared
+
+## Checklist
+
+- [ ] I have not included confidential data, credentials, private source files, or private connection strings.
+- [ ] This request preserves the documented production-ready scope.
+- [ ] This request does not add package publishing, compliance, legal, source-owner, or carbon-accounting correctness claims.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -15,6 +15,7 @@ Describe the proposed improvement.
 - [ ] I have not included confidential data, credentials, or private source files.
 - [ ] I included the source name and version or file name when relevant.
 - [ ] I selected the implementation target below.
+- [ ] I understand source-specific ingestion, parser, database, scheduler, downloader, package publishing, or production promotion work must be explicitly scoped.
 
 ## Implementation Target
 
@@ -31,3 +32,8 @@ Describe the proposed improvement.
 
 
 ## Out Of Scope
+
+
+## Production-Ready Scope
+
+Describe how this feature preserves the current narrow production-ready scope.

.github/ISSUE_TEMPLATE/production_readiness_question.md

@@ -0,0 +1,34 @@
+---
+name: Production-readiness question
+about: Ask whether a use case is inside or outside the documented production-ready scope
+title: "[Production Readiness]: "
+labels: question
+assignees: ""
+---
+
+## Question
+
+Describe the scope question.
+
+## Intended Use
+
+Describe the runtime, workflow, source family, or PostgreSQL operator path involved.
+
+## Implementation Target
+
+- [ ] Python
+- [ ] .NET
+- [ ] Docs
+- [ ] Database
+- [ ] Shared
+
+## Source Context
+
+- Source family:
+- Source version or file name:
+
+## Checklist
+
+- [ ] I have not included credentials, private connection strings, private source files, or production infrastructure secrets.
+- [ ] I understand maintainers may classify this as outside the current production-ready scope.
+- [ ] I am not requesting a compliance, legal, source-owner, factor-correctness, or carbon-accounting correctness guarantee.

.github/pull_request_template.md

@@ -2,28 +2,49 @@
 
 Briefly describe the task and outcome.
 
-## Changes
+## Scope
 
 -
 
-## Validation
+## Runtime Impact
+
+- [ ] No Python runtime behavior changed
+- [ ] No .NET runtime behavior changed
+- [ ] Runtime behavior changed and is described here:
+
+## Validation Performed
 
 - [ ] Tests/checks run and listed:
 - [ ] `git diff --check` passed
 
-## Scope Guard Checklist
+## PostgreSQL Impact
+
+- [ ] No PostgreSQL behavior, schema, migration, or operator workflow changed
+- [ ] PostgreSQL docs/checklists changed and are described here:
+- [ ] PostgreSQL runtime behavior changed and is described here:
+
+## Docs Impact
+
+- [ ] No docs changed
+- [ ] Docs changed and are described here:
+
+## Secrets And Artifacts Checklist
 
 - [ ] No confidential data
-- [ ] No production/compliance/legal claims
+- [ ] No credentials, private connection strings, private source files, or production secrets
+- [ ] No generated artifacts, build outputs, caches, database dumps, downloaded source files, or local test output
+
+## Production-Ready Claim Checklist
+
 - [ ] No source-specific ingestion unless requested
 - [ ] No parser/database/scheduler/downloader coupling unless requested
 - [ ] No external dependencies unless requested
-- [ ] One commit only
-- [ ] Tests/checks run and listed
+- [ ] No broader production, compliance, legal, source-owner, package publishing, or carbon-accounting correctness claims
+- [ ] Production-ready wording stays within the documented narrow supported scope
 
-## Deferred Items
+## Maintainer Merge Reminder
 
--
+Only maintainers merge pull requests. Contributors should not self-merge or imply merge authority.
 
 ## Reviewer Notes
 

.github/workflows/README.md

@@ -1,7 +1,23 @@
 # GitHub Workflows
 
-CI workflows are intentionally not configured yet.
+CI includes a Phase 1 release validation gate in
+`release-validation.yml`.
 
-Workflows should be added after implementation and test structure exist for the Python and .NET paths. Until then, the repository uses documentation and review checklists instead of workflow YAML files.
+The release gate validates a focused Phase 1 Python release-validation test set,
+local static safety boundaries, local source acquisition dry-run behavior, local
+parser fixture dry-run behavior, focused stable .NET production-safety contract
+tests, parity fixture presence, sample config safety, runbook consistency, and
+whitespace cleanliness.
 
-Do not add placeholder workflow YAML files without a task that defines the checks they should run.
+The full Python test suite, full .NET contract suite, and full repository
+public-safety validation are intentionally outside the default release gate. The
+full .NET contract suite is outside the default release gate until known
+deterministic parser assertion failures are resolved. They remain separate
+tracked hardening items until baseline/noise cleanup, allowlist support, and
+parser fixture determinism cleanup are available.
+
+The default workflow path is local-only. PostgreSQL integration validation is
+manual and opt-in through the workflow input plus the
+`CARBONOPS_RELEASE_GATE_RUN_INTEGRATION`,
+`CARBONOPS_RUN_POSTGRESQL_INTEGRATION`, and externally supplied
+`CARBONOPS_POSTGRESQL_TEST_DSN` controls.