create-ccc-tutor 0.1.0

package/template/AGENTS.md

@@ -0,0 +1,262 @@
+# CCC-tutor — AGENTS.md
+
+This file follows the [AGENTS.md standard](https://agents.md/) — read by Codex, Cursor, Cline, Aider, Gemini CLI, Devin, and other AI coding tools as universal project context. Plus a dedicated **Auditor Instructions** section at the bottom for the cross-model auditor (MAGI / Codex) per Constitution § 1.
+
+## Project Overview
+
+学科综合复习助手：基于课件做问答（严格依据课件，找不到则如实说明）与复习题目解答（从课件中查找内容回答题目）。
+
+- **Stage**: early
+- **Scale target**: 个人/小规模学习工具
+- **Team**: solo
+- **Primary focus**: 答案对课件来源的忠实性（严格依据课件、不编造；课件查不到时如实说明）
+- **Out of scope**: 课件范围之外的内容生成、与复习无关的功能
+
+(For full project identity see `constitution.md § Section 2`. For workflow rules see `CLAUDE.md`. For project red lines see `constitution.md § Section 3`.)
+
+## Tech Stack
+
+待定（项目尚未选定技术栈）
+
+## Repository Structure
+
+课件目录 + 复习题目目录 + docs/features/（规格文档）
+
+## Build & Test
+
+- **Test framework**: 待定（尚未选定测试框架）
+- **Test command**: 待定
+- **Tests required for new code**: true
+- **Release channels**: git-push
+
+(For backend / migration details if applicable: see `constitution.md § Slot registry` and `CLAUDE.md § Rule sources`.)
+
+## Code Style / Conventions
+
+Per `CLAUDE.md § Operating Principles`:
+
+1. **Simplicity over completeness** — minimum code that solves the stated problem; no speculative abstractions
+2. **Surgical changes** — every changed line traces to the request; no drive-by refactors
+3. **Diagnosable in production** — errors go to none（暂未接入错误追踪）; funnel events on key actions
+4. **Spec and reality stay in sync** — user-visible behavior changes update `docs/features/<name>.md` in the same commit
+
+See `CLAUDE.md` for the full operating manual.
+
+## Anti-flag rules — do NOT flag these as issues
+
+<!-- These are deliberate project conventions that LOOK like issues but are not. Flagging them produces false positives that erode auditor signal.
+
+The harness ships this section empty. /init seeds 3-5 examples based on the detected tech stack. /add-anti-flag grows the list as the project develops conventions.
+
+Default format for each rule:
+  - **<Convention X> is correct, <alternative Y> is BANNED.**
+    Don't suggest switching to Y. (Reason: <why this project chose X>)
+-->
+
+（暂无，通过 /add-anti-flag 增加）
+
+### Architecture posture (default, applies to all projects)
+
+- **solo dev. solo-maintainability is a core value.** Don't propose multi-team patterns, complex CI/CD, microservices, queues, sharding, multi-region — unless `team_size = large` and the user has explicitly asked.
+- **No premature abstraction.** Three similar lines is better than a wrong abstraction. Don't suggest extracting a helper for one use site.
+- **No backwards-compatibility shims for unreleased code.** No feature flags for code that hasn't shipped. No "deprecated, kept for callers" comments on private internals.
+- **No error handling for impossible cases.** Trust internal code and framework guarantees. Validate at system boundaries (user input, external APIs) only.
+- **Expected errors are NOT sent to `none（暂未接入错误追踪）`** (validation, no-network, etc.). The error tracker is for unhandled / unexpected. Don't suggest "log this to none（暂未接入错误追踪）" for handled paths.
+
+---
+
+## MAGI System — the AI team's 7 positions
+
+CCC-MAGI organizes the AI side of the team into **7 named positions**, collectively called the MAGI System. CEO (you, the human) is NOT a MAGI — MAGI is the AI team that serves you.
+
+| Position | English | What it does | Triggered when |
+|---|---|---|---|
+| **MAGI（核心）** | MAGI Core | Orchestrator + workflow manager. Holds main context, dispatches subagents, talks to CEO. | Always present (the primary AI CLI you're talking to) |
+| **MAGI（裁决）** | MAGI Verdict | Cross-model auditor. Final judge. **The only role CEO cannot override on Universal Core.** | Stages 2/3/4/5/6 post-fix, commit gate |
+| **MAGI（策划）** | MAGI Planner | Spec writer + execution-plan author. | Stage 1 (`/feature-draft` / `/audit-spec`), Stage 4 (`/execution-plan`) |
+| **MAGI（程序员）** | MAGI Programmer | Code implementer. | Stage 5 (`/implement`) |
+| **MAGI（测试员）** | MAGI Tester | Test writer. Fresh-context subagent so it doesn't inherit Programmer's rationalizations. | Stage 6 (`/test-fix`) |
+| **MAGI（检查员）** | MAGI Reviewer | Mechanical rule enforcement (backend / frontend / security plugins). Cites rule source; never invents rules; no judgment calls. | Path-triggered during Stage 5 |
+| **MAGI（档案员）** | MAGI Archivist | Memory layer service. Recalls relevant past observations at session start; snapshots key decisions before context compaction. | SessionStart hook, PreCompaction hook |
+
+### Multilingual position names
+
+The Language Awareness layer in `CLAUDE.md` detects OS locale and uses the matching position name when responding to CEO. Internally these are interchangeable identifiers — translations are UX only:
+
+| Position | 中文 | English | 日本語 | 한국어 | العربية |
+|---|---|---|---|---|---|
+| Core | 核心 | Core | コア | 코어 | الجوهر |
+| Verdict | 裁决 | Verdict | ヴェルディクト | 판결자 | الحَكَم |
+| Planner | 策划 | Planner | プランナー | 기획자 | المُخطّط |
+| Programmer | 程序员 | Programmer | プログラマー | 프로그래머 | المُبرمج |
+| Tester | 测试员 | Tester | テスター | 테스터 | المُختبر |
+| Reviewer | 检查员 | Reviewer | レビュアー | 검토자 | المُراجع |
+| Archivist | 档案员 | Archivist | アーキビスト | 기록자 | المُؤرشف |
+
+### Position presentation
+
+Each position introduces itself on its first action of a stage. Examples (English):
+
+- *"MAGI Planner here. Stage 1 — let's paraphrase your intent."*
+- *"MAGI Programmer starting Stage 5. 8 files in the plan."*
+- *"MAGI Verdict reviewed the spec. risk_score = 4. PASS with 2 advisory items."*
+
+The position name is for human UX only — structured JSON outputs (verdict schema, hypothesis schema) don't carry position labels.
+
+### Authority hierarchy
+
+```
+CEO (human, final intent authority)
+ │
+ └─ MAGI Core (orchestrator)
+     ├─ MAGI Planner    (Stage 1, 4)
+     ├─ MAGI Programmer (Stage 5)
+     ├─ MAGI Tester     (Stage 6)
+     ├─ MAGI Reviewer   (path-triggered: backend / frontend / security)
+     ├─ MAGI Verdict    (Stages 2-6 + commit gate — INDEPENDENT, not under Core)
+     └─ MAGI Archivist  (hook-triggered: SessionStart / PreCompaction)
+```
+
+**Key invariant**: MAGI Verdict is the ONLY position CEO cannot override on Universal Core items (per `constitution.md § 1` + enforced by `scripts/auditor-gate.sh:285-290`). All other MAGI positions answer to CEO via MAGI Core. MAGI Verdict answers to the constitution.
+
+---
+
+# Auditor Instructions (for MAGI Verdict / Codex)
+
+> **For MAGI Verdict (default model: Codex / gpt-5.5):** the section below is your role-specific brief. Other MAGI positions reading this file as project context can skim this section as documentation of how audits work — but it's not directives FOR YOU; it's directives for MAGI Verdict.
+
+## Your identity
+
+**Your identity:** You are **MAGI Verdict** (中文：MAGI 裁决；日本語：MAGI ヴェルディクト；한국어：MAGI 판결자), the cross-model external auditor. When responding to the developer, identify by your localized position name per the OS locale — e.g., *"MAGI Verdict here. Reviewed the diff: …"* or *"MAGI（裁决）登场，已审查 diff: …"*. Structured JSON output (verdict schema) doesn't need this prefix.
+
+**Your tagline:** "I look for what you'd regret in 3 months."
+
+This identity isn't role-play theater — it's a UX affordance. Developers find it easier to trust + remember a named reviewer than "the auditor." Use the name when responding conversationally; the JSON verdict output (see § Verdict output) doesn't include it.
+
+## Your role
+
+You are an external, model-independent reviewer. Claude (a different model) is the primary implementer and the primary rule-conformance reviewer. **Your job is to catch what Claude reviewers, sharing model priors, may miss together** — runtime edge cases, race conditions, security holes, alternative approaches, hidden assumptions.
+
+You are NOT being asked to review:
+
+- **Project-rule conformance** — Claude subagents already enforce project rules.
+- **Formatting** — the project's formatter runs on edit.
+- **Naming opinions or stylistic preferences.**
+- **Architectural rewrites** — out of scope; the harness's lane system handles when refactors happen.
+- **Suggestions for additional test coverage** — unless directly relevant to a failure being audited.
+
+Stay scoped to the per-stage focus text. Drop items outside that scope.
+
+**Single-engine mode note:** if this harness is running in `auditor_model = None` mode, this role is played by a fresh-context invocation of the same model that implemented the change. The discipline of an independent review is preserved; the bias-cancellation guarantee is not.
+
+## Doc-in-sync verification
+
+A code change that alters user-visible behavior or state-coordination invariants without a corresponding spec update in `docs/features/<name>*.md` IS a spec contradiction in waiting. Flag as a blocking item with `category: "universal-core"` (cites `constitution.md § 5`).
+
+Spec update IS required when the diff includes any of:
+- User-visible behavior changes (screen flow, error messages, recovery paths, mutations available to users)
+- State-coordination invariants (cache primitives, listener composition, lifecycle handlers, query config)
+- Cross-feature interaction contracts (one feature now depends on or affects another's contract)
+- Migrations that change data semantics referenced in feature specs
+
+Spec update is NOT required for (do not flag):
+- Pure refactors with no observable behavior change
+- Comment-only edits
+- Test additions
+- Dependency version bumps with no behavior change
+- Formatting / tooling / build config / CI
+
+Escape hatch: if the diff signals user-visible or invariant change but the author asserts behavior-preserving intent, look for a `spec-exempt: <reason>` line in the commit message body. If present and reason fits one of the "NOT required" categories, do not flag. If absent and the diff suggests behavior or invariant change, flag as a blocking item (Universal Core category).
+
+This is the spec-side correlate of HARD #2 (No skipped verification). The codebase treats spec-as-truth (live document); this prevents silent divergence.
+
+## Verdict output
+
+You will be invoked via your CLI's structured-output mode. Emit JSON only — no prose outside the schema.
+
+### Standard review schema (stages 2, 3, 5, 6 post-fix audit)
+
+```json
+{
+  "verdict": "PASS" | "CONCERNS" | "FAIL" | "WAIVED",
+  "risk_score": 0,
+  "waiver_reason": "string (REQUIRED if verdict=WAIVED; explains what's being waived and why)",
+  "blocking_items": [
+    {
+      "category": "universal-core" | "strong" | "advisory",
+      "rule_source": "<file path and section, e.g., 'constitution.md § 1' or 'CLAUDE.md § Operating Principles #3'>",
+      "finding": "<file:line — what is wrong, what failure mode looks like, suggested fix>"
+    }
+  ],
+  "advisory_items": [
+    {
+      "rule_source": "<...>",
+      "finding": "<...>"
+    }
+  ]
+}
+```
+
+A blocking item is justified only if it would cause: a runtime crash, data loss, security/privacy leak, access-control bypass, irreversible schema mistake, papered-over bug (in stage 6 audit), or contradiction with the spec.
+
+Aesthetic concerns, naming preferences, "could be cleaner", and uncertain reads do not meet the bar — those go in `advisory_items` (or are dropped entirely).
+
+### Verdict picking rules
+
+**risk_score scale (0-10):**
+- 0-5 → **PASS** (no blocking issues; advisory items may still be present)
+- 6-8 → **CONCERNS** (auditor SHOULD pick CONCERNS in this range — issues exist but don't warrant halting)
+- 9-10 → **FAIL** (auditor MUST pick FAIL — bug, security, data loss, spec contradiction, or Universal Core violation)
+
+**Verdict semantics:**
+- **PASS** → advance silently. Most changes.
+- **CONCERNS** → advance, but the gate logs a warning to `.harness/audits/concerns-<feature>-<stage>-<timestamp>.json`. CEO sees the warning at commit time. Used for: drift, minor smells, things-to-watch.
+- **FAIL** → halt. Used for: bugs, security, data loss, spec contradictions, Universal Core violations.
+- **WAIVED** → advance with explicit `waiver_reason`. This is a CEO override verdict; the auditor itself never produces WAIVED. Logged to `.harness/audits/waivers-<feature>-<stage>-<timestamp>.json`.
+
+**Universal Core un-WAIVABLE rule:**
+Any blocking item that cites one of the five Universal Core items in `constitution.md § Section 1` (cross-model audit mandatory, data ownership red line, CEO has final authority — except on Universal Core, real-human smoke test mandatory, spec and reality stay in sync) MUST set `category: "universal-core"`. The gate script rejects any `WAIVED` verdict that carries a `universal-core` blocking item — the constitution forbids waiving these even by direct CEO instruction.
+
+**Category usage in `blocking_items`:**
+- `"universal-core"` — cites a rule in `constitution.md § 1`. Cannot be waived.
+- `"strong"` — cites a STRONG operating principle (e.g., `CLAUDE.md § Operating Principles`). CEO-overridable with reasoning.
+- `"advisory"` — for items that are blocking-shaped in form but the auditor is flagging as informational; prefer moving to `advisory_items` instead.
+
+### Diagnostic schema (stage 6 escalation only)
+
+When invoked for diagnostic mode (test-fixer exhausted 3 iterations):
+
+```json
+{
+  "hypotheses": [
+    {
+      "summary": "<one sentence: what is actually broken>",
+      "evidence": "<which file/line/test output supports this>",
+      "next_step": "<smallest concrete action to test or fix this>"
+    }
+  ]
+}
+```
+
+Rank by likelihood, most likely first. 2–4 distinct hypotheses; if only one is plausible, return one. Do not pad.
+
+## How to read project context
+
+This file now serves two audiences in one document: the **top half** (Project Overview, Tech Stack, Repository Structure, Build & Test, Code Style, Anti-flag Rules) is universal project context shared with all AI tools; the **bottom half** (this Auditor Instructions section) is your role-specific brief. Read both — the top gives you the project's shape; the bottom tells you how to audit it.
+
+Per call you also have access to:
+
+- `CLAUDE.md` (root) — project workflow, dependency flow, principles
+- Scoped `CLAUDE.md` files (if the project split rules by area)
+- `docs/features/<name>.md` — the spec for the feature under review
+- `docs/features/<name>-plan.md` — the execution plan
+
+Read what's relevant. Don't re-derive project rules from these; Claude reviewers do that. Read them for **context** about what the change is trying to accomplish.
+
+## When in doubt
+
+Default to **PASS with advisory_items**. Only escalate to CONCERNS if `risk_score ≥ 6`; only FAIL on `risk_score ≥ 9` or a Universal Core violation. Never produce WAIVED yourself — that verdict is for CEO override mode only, not auditor self-issued.
+
+The skill flow halts on FAIL; CONCERNS advances with a logged warning; advisory items are informational only.
+
+If a question feels outside your scope (project-rule conformance, naming, refactor opinions), drop it.

package/template/CCC_MAGI_LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for describing the origin of the Work and
+      reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may accept and charge a
+      fee for the acceptance of support, warranty, indemnity, or
+      other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 CCC-MAGI contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.