tianluo 12.0.0__tar.gz

tianluo-12.0.0/.gitignore

@@ -0,0 +1,86 @@
+# =====================================================================
+# Repository root: ignore everything by default.
+# Stray files dropped at the root (test logs, scratch output, etc.) must
+# NOT be accidentally committed. Only the project files/dirs explicitly
+# un-ignored below are tracked. To track a new top-level entry, add an
+# explicit `!/<name>` (files) or `!/<name>/` (dirs) line here.
+# =====================================================================
+/*
+!/.gitignore
+!/.claude/
+!/LICENSE
+!/NOTICE
+!/README.md
+!/README.zh.md
+!/VERSIONS.md
+!/progress.md
+!/pyproject.toml
+!/tianluo.example.yaml
+!/docs/
+!/scripts/
+!/se3/
+!/tianluo/
+!/src/
+!/tests/
+
+# --- Global ignore patterns (apply at any depth) ---
+node_modules/
+.DS_Store
+*.swp
+*.swo
+__pycache__/
+*.pyc
+.pytest_cache/
+.worktrees/
+.collab/
+*.egg-info/
+human-calls/
+issues.md
+prompts/
+# But the built-in preset prompts shipped as package data MUST be tracked
+# (the broad `prompts/` rule above would otherwise swallow them, so the
+# root-cause doc-sync fix could never be committed/shipped).
+!/src/tianluo/templates/prompts/
+e2e
+materials
+
+# tianluo runtime dir (post-rename layout): ignore runtime content,
+# whitelist committed artifacts. Mirrors the legacy /se3/* block below so
+# `luo migrate run rename-to-tianluo` on this repo needs no gitignore edit.
+/tianluo/*
+!/tianluo/code-index.md
+!/tianluo/charter.md
+!/tianluo/issues/
+!/tianluo/scripts/
+!/tianluo/prompts/
+!/tianluo/version-rules.md
+!/tianluo/version-intents/
+
+# SE3: ignore runtime content, whitelist committed artifacts (legacy layout)
+/se3/*
+!/se3/code-index.md
+!/se3/charter.md
+!/se3/issues/
+!/se3/scripts/
+!/se3/prompts/
+!/se3/version-rules.md
+# Version-reconcile intent metadata: written by a worktree session's commit
+# step and committed on the flow branch so the merge-side reconcile step can
+# read every merged-in branch's intent from master. Must be tracked, unlike
+# the rest of se3/state runtime content that /se3/* ignores.
+!/se3/version-intents/
+tmp*.prompt
+
+# SE3 session file
+.claude/.session.json
+
+# tianluo local/live project config (not checked in; tianluo.example.yaml
+# is the shipped reference). Legacy se3.* names honoured through 12.x.
+tianluo.local.yaml
+se3.local.yaml
+src/tianluo/__pycache__/
+*.egg-info/
+
+# Userspace-installed system libraries for the headless-browser acceptance
+# test (populated by scripts/install_browser_test_libs.sh on no-root hosts).
+.browser-libs/

tianluo-12.0.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 reasonable and customary use in 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 choose to offer,
+      and charge a fee for, 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 Zhendong Zhang (CRE)
+
+   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.

tianluo-12.0.0/NOTICE

@@ -0,0 +1,4 @@
+tianluo (formerly SE3)
+Copyright 2026 Zhendong Zhang (CRE)
+
+This product includes software developed by Zhendong Zhang.

tianluo-12.0.0/PKG-INFO

@@ -0,0 +1,349 @@
+Metadata-Version: 2.4
+Name: tianluo
+Version: 12.0.0
+Summary: tianluo (田螺) - autonomous SE 3.0 flow engine: prompt once, walk away, come back to a finished deliverable
+Project-URL: Homepage, https://github.com/CoREse/tianluo
+Project-URL: Repository, https://github.com/CoREse/tianluo
+Project-URL: Changelog, https://github.com/CoREse/tianluo/blob/master/VERSIONS.md
+Project-URL: Issues, https://github.com/CoREse/tianluo/issues
+Author-email: "Zhendong Zhang (CRE)" <zzdzhangzzd@hotmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: agent,ai,autonomous,claude,developer-tools,flow-engine,llm,software-engineering
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Build Tools
+Requires-Python: >=3.8
+Requires-Dist: pexpect>=4.8.0
+Requires-Dist: prompt-toolkit>=3.0.0
+Requires-Dist: psutil>=5.9.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: rich>=13.0.0
+Requires-Dist: typer>=0.9.0
+Provides-Extra: browser
+Requires-Dist: playwright>=1.40.0; extra == 'browser'
+Provides-Extra: server
+Requires-Dist: argon2-cffi>=21.3.0; extra == 'server'
+Requires-Dist: fastapi>=0.110.0; extra == 'server'
+Requires-Dist: uvicorn>=0.29.0; extra == 'server'
+Requires-Dist: websockets>=12.0; extra == 'server'
+Description-Content-Type: text/markdown
+
+<p align="center"><img src="https://raw.githubusercontent.com/CoREse/tianluo/master/docs/assets/tianluo-icon.png" width="128" alt="tianluo icon"></p>
+
+# tianluo (田螺) — the Software Engineering 3.0 flow engine
+
+![Version](https://img.shields.io/badge/version-12.0.0-blue)
+![Python](https://img.shields.io/badge/python-3.8+-green)
+![License](https://img.shields.io/badge/license-Apache--2.0-lightgrey)
+
+**English** | [中文](README.zh.md)
+
+> **A project-level, cross-session flow framework where the program — not the human — supervises the AI agent. You prompt once, walk away, and come back to a finished deliverable.**
+
+*tianluo is named after the Snail Girl (田螺姑娘) of Chinese folklore: a farmer comes home each day to find the housework quietly finished — the spirit did the work while he was away, never asking, never interrupting. That is this tool's contract. You call it by its short name: the command is `luo`.*
+
+tianluo (formerly published as *se3*; the methodology is still called **SE 3.0**) is not a single-session prompting tool, a skill, a subagent, or a dynamic workflow. Those are *in-session* aids that augment one human-in-the-loop turn. tianluo sits one layer above: it is a CLI engine + persistent state machine + a code-first knowledge system (code-index + charter + why-comments) that supervises an AI coding agent across many sessions, on many machines, until the work is actually done.
+
+---
+
+## Design Philosophy
+
+### 1. A different paradigm: program-as-supervisor, human out-of-the-loop
+
+Skills, subagents, and dynamic workflows make a *single AI turn* smarter or more parallel. They are valuable, but they assume a human is present, reading output and steering after every step.
+
+tianluo makes a different bet. The unit of work is not a turn; it is a **project task**. Between `luo run "…"` and the final commit there may be dozens of LLM calls across plan / implement / test / self-check / invariant-check / commit steps, multiple agent rotations, fix loops, and even multi-machine collaboration via the daemon and central server. The supervisor of all this is the tianluo engine — Python code running a deterministic state machine — not a person watching a terminal.
+
+| Tool class | Scope | Who supervises | Where state lives |
+|------------|-------|----------------|-------------------|
+| Skills / subagents / dynamic workflows | One session, one turn (or a fan-out within one turn) | Human in the loop, reading output | Conversation context |
+| **tianluo** | A project task spanning many sessions / machines | The program (engine + daemon) | Persistent files (`tianluo/state/`, `tianluo/history/`, `tianluo/issues/`) |
+
+### 2. The real pain: attention is all you need
+
+LLMs are not the bottleneck. *Human attention* is. The cost of any agentic system is measured in how often it forces a person to read, judge, and decide. tianluo's north star is **save human attention**.
+
+The ideal tianluo session looks like this:
+
+1. **Prompt** — you type `luo run "…"` (or open a discovery session).
+2. **Discover** — the engine asks a few targeted clarifying questions until requirements converge.
+3. **Fire-and-forget** — you walk away. The engine plans, implements, tests, self-checks, checks the diff against recorded invariants, flags any charter drift, bumps the version, and commits.
+4. **Pick up the deliverable** — you come back to a clean commit on a branch, with the version, history, and code-index already aligned.
+
+Steps 1 and 2 are the only places where human attention is genuinely required. Everything else is the program's job.
+
+### 3. The four moats that make this paradigm work
+
+A program-as-supervisor paradigm only holds up if the framework provides four things that in-session tools cannot:
+
+- **Cross-session state machine** — `tianluo/state/engine.json` persists the exact step, attempt, context, and fix-loop history of every flow. `luo daemon` keeps a resident process supervising local `luo run` flows; `tianluo-server` aggregates many daemons into one web view; `luo run --loop` chains tasks autonomously on isolated git worktrees. The flow survives terminal exits, machine restarts, and hand-offs between machines. *Why this paradigm needs it:* without durable state, "walking away" loses the work.
+- **A code-first knowledge system (code-index + charter + why-comments)** — the source of truth is the code itself. A `tianluo/code-index.md` structure map (auto-maintained, self-freshening) gives the agent an orientation map of *what modules and symbols exist and where*; a small hand-maintained `tianluo/charter.md` carries only the high-altitude facts every step needs in full (project identity, top-level architecture, project-wide invariants); colocated why-comments carry intent the code cannot express. *Why this paradigm needs it:* a long-running unattended agent needs to orient itself in the codebase cheaply on every step without a curated mirror of the code rotting beside it. See [The knowledge system](#the-knowledge-system-code-index--charter--why-comments) below for why this beats the spec-mirror it replaces.
+- **Failure recovery built in** — `luo salvage` rescues a crashed session by committing dangling changes, filing follow-up issues, and archiving the state. The test-baseline cache distinguishes a new regression from a pre-existing red test. Issue discovery promotes any unresolved concern into a tracked `tianluo/issues/` record. *Why this paradigm needs it:* when no human is watching, the framework must catch its own failures rather than leak them.
+- **Portable substrate** — the engine is pure Python over the file system. The LLM call layer is a thin `AgentRunner` adapter; today's concrete runner is the Claude Code CLI, but the abstraction (`AgentRunner` / `RunResult` / `InfraErrorType`) is provider-neutral. *Why this paradigm needs it:* a paradigm bet should not be a single-vendor bet.
+
+### luo vs Claude Code Dynamic Workflows (complementary, not competing)
+
+Dynamic Workflows solve *in-session* parallelism: deterministic fan-out, judge panels, pipelines, all inside one orchestrating conversation. They make a single turn comprehensive and confident.
+
+tianluo solves *cross-session* project governance: persistent state, a code-first knowledge system, failure recovery, and a portable substrate that outlives any single conversation.
+
+The two compose. A future tianluo step can delegate its in-step parallel work to a Dynamic Workflow without changing tianluo's outer state machine. We deliberately do not pin to specific DW API names here, because DW is still in research preview and its surface will evolve.
+
+---
+
+## The knowledge system: code-index + charter + why-comments
+
+Earlier tianluo versions kept a parallel corpus of `tianluo/specs/**/spec.md` files — a curated prose mirror of the code — plus an entire governance machine to keep it from drifting: `luo sync` rounds, per-requirement drift baselines, `verify_spec` / `update_spec` / `spec_gate` flow steps, and the whole `sync_*` analyzer/loop/state/discovery stack. tianluo replaced that mirror with three colocated artifacts whose source of truth is the code itself.
+
+### The three pieces
+
+- **code-index** — a *structure map* of the project. Its structure comes deterministically from the code (a filesystem walk + Python AST symbol enumeration: directory/package → file/module → class → function/method); a one-line LLM summary, synthesized bottom-up (a directory's summary from its files', a file's from its symbols'), is attached to each level. It lands as **one self-sufficient file**, `tianluo/code-index.md` — the **authoritative product, committed to git**. It *is* the map, and it is what `luo code-index` renders and what gets injected into every flow step. Because it is plain text in a diff, a wrong summary can be spotted by a human reviewer and corrected, and the correction lands durably. Each node line also carries an embedded content fingerprint (a terse, render-invisible HTML comment), so the committed md *alone* decides what changed: on rebuild only fingerprint-changed nodes are re-summarized by the LLM, unchanged nodes reuse their existing summary (so human corrections survive), and the md is flushed periodically during a build so a crash resumes from where it stopped. There is no separate cache file — structure, summaries, and fingerprints all live in the one committed, human-diffable file.
+
+  The structure comes from the **code**, not the json; the json is just a rebuild accelerator. Display reads only the `.md`. The optimization goal is **structural coverage, not summary depth** — the map answers *which modules/symbols exist and where*, and deliberately does not descend into implementation detail (that is the source code's job; copying it into the index would just reproduce a worse-than-code mirror).
+
+- **charter** — `tianluo/charter.md`, the slimmed, renamed successor of the old base spec. It is injected, in full, into every step, and doubles as the conventions channel for sandboxed sub-processes (which cannot read `CLAUDE.md`). An *altitude gate* admits only what is **un-sayable in code and needed in full by the whole project**: project identity, top-level architecture, and project-wide cross-cutting invariants. The per-module locator index that used to bloat the base spec is gone — that job belongs to code-index. A byte threshold is a monitoring light, not a hard wall: because charter content is decoupled from project size (it grows with architectural complexity, not LOC), full-loading it stays cheap even on large projects; if it ever grows hard to load in full, that is a red flag that low-altitude content leaked in — not a reason to build an index over the charter.
+
+- **why-comments** — colocated comments that carry *only* the why/intent that code cannot express, updated only when the why changes. They are not a source for code-index, so there is no per-change synchronization tax; the implement step's prompt simply asks the agent to update the colocated why-comment when a change's intent changes. This is honestly a prompt-level soft convention (same strength as the other conventions), pressing the comment-discipline surface to its minimum rather than eliminating it.
+
+### What actually got better (an honest accounting)
+
+This refactor does **not** make code descriptions more semantically correct: an LLM-generated summary can be wrong in exactly the same way a hand-written spec was. The real gains are elsewhere:
+
+- **Source of truth returns to the code.** Navigation and intent live next to the code, not in a separate corpus that has to be kept honest.
+- **Staleness is eliminated.** code-index regenerates incrementally with zero discipline required: a deterministic enumerator re-walks the tree every build, so a newly added symbol is enumerated, a deleted one is pruned, and only fingerprint-changed symbols are re-summarized. Completeness is a *property of the enumerator*, not of LLM diligence — the LLM only summarizes the symbols it is handed and never decides who is included, so it cannot omit a symbol, and a mis-summarized line still appears on the map.
+- **The governance maintenance surface collapses.** The entire `sync_*` stack, `verify_spec`, `update_spec`, `spec_gate`, the per-requirement drift baselines, and the old `spec_check` all retire. What remains is two cheap, anchored checks: `INVARIANT_CHECK` (does the diff violate any *already-recorded* binding invariant — anchored to {task description, charter, the touched code's why-comments}?) and `CHARTER_FRESHNESS` (an advisory that flags only when the diff plausibly touches one of charter's content classes, and otherwise passes for free).
+- **Granularity and admission become explicit knobs.** code-index granularity bottoms out at each file's smallest *natural* semantic unit (code → function/method; structured non-code → its natural unit; opaque files → one file-level line), with line/byte chunking only as a last-resort degrade mode gated behind three simultaneous conditions; the four thresholds are exposed in `tianluo.yaml` (`spec_governance:`). Charter content is gated by an admission standard you can read and enforce. Both are dials you turn, not emergent behavior you fight.
+- **Charter volume is decoupled from project scale.** It grows with architecture, not lines of code.
+- **The failure floor is higher than the old system's.** Even if every soft discipline lapses, the one automatically-maintained artifact — code-index — stays self-fresh. The system's worst case is therefore strictly better than the old system's worst case of *a rotting spec corpus + grep*.
+
+### A concrete before/after — and why spec-index could never win this
+
+Take the old `spec_index.py` (~1130 lines — itself retired by this very refactor) as a worked example. Suppose you need to answer a *navigation* question about it: where is it, what does it do, what are its key symbols?
+
+Without a code-index, you have to read the whole ~1130-line file into context to answer even that. With a code-index, you first read the few map lines about that file — for instance, *"builds an item-level spec index, incremental invalidation via mtime + size + sha256; key symbols `load_or_build` / `_make_summary` / `_extract_locator` / `_h4_dividers`."* Navigation questions never touch the source. And a *precise* question — say, the exact boundary condition of one heuristic — needs only a pinpoint read of those ~30 lines, not the whole file.
+
+**The comparison with spec-index is the sharpest point.** A spec / spec-index has an upside that is *fundamentally capped by living one layer above the code*: even assuming a spec were perfectly accurate and perfectly complete, it still sits at spec altitude and cannot surface the actual code-level detail — so after it locates the file for you, you still have to go back and read the code, and to be thorough you have to read all of it. The spec's likely inaccuracy and incompleteness is merely insult on top of that injury; it is **not** the reason it loses to code-index. code-index is not subject to this cap at the root, because its source of truth *is* the code and it walks you straight to those ~30 lines.
+
+This is exactly the **coverage > depth** bet cashing out: the map's job is to tell you which ~30 lines to flip to — not to replace those ~30 lines. And that context saving is not a one-time win: it compounds on **every step of every flow**, which is precisely the cost code-index exists to cut.
+
+> Historical decisions and retained-but-removed intent (e.g. a feature pulled out while its intent is kept on record) do not enter the charter; they continue through the issue channel (`luo issue`). Cross-file architectural decisions with no single owner enter the charter, hand-maintained, accepting that they cannot be auto-synced.
+
+---
+
+## Installation
+
+```bash
+# Core CLI (Python 3.8+)
+pip install tianluo
+
+# With the central server / web console
+pip install 'tianluo[server]'
+
+# With the headless-browser acceptance test (needs `playwright install chromium` afterwards)
+pip install 'tianluo[browser]'
+```
+
+Current version: **12.0.0**. The installed console scripts:
+
+| Script | Purpose |
+|--------|---------|
+| `luo` | **The** command. Short for tianluo — you write `tianluo` down, you call `luo` to work. |
+| `tianluo` | Full-name entry, identical to `luo` (docs, demos, discoverability) |
+| `se3` | Transitional alias from the rename; prints a migration notice, removed in 13.0.0 |
+| `tianluo-server` | Central web server (only with the `server` extra) |
+| `se3-server` | Transitional alias for `tianluo-server`, removed in 13.0.0 |
+
+The core CLI never imports the web stack, so installing without `[server]` keeps the dependency surface minimal.
+
+> Prefer a two-letter command? `alias tl=luo` — we deliberately don't ship `tl`
+> (the Teal compiler owns it, and two competing short commands would split the
+> docs and community vocabulary).
+
+### Migrating an existing se3 project
+
+Everything keeps working unchanged through 12.x: the `se3` command, a legacy
+`se3/` runtime directory, and `se3.yaml` / `se3.local.yaml` configs are all
+still honoured. To move a project to the new layout in one reviewable,
+`git revert`-able commit:
+
+```bash
+luo migrate run rename-to-tianluo   # git mv se3/ → tianluo/, config renames, .gitignore rewrite
+```
+
+All legacy fallbacks are removed in **13.0.0**.
+
+---
+
+## Quick Start
+
+```bash
+# 1. Initialize a project (creates tianluo.yaml, tianluo/charter.md, .gitignore, git repo)
+cd your-project
+luo init
+
+# 2. Optional: explore vague requirements through multi-turn discovery first
+luo run --discover "I want a CLI tool that does X"
+
+# 3. Run a task end-to-end (analyze → plan → implement → test → self_check →
+#    invariant_check → charter_freshness → version_analyze → commit → summarize)
+luo run "Add JWT authentication"
+
+# 4. Resume an interrupted flow exactly where it stopped
+luo run --resume
+
+# 5. Navigate the codebase via the structure map
+luo code-index                          # adaptive root map: a budgeted, zoomable directory tree
+luo code-index index src/tianluo/engine     # drill one literal level (a directory's immediate children)
+luo code-index show src/tianluo/cli.py      # one file's full function/method detail
+```
+
+### Three operating modes
+
+- **`--loop`** — Run tasks back-to-back on an isolated git worktree branch
+  (`loop/<slug>-<n>`). Each iteration gets its own clean working tree; the
+  branch is auto-merged or auto-discarded when the loop ends, or preserved
+  for deferred merge if you Ctrl-C.
+- **`luo daemon start`** — Launch a resident background process that
+  supervises every local `luo run`, aggregates state under
+  `tianluo/state|logs|calls|issues`, and (optionally) dials out to a central
+  server. Lets you check on a flow from anywhere.
+- **`tianluo-server`** — A FastAPI + WebSocket central server (with a bundled
+  static web console at `/`) that merges many daemons into one multi-machine
+  view. Useful for fleets, remote launch, and watching long-running flows
+  from a browser. Defaults to `127.0.0.1:8080`.
+
+#### Web console authentication
+
+The central server is a multi-tenant control plane — the web console and REST
+API require a login, and every machine / flow is scoped to the owner that owns
+it. The first-run flow is:
+
+1. **Mint a break-glass admin token** — run `tianluo-server bootstrap-token` once;
+   it prints a one-time admin token to the console.
+2. **Log in** — open the web console and exchange the token for the break-glass
+   admin session (`POST /api/auth/breakglass`).
+3. **Create local users** — as admin, invite/create accounts (`POST /api/users`).
+   v1 has no public self-service registration.
+4. **Issue a daemon key** — each owner self-mints a daemon key in the UI
+   (`POST /api/daemon-keys`), then binds a worker with
+   `luo daemon start --daemon-key <key>`. The owner only ever sees their own
+   machines and flows.
+
+See [docs/daemon-and-server.md](docs/daemon-and-server.md#authentication--multi-tenant-access)
+for the full end-to-end auth walkthrough and configuration keys.
+
+---
+
+## Command Reference
+
+All commands found below are present in `src/tianluo/cli.py` or its registered
+sub-typers as of version 12.0.0.
+
+### Top-level commands
+
+| Command | Purpose |
+|---------|---------|
+| `luo run [TASK]` | Unified entry point. Drives the flow engine state machine (analyze → plan → implement → test → self_check → invariant_check → charter_freshness → version_analyze → commit → summarize). Supports `--resume`, `--flow-id`, `--loop`, `--max-iterations`, `--no-worktree`, `--merge`, `--list-loops`, `--discover`, `--from-issue`, `--change`, `--type`, `--preset`, `--output-format`. |
+| `luo init` | Initialize a new project: writes `tianluo.yaml`, `tianluo/charter.md`, `.gitignore`, and runs `git init` if needed. Flags: `--project-root`, `--name`, `--force`. |
+| `luo code-index` | Render the **adaptive root map** from `tianluo/code-index.md`: a byte-budgeted, zoomable directory tree (top level always shown; code directories expanded a few levels deep within the budget). This is the same map injected into every flow step. Reads the committed map (reports "not built" until you run `rebuild`); flow steps keep it fresh lazily/incrementally. |
+| `luo code-index index [PATH]` | Render exactly **one literal level** at `PATH`: a directory's immediate children (subdirs + files), or a file's functions/methods. No argument → the literal root level. Unlike the bare command, it never auto-expands. |
+| `luo code-index show <path>` | Print one file's full function/method detail (and any degraded chunks) from the structure map. |
+| `luo code-index rebuild [--force]` | Rebuild the code-index, flushing the md periodically as a checkpoint. Incremental by default (only fingerprint-changed nodes are re-summarized); `--force` re-summarizes everything. |
+| `luo code-index inspect` | Show code-index stats (file / symbol / degraded-chunk counts) from the on-disk map. |
+| `luo migrate run <id>` / `luo migrate list` | Run a registered version/format migration (`run <id>`), or list the available migrators (`list`). A reusable registry skeleton; the first migrator (`spec-to-new-system`) converts a legacy `tianluo/specs/` project to the code-index + charter + why-comments system in one reviewable, `git revert`-able change. |
+| `luo guardrails <spec-file>` | Run tianluo guardrails on a file (deleted-line / weakened-language detection); `--sizes` runs project-wide size checks. Used by `luo merge`. Flag: `--original` / `-o <baseline-file>`. |
+| `luo merge <branch> [<branch> ...]` | Sequentially merge branches into HEAD with LLM-driven conflict resolution. Flags: `--strategy fast\|safe\|strict`, `--delete-merged` / `--no-delete-merged`. Runtime data under `tianluo/` is synchronized per the tiered policy. |
+| `luo merge-respond <call-file>` | Apply a human decision file produced by `luo merge` when conflicts or guardrail violations escalated to a human MCP call. |
+| `luo salvage` | Best-effort recovery of an abnormally terminated session: tolerant state load, commit dangling diff, file follow-up issues, archive the session. Flag: `--project-root` / `-p <path>`. |
+
+### `luo history` — flow history
+
+| Subcommand | Purpose |
+|------------|---------|
+| `luo history` / `luo history list` | List flows across active state, archived state, and history-only directories. Flags: `--active-only`, `--archived-only`, `--json`. |
+| `luo history show <flow_id>` | Show structured step-by-step details. Flags: `--detailed` (LLM call breakdown), `--verbose` (full tool-call stream), `--json`. |
+| `luo history restore <flow_id>` | Resume a specific flow by ID (delegates to `luo run --resume --flow-id`). `--dry-run` prints the command without executing. |
+| `luo history archived` | List only archived flows. `--json` for machine-readable output. |
+
+### `luo issue` — project issues
+
+| Subcommand | Purpose |
+|------------|---------|
+| `luo issue` / `luo issue list` | List open issues (default). `--all` includes closed; `--type <t>` filters by type. |
+| `luo issue show <id>` | Render an issue's full details. |
+| `luo issue create` | Interactively create a new issue (title, description, type, priority, tags). |
+| `luo issue reset <id>` | Reset an in-progress issue back to `open`. |
+
+### `luo daemon` — resident control plane
+
+| Subcommand | Purpose |
+|------------|---------|
+| `luo daemon start` | Start the daemon. `--foreground` keeps it attached; `--server-url <ws://…>` registers with a central server; `--daemon-key <key>` binds this machine to an owner on a multi-tenant server. |
+| `luo daemon stop` | Stop the running daemon. |
+| `luo daemon status` | Report run state, machine id, server URL, real connection state, and tracked flows. `--json` for machine-readable output. |
+
+---
+
+## Directory Layout
+
+Everything under `tianluo/` is gitignored by default *except* the whitelisted
+sub-paths shown below (the code-index map, charter, issues, scripts, prompts,
+and `version-rules.md` are tracked; runtime state and logs are not).
+
+```
+your-project/
+├── tianluo.yaml                       # Project config (tracked)
+├── tianluo.local.yaml                 # Local override   (gitignored)
+├── pyproject.toml                 # Single source of truth for project version
+├── VERSIONS.md                    # Changelog (maintained by documentation-updater)
+├── scripts/                       # Helper scripts
+├── .gitignore                     # Written / extended by `luo init`
+└── tianluo/                           # tianluo runtime root
+    ├── code-index.md             # ✅ tracked — authoritative structure map (LLM-injected, human-reviewable)
+    ├── charter.md                # ✅ tracked — project identity / architecture / invariants, injected in full every step
+    ├── issues/                   # ✅ tracked — open/ and closed/ YAML records
+    ├── prompts/                  # ✅ tracked — project-level preset prompt bodies (luo run --preset)
+    ├── version-rules.md          # ✅ tracked — optional, not present by default
+    ├── state/                    # ❌ runtime — engine.json, …
+    │   └── archive/              #   archived engine snapshots
+    ├── history/                  # ❌ runtime — per-flow per-step jsonl conversations
+    ├── logs/                     # ❌ runtime — execution logs (incl. logs/llm/ traces)
+    ├── calls/                    # ❌ runtime — pending human MCP call files
+    ├── cache/                    # ❌ runtime — derived caches (build locks, etc.)
+    ├── tmp/                      # ❌ runtime — transient prompt/response snapshots
+    └── worktrees/                # ❌ runtime — loop-mode / DAG isolation worktrees
+```
+
+---
+
+## Navigating the codebase
+
+The code-index *is* the index into this codebase. Start at the root view and
+drill down — you read the map's few lines first, and open source files only
+when you need the implementation detail behind a specific symbol:
+
+```bash
+luo code-index                           # the adaptive root map (budgeted zoomable tree)
+luo code-index index src/tianluo/engine      # one level: the engine package's immediate children
+luo code-index show src/tianluo/engine/code_index.py   # that file's full symbol tree
+```
+
+The same root-view map is injected automatically into every flow step, so the
+agent always carries a project-wide orientation map; deeper function-level
+detail is fetched on demand. Charter (`tianluo/charter.md`) is injected in full
+alongside it and carries the high-altitude facts — project identity, top-level
+architecture, and project-wide invariants — that every step needs to see whole.
+
+---
+
+## Version & License
+
+- Version is owned by `pyproject.toml` (`12.0.0`) and bumped by the engine's `version_analyze` + `commit` steps. Do not hand-edit it.
+- License: Apache-2.0.
+- See [VERSIONS.md](VERSIONS.md) for the full changelog.