@c4a/context-cli 0.7.8 → 0.7.10-alpha.1

package/indexers/bundles/context-note-indexer/references/classification.md

@@ -1,55 +1,28 @@
 # Choose the reader outcome
 
-Classify useful passages, not the entire file. Source type, reader-facing form
-and operation are independent choices. One source can correct an existing FAQ,
-add a decision explanation and contain irrelevant conversation at the same time.
-Explain classifications in the user's language in the work-start report; the
-profile IDs below are protocol identifiers, not headings for the reader.
+Read the saved material and compare its reader questions with the current
+article navigation, including topics originally discovered from code. A note
+or session may correct an existing answer, explain a decision, or justify a new
+article. Its filename and source type do not determine the article form.
 
-| Material and reader need | Suitable profile | Action |
-| --- | --- | --- |
-| A concrete question with a supported answer | faq-support | Update the matching answer; create only if the question is distinct |
-| A repeatable task with prerequisites and checks | technical-guide / user-and-developer-guide | Integrate steps into the existing guide or propose a missing task |
-| Operational diagnosis and recovery | runbook | Preserve symptoms, checks, safe actions and verification |
-| Confirmed choice with rationale and limits | decision-record | Explain the choice, applicability and meaningful alternatives |
-| Agreed intended behavior and acceptance conditions | product-requirements | Keep intended behavior distinct from current implementation |
-| A reusable term, relationship or domain rule | domain-reference | Define it with scope and useful examples |
-| An incident account supported by observations | incident-review | Separate observations, causes and unverified hypotheses |
-| A test method or reported validation result | test-validation | Retain method, scope and what the result actually demonstrates |
-| Repetition, superseded claims, unresolved speculation without reader value | No new target | Support, defer or exclude with a concrete reason |
-| A required reader outcome needs a capability this Provider does not supply | `unsupported` for the affected material | Name the actual missing capability using the current Route; report its scope and recovery |
+A question and supported answer can become a FAQ; repeatable steps belong in a
+guide or runbook; a confirmed choice needs rationale and limits; observations
+about an incident or test retain their actual scope. These are writing choices,
+not required profile registrations or fixed article counts.
 
-“FAQ”, “knowledge improvement” and “knowledge accumulation” are not three source
-storage types. FAQ is a reader form; improvement usually revises approved prose;
-accumulation may add a topic or enrich an existing one. Decide from the actual
-reader question and existing coverage. Never route every note/session into FAQ.
+Reuse the stable article identity when revising the same reader task. Similar
+titles alone do not establish that two articles should merge. Separate different
+versions or audiences when combining them would mislead readers. Several
+authorized sources may contribute to one article, regardless of which skills
+helped investigate them.
 
-Choose the closest applicable declared profile by reader task, then adapt its
-outline to the useful content. Headings, grouping and examples are writing
-choices, not new capabilities. An existing project template override takes
-precedence; use supported customization when a reusable local template is
-needed, not as a prerequisite for ordinary writing. Do not invent profile IDs
-or claim unsupported tools, source access or output contracts.
+Use the current plan submission for article targets and writing batches. A
+simple source can directly suggest its target; do not manufacture a separate
+per-passage classification ledger. Keep genuinely unfinished investigation in
+the stage's remaining scope. No independent article value may mean supporting
+an existing article, not excluding the source from all production.
 
-Reserve `unsupported` for a real capability gap that prevents the requested
-outcome within the authorized scope, not a mismatch with a stock outline. Name
-the missing capability in the current Route payload and explain which work is
-affected; follow its recovery instead of imposing an extra approval or stopping
-unrelated work yourself. Missing metadata or an unresolved claim can usually be
-bounded in useful prose. Request material only when the missing evidence is
-necessary to answer the reader's question; exclude material with no reader value.
-
-Reach for it rarely. The forms above are broad, and an awkward fit is not an
-absent one — a benchmark result is test-validation, a complaint with a supported
-answer is faq-support, an onboarding checklist is a guide. What decides is the
-reader question, not how the record happens to be laid out. A messy record, an
-unstated applicability boundary and an unfamiliar topic are none of them
-capability gaps; the first two are ordinary authoring work and the third is
-usually one of these forms under a name you have not seen before.
-
-Keep one subject identity for the same reader topic across updates. Two topics
-with the same title are not necessarily the same page; compare audience, scope
-and task. Do not merge different versions or platforms just to reduce page count.
-Conversely, do not split a coherent answer into thin pages because the source
-has many headings. Close the actual current inventory using the Route schema,
-including explicit dispositions for excluded material.
+Do not invent a tool capability or source authorization. Missing essential
+evidence is a scoped gap; an unfamiliar topic or imperfect stock outline is
+ordinary investigation and writing. Long-term exclusions need the applicable
+user authorization, not just a desire to finish sooner.

package/indexers/bundles/context-note-indexer/references/customization.md

@@ -1,36 +1,23 @@
-# Business replacement and customization
+# Choosing and adapting skills
 
-Enable the chosen skill through the host's ordinary skill switch. Install it
-through your organization's own channel; Context has no additional business
-skill installation or enabled registry. The Agent discovers currently visible
-`context-…-indexer…` skills, then reads their real SKILL.md and sibling
-context-indexer.yaml. A matching name is a discovery hint, not compatibility.
+Use relevant skills actually available in the current host. In planning,
+declare their names, usable entries when needed, and the scopes and purposes
+for which they help. The current stage returns that temporary guidance during
+planning and writing. A name is a discovery hint, not proof of semantic fitness.
 
-To replace a default, declare the business Provider as the primary for the
-selected requirement, using its observed version, supported profiles and actual
-distribution coordinates. Do not select the default too. Use the current
-Provider selection Route's host_visible_skills observation and indexers payload;
-let the host resolution action supply the actual bundle when requested. No host
-cache crawling or guessed version/integrity is needed.
+Adapt reader questions, grouping and outlines without registering a profile,
+verifying skill versions or hashes, or attaching a skill identity to formal
+articles. Multiple skills may complement one module or article. Use another
+available skill when it supplies useful interpretation; do not invent a
+missing capability or silently expand source permissions.
 
-For a reusable wording/template change, these defaults support instructions-append
-and template-override, not config or program-extend. Ordinary heading and grouping
-choices do not require customization. Follow the selected Provider's actual
-capabilities if it is a replacement. For independent
-source interpretation a standalone business Provider is appropriate. To enrich
-another primary, declare extension profiles and compatible fragments in its
-manifest and bind them with kind extension. The existing protocol validates
-these declarations; CLI never decides which business interpretation is best.
+A reusable specialist skill should describe its source interpretation,
+lightweight skeleton investigation, optional bounded helpers and writing
+guidance. Ordinary note/session work needs no parser program: read the supplied
+material and propose a target. Detailed source analysis belongs only where the
+current reader task needs it.
 
-An override is named by the declared template ID, not its bundle filename:
-`src/indexer/<indexer-id>/templates/note-faq-support.md` overrides
-`note-faq-support`, whose default file is `templates/faq-support.md`.
-Keep the required origin comment pointing to the selected skill, observed
-version and profile. The same local override and `instructions.md` apply to
-initial writing and approved-page revision; no separate revision template is needed.
-
-The default template is a writing aid, not a mandatory business taxonomy.
-Customize reader questions and examples without changing source identity,
-revision authority, provenance or the single-primary rule. Check an unrelated
-session, an excerpt with unavailable original, a rejected proposal, an existing
-page correction and a mixed-code target before distributing a replacement.
+When adapting guidance, check a source with an unavailable original, an
+unconfirmed proposal, a correction to an existing article and a mixed-code
+target. Preserve source strength, real citations and the current stage's file
+submission contract. Do not create persistent tool-selection or producer logs.

package/indexers/bundles/context-note-indexer/references/extension-placement.md

@@ -1,54 +1,28 @@
-# Where note material belongs in a base profile's page
+# Place supporting note material
 
-A `note/…` profile is an extension. It does not own a page and does not open a
-parallel one. The module stays on its base profile and selected page plan,
-including an applicable project template override. Contribute to the relevant
-sections; the attachment examples below are guidance, not a heading whitelist.
+Use the current article's reader question and supplied revision base, not a
+profile binding. Integrate relevant explanations into the appropriate sections
+without opening a parallel page or collecting everything under a generic
+"Notes" heading. The article can use several skills.
 
-Do not restate a base section the note has nothing to add to, and do not
-introduce a "notes" section to hold everything a note said.
-
-## What a note can establish that the base sources cannot
-
-Read the base profile's Chapter blueprint and notice which sections its own
-evidence can settle. Structure settles from code and contracts: entry points,
-signatures, registrations, schemas, dependency edges. Several sections in every
-base blueprint ask for something else — why a limit was chosen, what a timeout
-means for a caller, which combination is unsupported, what breaks on upgrade,
-which behavior is deliberate. Those are the sections a saved note is for.
-
-This is the useful division. If a note repeats a signature the code already
-establishes, it adds nothing and risks contradicting the authoritative source. If
-it carries a constraint, a known pitfall or an applicability boundary, it belongs
-in the section that asks for exactly that.
-
-## Attachment points by family
-
-| Family | Base profiles | Sections a note usually reaches |
-| --- | --- | --- |
-| Applications and containers | `monorepo-container`, `web-application` | `Dependency and layering constraints`, `Shared configuration and tooling`, `Configuration and environment selection`, `Known exclusions and source-of-truth links` |
-| Reusable capabilities | `component-library`, `sdk-library`, `cli-tool`, `plugin-extension` | `Compatibility and release constraints`, `Behavior, lifecycle, and errors`, `Recovery and rollback boundaries`, `Configuration, permissions, and isolation`, `Compatibility, failure, diagnostics, and recovery` |
-| Services and gateways | `api-service`, `gateway-facade`, `domain-service` | `Error, timeout, and compatibility behavior`, `Timeout, retry, compatibility, and failure translation`, `State, transaction, and idempotency behavior`, `Failure and recovery behavior`, `Configuration, observability, and release` |
-| Runtimes and data flow | `background-runtime`, `event-consumer`, `data-sync-reconciliation`, `storage-repository` | `Concurrency, ordering, retry, and idempotency`, `Idempotency, retry, checkpoint, and failure destination`, `Authentication, failure, retry, and fallback`, `Transaction, consistency, cache, and locking behavior`, `Failure recovery and observability` |
-| Boundaries and contracts | `adapter-integration`, `contract-source`, `derived-generated-source` | `Error, retry, fallback, and compatibility behavior`, `Versioning, compatibility, and deprecation`, `Generated versus maintained behavior`, `Compatibility and regeneration` |
-| Document profiles | `domain-reference`, `product-requirements`, `technical-guide`, `user-and-developer-guide`, `public-api-reference`, `runbook`, `faq-support`, `standard-policy`, `decision-record`, `incident-review`, `test-validation`, `release-migration-guide`, `documentation-site` | The base document blueprint keeps its shape; a note adds applicability, an exception, a correction or a missing definition |
-
-Read the section names from the actual base template the Route delivered. The
-table lists the sections these families most often need and is not the complete
-set; a base profile may declare a better-fitting section than the one named here.
+Code may establish entry points, signatures, registrations and current
+branches. Saved material can explain why a limit was chosen, an intentionally
+unsupported case, an operational exception or a known pitfall. Put those
+contributions where the reader needs them; do not repeat signatures or replace
+authoritative behavior with recollection.
 
 ## How the material reads once placed
 
-Attribute it. A base page's other sections are backed by code or contracts, so a
+Attribute it. An existing article's other sections are backed by code or contracts, so a
 sentence sourced from a note has to carry its own strength or a reader will
 assume the whole page is equally authoritative. "Recorded in an operations note:
 the retry limit was set to three to stay under the downstream quota" is placeable.
 "The retry limit is three" is not, unless the code establishes it — and if the
-code establishes it, the base section already owns that line.
+code establishes it, the existing section already owns that line.
 
 A note may report one occurrence or document an explicitly confirmed rule.
 Retain that distinction and its attribution. Qualify missing dates or versions
-where they affect the base section's meaning; do not generalize a single case
+where they affect the existing section's meaning; do not generalize a single case
 or demote a confirmed rule merely because either was saved as a note.
 
 When a note contradicts what the code establishes, do not silently pick one. The

package/indexers/bundles/context-note-indexer/references/indexer.md

@@ -32,8 +32,16 @@ note itself states the boundary, use it and proceed within authorization.
 
 ## Diagrams
 
-Use the materialized [diagram guidance](diagrams.md) when a diagram clarifies the reader task. This also applies to older templates, source diagrams and Composer summaries. Preserve source strength, version and external boundaries; diagram presence is not a completion requirement.
+Use the materialized [diagram guidance](diagrams.md) when a diagram clarifies the reader task. This also applies to source diagrams and combined articles. Preserve source strength, version and external boundaries; diagram presence is not a completion requirement.
 
 ## Existing source images and tables
 
 For authorized visual material, follow [source visual processing](visual-source-processing.md): preference, capability-aware conversion, accepted-result reuse and retention. Follow the workspace AGENTS.md for editable diagram style.
+
+## Reading selected article material
+
+Read the current task's brief and source navigation; choose relevant examples
+and source passages rather than enumerating profile bindings. For a revision,
+use the supplied base article and references. Reuse unchanged shared material
+already in context. The CLI checks source authorization, regional references
+and safe writes; the Agent decides the topic, meaning and useful diagrams.

package/indexers/bundles/context-note-indexer/references/updates-and-composition.md

@@ -1,37 +1,31 @@
 # Updates and composition
 
-First inspect the authorized existing knowledge and requested outcome. Saving
-input alone does not authorize a new indexing target. If a paragraph corrects
-an existing explanation, revise that approved page. Retain its useful steps,
-examples, images, limitations and confirmed contributions. If the material
-supports a new reader task, propose that topic through normal structure review
-before Author; never write directly to approved knowledge. If it adds nothing
-new, retain the source without producing a duplicate page.
+Start with existing article titles, descriptions and references. Read relevant
+article bodies or source passages when that navigation is insufficient. A
+correction belongs in the affected article; do not create a page merely to
+announce an improvement. A new reader question may justify a new target.
+Several authorized sources and skills may contribute to the same article.
+There is no primary-skill ownership or extension-profile binding to retain.
 
-Use one primary Provider per target. For an independent note/session topic this
-Provider may be primary with one of its declared document profiles. For an
-existing Code or Markdown page, retain that page's primary Provider. When this
-Provider's specialized interpretation is needed, select it as an extension
-layer and bind its prefixed extension profile to the active base profile, e.g.
-`note/component-library` extends `component-library`. `profile.additional`
-uses `kind: extension`, not `supporting`: supporting profiles belong to the
-same primary layer. Read actual manifests; do not invent a profile name for a
-business Provider.
+Use the current stage's plan submission to propose targets or append revision
+tasks. Preserve accepted articles; do not overwrite a successful task by
+resubmitting different content. Once a revision is issued, use its supplied
+base Markdown and reference table to edit only the necessary sections through
+the current submission schema. Keep useful unaffected examples and limitations.
 
-This is an instruction-only extension. Its selected references guide source
-interpretation in the primary task; it has no separate inspector/program and
-does not claim to emit machine fact fragments. It supplies source-backed
-distinctions, relevant reasons, conflicts and limits to the same writing task. It does not become a second author,
-replace the primary API table, or create a standalone session page merely
-because a source exists. Extend only the target's explicit evidence/read scope;
-a commit or URL in metadata does not authorize fetching it. If no extension is
-selected, the main Provider can still read authorized supporting material under
-its own guidance; do not silently enable an unavailable skill.
+Write drafts and submission files in the designated Agent temporary directory.
+Submit their paths through the current CLI action, not long shell arguments.
+The coordinator may submit a finished subset. Child Agents work only when the
+current host supports them and the issued directory permits that scheduling;
+they do not concurrently mutate shared production state.
 
-An incorrect source summary needs explicit correction by the host import flow,
-with current base_digest and task adjustment for pinned inputs. An accurate
-source but misleading page needs only approved-page revision. This Provider
-must not rewrite the original source to make a new page seem supported.
-A rejected revision leaves source material and approved content available for
-repair. Knowledge approval never changes upstream code, approves an MR, or
-turns a proposal into an adopted decision.
+An accurate source with a misleading article needs an article revision. An
+incorrect source needs the authorized source-import correction flow, not an
+Indexer quietly rewriting evidence. A source change invalidates affected task
+inputs; follow the CLI refresh action and preserve unrelated work.
+
+CLI acceptance saves a candidate for this run; it is not publication. Review
+rejection requires repair, not deletion of the article's responsibility.
+Temporary plans, candidates and receipts need not survive clearing temporary
+storage or changing machines. A new run starts from formal sources, confirmed
+long-term requirements and formal articles.

package/indexers/bundles/context-note-indexer/references/writing.md

@@ -6,7 +6,7 @@ smallest source span supporting each claim; link the stored summary when that
 is all you read. Never pretend its original conversation or linked document was
 available. Missing originals limit confidence, not permission to invent detail.
 
-Select the declared profile template for the actual reader task. Its headings
+Choose an outline for the actual reader task; a supplied template is optional guidance. Its headings
 are prompts, not required empty sections. A FAQ answers a coherent reader question
 or related set of questions; a guide teaches a task; a decision explains a choice and its
 limits. Do not make one page per source heading or one page per input file.
@@ -50,8 +50,8 @@ only when writing choices cannot solve the missing capability. Explain an actual
 tooling gap and the available recovery in the user's language, outside the
 knowledge page; do not turn an unfamiliar topic into a request for a new Provider.
 
-Before returning the current Route payload, read the page as a reader: can they
+Before submitting the draft files, read the page as a reader: can they
 answer the selected question without reconstructing the conversation? Check
-that each meaningful source topic is included, supporting, deferred or excluded
-with a concrete reason. A generic overview that drops the actual decision,
+that the article answers its planned reader question. Keep remaining investigation
+and real gaps visible in the stage; do not submit a per-passage disposition ledger. A generic overview that drops the actual decision,
 exception or resolution is incomplete even if its headings look correct.

package/indexers/bundles/context-note-indexer/templates/articles/c01.md

@@ -2,6 +2,17 @@
 id: context.article.c01
 kind: procedure
 media-type: text/markdown
+program:
+  article: c01
+  policies:
+    - standard
+  sections:
+    scope: 定位与边界
+    capabilities: 核心能力
+    dependencies: 技术与依赖摘要
+    index: 知识索引
+    tasks: 任务导航
+    sources: 来源与适用版本
 ---
 
 # C01 模块／知识入口

package/indexers/bundles/context-note-indexer/templates/articles/c02.md

@@ -2,6 +2,21 @@
 id: context.article.c02
 kind: procedure
 media-type: text/markdown
+program:
+  article: c02
+  policies:
+    - standard
+  sections:
+    goals: 业务目标
+    actors: 角色与场景
+    prerequisites: 使用前提
+    operations: 操作与结果
+    exceptions: 规则与异常
+    acceptance: 验收依据
+    version: 版本和范围
+    capabilities: 能力边界
+    flows: 主要流程入口
+    references: 相关系统与文档
 ---
 
 # C02 业务概览

package/indexers/bundles/context-note-indexer/templates/articles/c03.md

@@ -2,6 +2,15 @@
 id: context.article.c03
 kind: procedure
 media-type: text/markdown
+program:
+  article: c03
+  policies:
+    - standard
+  sections:
+    scope: 适用范围
+    terms: 术语表
+    distinctions: 易混概念
+    references: 相关入口
 ---
 
 # C03 术语与标识

package/indexers/bundles/context-note-indexer/templates/articles/c04.md

@@ -2,6 +2,16 @@
 id: context.article.c04
 kind: procedure
 media-type: text/markdown
+program:
+  article: c04
+  policies:
+    - standard
+  sections:
+    layers: 依赖分层
+    catalog: 核心依赖表
+    initialization: 初始化与注入
+    compatibility: 兼容和版本约束
+    boundaries: 跨边界定位
 ---
 
 # C04 依赖与协作边界

package/indexers/bundles/context-note-indexer/templates/articles/c05.md

@@ -2,6 +2,17 @@
 id: context.article.c05
 kind: procedure
 media-type: text/markdown
+program:
+  article: c05
+  policies:
+    - standard
+  sections:
+    symptoms: 现象索引
+    conditions: 适用条件
+    findings: 已知事实与判断
+    diagnosis: 排查步骤
+    recovery: 修复与验证
+    sources: 来源
 ---
 
 # C05 已知问题与排障

package/indexers/bundles/context-note-indexer/templates/articles/c06.md

@@ -2,6 +2,17 @@
 id: context.article.c06
 kind: procedure
 media-type: text/markdown
+program:
+  article: c06
+  policies:
+    - standard
+  sections:
+    context: 背景与问题
+    decision: 结论与状态
+    alternatives: 选项与取舍
+    impact: 影响范围
+    followup: 后续行动
+    sources: 来源与版本
 ---
 
 # C06 补充说明与决策

package/indexers/bundles/context-note-indexer/templates/articles/c07.md

@@ -2,6 +2,16 @@
 id: context.article.c07
 kind: procedure
 media-type: text/markdown
+program:
+  article: c07
+  policies:
+    - standard
+  sections:
+    entries: 问题到入口
+    identity: 源码身份与版本
+    reading: 推荐阅读顺序
+    boundaries: 外部边界
+    evidence: 进一步证据
 ---
 
 # C07 从知识继续查源码

package/indexers/bundles/context-note-indexer/templates/articles/d01.md

@@ -2,6 +2,16 @@
 id: context.article.d01
 kind: procedure
 media-type: text/markdown
+program:
+  article: d01
+  policies:
+    - standard
+  sections:
+    scope: 领域职责
+    services: 服务分工
+    entries: 入口与调用边界
+    collaboration: 数据与事件协作
+    references: 阅读导航
 ---
 
 # D01 领域架构与服务地图

package/indexers/bundles/context-note-indexer/templates/articles/d02.md

@@ -2,6 +2,17 @@
 id: context.article.d02
 kind: procedure
 media-type: text/markdown
+program:
+  article: d02
+  policies:
+    - standard
+  sections:
+    trigger: 场景与触发
+    actors: 参与方
+    flow: 主流程
+    branches: 分支与状态
+    failures: 失败和下一步
+    sources: 源码链路与证据边界
 ---
 
 # D02 业务流程与跨层链路

package/indexers/bundles/context-note-indexer/templates/articles/d03.md

@@ -2,6 +2,17 @@
 id: context.article.d03
 kind: procedure
 media-type: text/markdown
+program:
+  article: d03
+  policies:
+    - standard
+  sections:
+    scope: 业务与版本
+    catalog: 规则分类
+    conditions: 条件与结果
+    implementation: 执行位置
+    conflicts: 例外与冲突
+    references: 相关流程
 ---
 
 # D03 业务规则

package/indexers/bundles/context-note-indexer/templates/articles/d04.md

@@ -2,6 +2,21 @@
 id: context.article.d04
 kind: procedure
 media-type: text/markdown
+program:
+  article: d04
+  policies:
+    - standard
+  sections:
+    scope: 工程边界
+    commands: 构建与测试入口
+    delivery: 环境与交付
+    conventions: 兼容与研发约定
+    environment: 运行与环境
+    configuration: 配置定位
+    observability: 日志指标与追踪
+    diagnosis: 诊断路径
+    recovery: 恢复与回滚
+    verification: 验证依据
 ---
 
 # D04 运维与排障入口

package/indexers/bundles/context-note-indexer/templates/articles/f01.md

@@ -2,6 +2,17 @@
 id: context.article.f01
 kind: procedure
 media-type: text/markdown
+program:
+  article: f01
+  policies:
+    - standard
+  sections:
+    architecture: 架构总览
+    stack: 技术栈与运行方式
+    startup: 启动与分层
+    crosscutting: 关键横切能力
+    deployment: 部署边界
+    references: 相关入口
 ---
 
 # F01 架构

package/indexers/bundles/context-note-indexer/templates/articles/f06.md

@@ -2,6 +2,17 @@
 id: context.article.f06
 kind: procedure
 media-type: text/markdown
+program:
+  article: f06
+  policies:
+    - standard
+  sections:
+    scope: 模型范围
+    catalog: 类型目录
+    roles: DTO 与视图模型
+    mapping: 转换与校验
+    authority: 权威与生成关系
+    references: 使用与源码
 ---
 
 # F06 类型模型

package/indexers/bundles/context-note-indexer/templates/articles/f08.md

@@ -2,6 +2,19 @@
 id: context.article.f08
 kind: procedure
 media-type: text/markdown
+program:
+  article: f08
+  policies:
+    - standard
+  sections:
+    systems: 使用的组件库与设计系统
+    layers: 样式分层
+    tokens: Token 定义与消费
+    overrides: 局部覆盖
+    platforms: 主题与平台差异
+    accessibility: 响应式与可访问性
+    examples: 调整入口与示例
+    references: 系统规范与源码
 ---
 
 # F08 样式与设计系统

package/indexers/bundles/context-note-indexer/templates/articles/f09.md

@@ -2,6 +2,17 @@
 id: context.article.f09
 kind: procedure
 media-type: text/markdown
+program:
+  article: f09
+  policies:
+    - standard
+  sections:
+    scope: 工程与交付边界
+    prerequisites: 运行前提
+    commands: 构建与测试入口
+    deployment: 部署与配置
+    verification: 验证与回滚
+    references: 相关资料
 ---
 
 # F09 构建与部署

package/indexers/bundles/context-note-indexer/templates/articles/l01.md

@@ -2,6 +2,18 @@
 id: context.article.l01
 kind: procedure
 media-type: text/markdown
+program:
+  article: l01
+  policies:
+    - standard
+  sections:
+    purpose: 用途与适用范围
+    installation: 安装与初始化
+    capabilities: 主要能力
+    usage: 典型用法
+    contracts: 契约与扩展点
+    limits: 限制与兼容
+    references: 源码与验证入口
 ---
 
 # L01 公共能力与使用指南