test

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @Vector897

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,32 @@
+name: Bug report
+description: Report a reproducible problem in Globot.
+title: "[Bug]: "
+labels: [bug, needs-triage]
+body:
+  - type: markdown
+    attributes:
+      value: "Thanks for helping improve Globot. Do not include credentials, personal data, or security vulnerabilities."
+  - type: textarea
+    id: summary
+    attributes:
+      label: What happened?
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce
+      placeholder: "1. ...\n2. ...\n3. ..."
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behaviour
+    validations:
+      required: true
+  - type: input
+    id: environment
+    attributes:
+      label: Environment
+      placeholder: "OS, Python/Node version, browser, commit SHA"

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/Vector897/Globot/blob/main/SECURITY.md
+    about: Do not open a public issue for security reports. Follow the security policy.
+  - name: Support
+    url: https://github.com/Vector897/Globot/blob/main/SUPPORT.md
+    about: How to ask questions and get help.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,21 @@
+name: Feature request
+description: Propose an improvement to Globot.
+title: "[Feature]: "
+labels: [enhancement, needs-triage]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem would this solve?
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed approach
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered

.github/dependabot.yml

@@ -0,0 +1,14 @@
+version: 2
+updates:
+  - package-ecosystem: pip
+    directory: /backend
+    schedule:
+      interval: weekly
+  - package-ecosystem: npm
+    directory: /frontend
+    schedule:
+      interval: weekly
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly

.github/pull_request_template.md

@@ -0,0 +1,14 @@
+## Summary
+
+Describe the problem and the change.
+
+## Validation
+
+- [ ] `python -m compileall -q backend`
+- [ ] `cd frontend && pnpm build`
+- [ ] Documentation updated where needed
+
+## Safety and data
+
+- [ ] No credentials, personal data, or private operational data were added.
+- [ ] Human review remains required for consequential recommendations.

.github/workflows/ci.yml

@@ -0,0 +1,44 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  backend-syntax:
+    name: Backend syntax
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.11'
+      - name: Compile Python sources
+        run: python -m compileall -q backend
+
+  frontend-build:
+    name: Frontend build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: pnpm/action-setup@v4
+        with:
+          version: 11
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+          cache: pnpm
+          cache-dependency-path: frontend/pnpm-lock.yaml
+      - name: Install dependencies
+        working-directory: frontend
+        run: pnpm install --frozen-lockfile
+      - name: Build
+        working-directory: frontend
+        run: pnpm build
+        env:
+          VITE_CLERK_PUBLISHABLE_KEY: pk_test_ci_placeholder
+          VITE_API_BASE_URL: http://localhost:8000

.gitignore

@@ -292,11 +292,3 @@ site/
 # 如果需要忽略自动生成的迁移文件，取消注释：
 # backend/alembic/versions/*.py
 # 但通常建议保留迁移文件
-
-# Ignore all markdown files except README.md
-*.md
-!README.md
-
-
-
-.txt

AGENTS.md

@@ -0,0 +1,21 @@
+# Agent contribution guidance
+
+Automated coding agents working in this repository must follow the same standards as human contributors.
+
+## Scope and safety
+
+- Prefer small, reviewable changes with tests or a documented validation step.
+- Do not add credentials, tokens, personal data, private URLs, local paths, or generated databases to commits.
+- Treat model outputs, financial calculations, compliance assessments, and route recommendations as advisory. Do not remove human review or approval controls.
+- Do not claim that mock data is live, verified, or production-ready.
+
+## Required checks
+
+Run the checks that cover your change before proposing it:
+
+```bash
+python -m compileall -q backend
+cd frontend && pnpm build
+```
+
+Update `README.md` and the relevant documentation whenever setup, configuration, data assumptions, or user-visible behaviour changes.

CHANGELOG.md

@@ -0,0 +1,21 @@
+# Changelog
+
+All notable changes to Globot will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project aims to follow [Semantic Versioning](https://semver.org/).
+
+## [Unreleased]
+
+### Added
+
+- MIT `LICENSE` and community health files (Contributing, Security, Code of Conduct, Governance, Support).
+- CI workflow (backend syntax + frontend production build) and Dependabot updates.
+- Maintainer-oriented OpenAI/Codex plan and public roadmap under `docs/`.
+- Backend / frontend `.env.example` files with safe defaults.
+- Typed decision-record schemas for human-reviewed recommendations.
+
+### Changed
+
+- Rewrote the README as an OSS decision-support project (badges, architecture, clear mock-data boundaries).
+- Removed personal administrator defaults; debug mode is off by default.
+- Frontend package renamed to `globot-frontend`; Docker base image aligned to Python 3.11.

CODE_OF_CONDUCT.md

@@ -0,0 +1,23 @@
+# Contributor Covenant Code of Conduct
+
+## Our pledge
+
+We pledge to make participation in the Globot community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+## Our standards
+
+Examples of behaviour that contributes to a positive environment include:
+
+- demonstrating empathy and kindness toward other people;
+- respecting differing opinions, viewpoints, and experiences;
+- giving and gracefully accepting constructive feedback;
+- accepting responsibility and apologising to those affected by mistakes; and
+- focusing on what is best for the overall community.
+
+Examples of unacceptable behaviour include harassment, sexualised language or imagery, personal or political attacks, public or private harassment, publishing others' private information without permission, and other conduct that could reasonably be considered inappropriate in a professional setting.
+
+## Enforcement
+
+Community leaders are responsible for clarifying and enforcing these standards. Reports may be made privately through the repository owner's GitHub profile. All complaints will be reviewed and investigated promptly and fairly. Leaders may remove, edit, or reject comments, commits, code, issues, and other contributions that are not aligned with this Code of Conduct.
+
+This Code of Conduct is adapted from the [Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).

CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# Contributing to Globot
+
+Thanks for helping improve Globot. Contributions are welcome in code, documentation, tests, demo scenarios, and design review.
+
+## Before you begin
+
+1. Search existing issues and pull requests to avoid duplicate work.
+2. For a material change, open an issue first and describe the user problem, proposed approach, and validation plan.
+3. Do not include credentials, personal data, confidential shipping records, or licensed data that cannot be redistributed.
+
+## Development workflow
+
+1. Fork the repository and create a focused branch from `main`.
+2. Keep the change small and explain the behaviour it changes.
+3. Update relevant documentation and examples in the same pull request.
+4. Run the checks below before requesting review:
+
+   ```bash
+   python -m compileall -q backend
+   cd frontend && pnpm build
+   ```
+
+5. In the pull request, state the motivation, how you tested it, and any follow-up work.
+
+## Pull-request expectations
+
+- Use clear, descriptive commit and pull-request titles.
+- Include tests when changing behaviour; explain why when tests are not practical.
+- Keep generated files, local databases, uploads, and secrets out of commits.
+- Preserve the human-review boundary for recommendations that could affect logistics, compliance, or financial decisions.
+- Be patient and respectful during review. Maintainers may request revisions, defer work, or close changes that do not fit the roadmap.
+
+## Reporting bugs and proposing features
+
+Use the GitHub issue templates. A good report includes reproduction steps, expected and actual behaviour, environment details, and a minimal example where possible. Please do not use public issues for security vulnerabilities; follow [SECURITY.md](SECURITY.md) instead.
+
+By contributing, you agree to follow the [Code of Conduct](CODE_OF_CONDUCT.md).

GOVERNANCE.md

@@ -0,0 +1,21 @@
+# Governance
+
+## Maintainer
+
+The repository owner, **Vector897**, is the primary maintainer and is accountable for roadmap decisions, review, releases, security coordination, and community health.
+
+## How decisions are made
+
+Issues and pull requests are the public record for project decisions. The maintainer welcomes proposals and will prioritise work that improves reproducibility, security, documentation, test coverage, accessibility, and the project's decision-support mission.
+
+For a substantive change, the maintainer may ask for an issue, design note, tests, or a staged implementation. Decisions aim for consensus when possible; if consensus is not reached, the primary maintainer makes the final call and records the rationale in the relevant discussion or pull request.
+
+## Maintainer responsibilities
+
+- triage issues and review pull requests;
+- keep the default branch and release notes understandable;
+- protect contributors and reporters handling security issues;
+- enforce the [Code of Conduct](CODE_OF_CONDUCT.md); and
+- avoid merging features that bypass human review for consequential recommendations.
+
+Contributors who demonstrate sustained, constructive maintenance work may be invited to take on additional review responsibilities.

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Vector897
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.