feat(community): operationalize contribution workflow

[openai0229]

Related issue

Closes #1937

Summary

• Publish the Community ownership, response, contribution-boundary, Ready-task, Project, Milestone, and Release contracts.
• Add a generic maintainer Task form and validate the public operations configuration in CI.
• Add source-controlled Project lifecycle synchronization for Issue and pull request events.
• Repair the existing localization source-hash baseline so the frontend CI gate can become required.

Affected surfaces

• Frontend / Web
• Backend / API / Storage
• Database plugin / Driver
• JCEF / Desktop packaging
• CI / Build / Release
• Documentation only

Verification

• Commands and results:
  • node --test script/github/issue-claim.test.js script/github/sync-community-project.test.js - 30 tests passed.
  • ruby script/github/validate-community-operations.rb - 9 boundaries and all contracts validated.
  • ruby YAML parse for .github/**/*.yml and .github/**/*.yaml - passed.
  • node ./scripts/validate-i18n.cjs from chat2db-community-client - passed for 25 modules, two properties bundles, and five READMEs.
  • actionlint .github/workflows/community-project-sync.yml .github/workflows/ci.yml - passed.
  • git diff --check - passed.
• Manual verification: Ran the Project reconciler against Community Project Bug:  #3 with an authenticated project-scoped token; closed items remained Done and open PR feat(ai): standardize AI tool results as JSON #1876 moved to In Review.
• UI evidence: N/A - repository operations and workflow change.

Risk and compatibility

• Public API or stored data: N/A - no product API or persisted workspace data changes.
• Database or driver compatibility: N/A - no database implementation changes.
• Network, privacy, or security: The Project workflow uses the existing ACCESS_TOKEN secret only in a trusted default-branch checkout and never checks out pull request code.
• Community / Local / Pro boundary: Explicitly documents and validates that commercial-edition work is outside the public Community contribution queue.
• Backward compatibility: Existing labels, Issue forms, claim commands, and Project fields remain compatible.

Reviewer map

• Start here: .github/COMMUNITY_OPERATIONS.md, then .github/workflows/community-project-sync.yml and script/github/sync-community-project.js.
• Failure condition: New Issues or linked pull requests do not reach the documented Project state, operations validation fails, or the frontend i18n check remains red.
• Rollback or disable path: Disable community-project-sync.yml; Project fields and Issues remain intact and can be managed manually.

Contributor declaration

• I linked the Issue that defines this change.
• I tested the affected behavior and reported the actual results above.
• I did not include credentials, private data, or generated build output.
• I disclosed substantial AI assistance below, or this PR contains no substantial AI-generated code.

AI assistance: Codex was used to inspect the repository, draft the operations contracts and automation, and run the reported verification.

[github-actions]

Reviewed e465eb7. Findings: 0 critical, 1 high, 1 medium. Merge recommendation: request changes because reopened contribution-ready issues are assigned an incorrect lifecycle status; the Project pagination gap should also be fixed so reconciliation covers the full board. Coverage was limited to the GitHub-provided current diff, with highest-risk review focused on the Project workflow, synchronizer, tests, CI, and operations configuration. No tests or runtime checks were run.

``

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by AI Pull Request Reviewer for #1939 · 13.2 AIC · ⌖ 4.46 AIC · ⊞ 17.7K

Addressed both findings in the latest commits: reopened task state now uses the eligibility fallback, Project item loading is paginated, and focused tests cover both cases.