# Changelog All notable changes to RecoWork are documented here. This project follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and [Semantic Versioning](https://semver.org/). This changelog records functional behavior, compatibility, migration, CLI, template, target, and generated-artifact changes. It excludes website-only visual, copy, layout, interaction-polish, and documentation-presentation changes. ## [Unreleased] ## [3.2.2] - 2026-08-21 ### Changed - Durable workflow templates now organize formal work by stable modules. Each module uses `index.md` as its entry point and `整体方案.md` (`zh`) or `overall-plan.md` (`en`) as its Current authority document; specialized child documents are created only for an independent lifecycle, audience, review path, or change cadence. - `rw view` now refreshes its open document and navigation automatically when Markdown or index content changes in the local workspace. ### Compatibility - Existing workspaces remain user-owned and are not reorganized automatically. The new convention applies to new work and to user-confirmed consolidation of existing material. ## [3.2.1] - 2026-08-21 ### Fixed - Hardened `rw view` startup: the Markdown renderer now uses a dedicated viewer asset route and loads only when a document is opened, so an unavailable renderer cannot hide workspace navigation or the current-work dashboard. The affected document shows a localized recovery message instead of a blank page. ## [3.2.0] - 2026-08-20 ### Added - Added `rw view [directory]`, a zero-configuration local Markdown viewer for RecoWork workspaces. It is read-only, localizes its own UI from the workspace locale, follows `index.md` for current-work navigation, and keeps localized archives behind an explicit toggle. It recognizes either a project root or a workspace directory passed directly, supports URL document routes, scope-aware full-text search, concise overview metadata, breadcrumb/previous/next navigation, GitHub-flavored Markdown, collapsible nested navigation, and fixed header/sidebar scrolling. Local agents start it through `npx --yes recowork@latest view .` after initialization or on a browse request; an already-running viewer for the same workspace is reused automatically. - `idea-to-project` local workspaces now include `parked-ideas.md` for restartable directions. It records the parking reason, restart condition, priority, last assessment, related material, and next step without mixing parked work with open questions or archived history. - Idea-to-project Chat / mobile instructions and continuation summaries now retain parked directions and their restart conditions. ## [3.1.0] - 2026-08-18 ### Changed - Durable local workspaces now keep formal directories and normal indexes limited to Current or still-open material. Confirmed historical versions and completed process material are organized in a separate localized archive by category, topic, and version. ### Compatibility - Existing workspace files remain user-owned. RecoWork never moves, archives, deletes, renames, or rewrites them automatically; agents must present archive candidates and obtain user confirmation first. ## [3.0.0] - 2026-08-16 ### Fixed - Local-agent initialization prompts and first-run documentation now use `npx --yes recowork@latest`, so users can fetch and run RecoWork without a globally installed `rw` command or an interactive npm installation prompt. ### Changed - Replaced the separate `idea-engineering` and `project-engineering` choices with `idea-to-project`: one staged workflow for exploration, validation, explicit project entry, and project advancement. - Renamed the Chinese template labels to “从想法到落地” and “系统性学习”; template IDs, commands, and existing workspaces remain unchanged. ### Compatibility - Existing idea and project workspaces remain untouched. `rw status` and `rw upgrade` now provide a read-only guide to initialize the unified workflow in a separate destination; no in-place conversion is attempted. ### Breaking Changes - `idea-engineering` and `project-engineering` are no longer available as independent templates for new initialization, listing, or display. Use `idea-to-project` for the unified workflow; the `idea` and `project` aliases continue to resolve to it. ## [2.0.0] - 2026-07-24 ### Added - Added `web-design-standard`, a reusable product-web design standard that produces one localized standard file for local agents and a standalone responsive-web prompt for Chat / mobile. ### Changed - Retired `general-ai-workflow` because its daily-task scope did not provide a sufficiently distinct reusable workflow. New initialization now directs users to idea, project, or learning workflows; existing general workflow files remain untouched and receive a read-only migration guide from `rw status` or `rw upgrade`. - Local initialization now safely integrates a marker-bounded RecoWork block into an existing root `AGENTS.md`; upgrades preserve a user-modified or removed managed block. - Workflow role contracts now require objective assessment of risks, contradictions, weak assumptions, and credible alternatives instead of reflexive agreement. ### Compatibility - Existing root `AGENTS.md` content remains unchanged outside the managed RecoWork block. Existing workflows are not modified automatically. - Existing `general-ai-workflow` files remain untouched; use the migration guidance from `rw status` or `rw upgrade` to initialize a separate supported workflow. ### Breaking Changes - `general-ai-workflow` and its `general`, `task`, and `daily` aliases can no longer be initialized, listed, or shown. ## [1.0.0] - 2026-07-21 ### Added - Added the `chat-mobile` target with a start instruction, task protocol, and manual continuation/migration summary. - Added the `local-agent-project` target with tool-neutral `AGENTS.md`, working methods, a durable workspace, and safe upgrade support. - Added legacy chat migration guidance that initializes a separate local workflow without touching existing files. ### Changed - Replaced brand-specific targets with the two user-facing environments: Chat / mobile and desktop AI assistant. - Consolidated durable knowledge into canonical workspace documents and indexes instead of a separate knowledge directory. - `rw add` now refuses destinations that already contain `rw-manifest.json`, preventing reinitialization from overwriting an existing workflow. - Updated templates, CLI prompts, bilingual README files, specifications, and the documentation site for the new environment model. ### Removed - Removed brand-specific target output, native skills, platform configuration folders, and Notion/Feishu document exports. ### Compatibility - Legacy target names remain CLI aliases and resolve to `chat-mobile` or `local-agent-project`. - Existing workspaces remain untouched. Legacy Chat workflows receive a migration command for a separate local destination. ### Breaking Changes - Brand-specific generated paths and native skill output are no longer produced. Use `local-agent-project` for complete local workflows or `chat-mobile` for lightweight chat workflows. ## [0.4.0] - 2026-07-20 ### Added - Learning workflows now require a confirmed learning agreement before generating or changing a roadmap, lesson, practice plan, or project plan. - Project workflows now require a confirmed project agreement before generating or changing a complete solution, plan, or implementation. - Confirmation gates are included in localized role contracts, working methods, chat prompts, and project instructions. ### Changed - `learning-engineering` and `project-engineering` templates are now version `1.1.0`. - The published npm package now exposes repository, homepage, and issue-tracker links; the bundled CLI reference links to guided setup, source, releases, and AI-led initialization. ### Compatibility - Existing workflows are not changed automatically. Run `rw upgrade --plan .` to review available method and target updates; apply only updates that remain unmodified in the user project. - New initializations pause for explicit confirmation only before broad learning or project design work. Explicitly confirmed local tasks can proceed without repeated confirmation. ## [0.3.0] - 2026-07-12 ### Added - Localized target output paths and static content for Chinese and English initialization. - Document standards, index-first retrieval, and index maintenance across durable workflow templates. - Conventional Commit guidance for contributors and AI agents. - A conservative workflow upgrade advisor with versioned manifests, read-only checks, safe updates, and workspace review reports. ### Changed - Chinese initialization now generates user-facing paths such as `知识库/` and `示例/` while preserving tool convention files. - Target locale changes remove stale generated files from the previous locale when they are safe to replace. - Workspaces are now explicitly user-owned during upgrades: existing workspace content is never overwritten, moved, deleted, or restored. - Upgrade reports are written to `.recowork/upgrade-reports/`, outside user-owned workspaces. ### Compatibility - Existing workflows are not changed automatically. Run `rw upgrade --adopt .` before using upgrade checks on legacy manifests. - New workspace templates require `--scope workspace --add-missing`; existing workspace files remain untouched. ## [0.2.2] - 2026-07-09 ### Fixed - Added a `recowork` executable alias so `npx recowork ...` resolves and runs correctly. ## [0.2.1] - 2026-07-09 ### Fixed - Published the root package that includes the CLI entry point, templates, and targets. ## [0.2.0] - 2026-07-09 ### Deprecated - This version was published without the required executable entry point. Use `0.2.2` or later.