Sync GitHub commit 9894459

CONTRIBUTING.md

@@ -6,6 +6,18 @@ This repository is intentionally narrow. It tracks the new AI and coding-agent m
 
 Before submitting, read the [curation standard](meta/CURATION.md). Maintainers use it to decide whether a resource is specific, stable, and useful enough for the list.
 
+## Fastest Contribution (Under Five Minutes)
+
+If you are suggesting one resource and do not want to prepare a fork, use the [resource suggestion form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=resource-suggestion.yml). Include:
+
+- the canonical public URL;
+- the most specific README category;
+- one sentence on the contribution, novelty, or practical value for recurring agent systems;
+- the source type and evidence tier;
+- any caveat, such as vendor bias, a paywall, early-stage status, or weak evidence.
+
+Maintainers will still apply the same scope, duplication, source-quality, and annotation checks used for pull requests. Corrections to an existing annotation are equally useful; link the current entry and state exactly what should change.
+
 ## Quick PR Flow
 
 1. Search `README.md` for the resource title, author, project, and URL.

README.md

@@ -43,7 +43,7 @@ configs:
 </p>
 
 <p align="center">
-  <a href="#start-here">Start here</a> |
+  <a href="#build-from-this">Build from this</a> |
   <a href="#pattern-library">Pattern library</a> |
   <a href="examples/README.md">Examples</a> |
   <a href="schemas/loop-contract.schema.json">Schema</a> |
@@ -64,7 +64,7 @@ configs:
 </p>
 
 <p align="center">
-  <sub>Useful? Star the repository to find it again, <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/fork">fork the contracts and dataset schema</a>, or <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/subscription">watch releases</a> for curated updates.</sub>
+  <sub>Useful? Star the repository to find it again, <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/fork">fork the contracts and dataset schema</a>, or <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/subscription">watch Releases and Discussions</a> for curated updates.</sub>
 </p>
 
 Awesome Loop Engineering is a curated, implementation-oriented field guide to **Loop Engineering**: the layer above prompt, context, and harness engineering for designing recurring AI-agent systems.
@@ -1032,6 +1032,35 @@ Where this project is going and where to talk about it.
 - 🧾 **Template** [Discussion guide](meta/DISCUSSIONS.md) - Suggested discussion categories, starter prompts, and moderation standard.
 - 🔁 **Pattern** [Show your Loop Engineering patterns](https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2) - Community discussion for real or anonymized loop examples.
 
+<h2 id="build-from-this">Build From This</h2>
+
+Use the repository as an implementation kit, not only as a reading list.
+
+<table>
+  <tr>
+    <td><strong>Run locally</strong></td>
+    <td>Follow the <a href="examples/runnable/README.md#test-repair-loopsh">test-repair walkthrough</a>, then switch to the runtime that owns your trigger and isolation.</td>
+  </tr>
+  <tr>
+    <td><strong>Adapt a contract</strong></td>
+    <td>Start from the <a href="examples/ci-repair-loop.json">CI repair contract</a> and replace its objective, intake, checks, budget, and escalation rules.</td>
+  </tr>
+  <tr>
+    <td><strong>Validate a contract</strong></td>
+    <td>Use the <a href="packages/loop-contract-schema/README.md"><code>loop-contract-schema</code> package</a> in CI or call the JSON Schema from your own validator.</td>
+  </tr>
+  <tr>
+    <td><strong>Analyze the field</strong></td>
+    <td>Use the <a href="data/README.md">dataset export guide</a> to work with the CSV, JSONL, source audit, and Resource Atlas payload.</td>
+  </tr>
+  <tr>
+    <td><strong>Contribute one source</strong></td>
+    <td>Use the <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=resource-suggestion.yml">resource suggestion form</a> or the <a href="CONTRIBUTING.md#fastest-contribution-under-five-minutes">under-five-minute contribution path</a>.</td>
+  </tr>
+</table>
+
+[Fork the repository](https://github.com/ChaoYue0307/awesome-loop-engineering/fork) to adapt the contracts, runnable templates, and dataset schema for your own loop system.
+
 ## Contributing
 
 Contributions are welcome. Please read [CONTRIBUTING.md](CONTRIBUTING.md) before opening a pull request.

README.zh-CN.md

@@ -7,7 +7,7 @@
 </p>
 
 <p align="center">
-  <sub>如果这个项目对你有帮助，可以 Star 以便再次找到它，<a href="https://github.com/ChaoYue0307/awesome-loop-engineering/fork">Fork loop contracts 与数据 schema</a>，或<a href="https://github.com/ChaoYue0307/awesome-loop-engineering/subscription">订阅 Releases</a> 获取精选更新。</sub>
+  <sub>如果这个项目对你有帮助，可以 Star 以便再次找到它，<a href="https://github.com/ChaoYue0307/awesome-loop-engineering/fork">Fork loop contracts 与数据 schema</a>，或<a href="https://github.com/ChaoYue0307/awesome-loop-engineering/subscription">订阅 Releases 与 Discussions</a> 获取精选更新。</sub>
 </p>
 
 <p align="center">

ROADMAP.md

@@ -8,19 +8,21 @@ This roadmap keeps Awesome Loop Engineering focused on useful, verifiable work f
 - Add real or anonymized gallery entries from practitioners running recurring agent loops.
 - Grow the runnable loop directory beyond the test-repair reference loop, including scheduled-trigger variants per runtime.
 - Add more translations for the introduction, mental model, Loop Contract, and contribution guide.
+- Audit contextual sources in small batches and replace weak summaries or secondary links with stronger canonical evidence.
 - Continue replacing weak or unstable links with primary sources, official docs, papers, and implementation-heavy write-ups.
 
 ## Pattern Library
 
-Completed reference patterns now cover PR babysitting, CI repair, docs drift, deploy verification, feedback clustering, dependency triage, evaluation regression, security review, cost-control, and bug hunting. Every pattern now ships a schema-validated loop contract in `examples/`.
+The library now contains 15 reference patterns: PR babysitting, CI repair, docs drift, deploy verification, feedback clustering, dependency triage, evaluation regression, security review, cost control, bug hunting, enterprise approval, incident response, data quality, release notes, and model routing. Every pattern ships a schema-validated loop contract in `examples/`.
 
-Next pattern-library work should focus on variants backed by operational evidence:
+Next pattern-library work should prioritize variants backed by operational evidence rather than adding names for coverage. Useful additions include runtime-specific implementations, before/after receipts, measured retry and cost budgets, failure cases, and human-escalation outcomes.
 
-- enterprise approval loops for permissioned agents;
-- incident response loops with pager handoff and postmortem evidence;
-- data-quality loops for repeated dataset or knowledge-base refresh;
-- release-note loops that connect commits, issues, docs, and changelogs;
-- model-routing loops that balance quality, latency, privacy, and cost.
+## Community And Adoption
+
+- Publish a concise monthly Discussions digest with corrected annotations, new primary sources, and open contributor tasks.
+- Keep several narrowly scoped `good first issue` and `help wanted` tasks available for source audits, translations, runnable examples, and gallery case studies.
+- Ask cited authors to review the repository's characterization of their work; request corrections, not promotion or stars.
+- Track qualified traffic, forks, watchers, and external contributions after each launch channel while GitHub traffic data is still available.
 
 ## Gallery
 

docs/index.html

@@ -1016,7 +1016,7 @@
             <p class="section-intro">Add a vetted source with a specific annotation, or document a loop you actually run. Both paths have a checklist.</p>
           </div>
           <div class="link-grid">
-            <a class="card" href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/CONTRIBUTING.md"><h3>Add a resource</h3><p>Primary sources and implementation-heavy work, with one precise annotation.</p></a>
+            <a class="card" href="https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=resource-suggestion.yml"><h3>Suggest a resource</h3><p>Submit one canonical source and a precise annotation in under five minutes.</p></a>
             <a class="card" href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/gallery/README.md"><h3>Share a loop</h3><p>Publish a real or anonymized case study using the gallery checklist.</p></a>
             <a class="card" href="https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2"><h3>Join the discussion</h3><p>Compare operating patterns with other loop builders.</p></a>
           </div>
@@ -1085,7 +1085,7 @@
             <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/CONTRIBUTING.md">Contributing</a>
             <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/fork">Fork and adapt</a>
             <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/releases">Release notes</a>
-            <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/subscription">Watch releases</a>
+            <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/subscription">Watch releases + discussions</a>
             <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/ROADMAP.md">Roadmap</a>
           </div>
           <div>

meta/DISTRIBUTION.md

@@ -2,6 +2,19 @@
 
 Use this checklist after major updates or releases. The goal is accurate discovery, not hype.
 
+## Current Launch Status
+
+Status as of 2026-07-17:
+
+| Surface | Status | Evidence / next action |
+| --- | --- | --- |
+| GitHub release | Complete | [`v0.5.0`](https://github.com/ChaoYue0307/awesome-loop-engineering/releases/tag/v0.5.0) describes 509 resources and links the atlas, dataset, templates, and contribution guide. |
+| GitHub Explore topic | Complete | [`github/explore#5209`](https://github.com/github/explore/pull/5209) merged the `loop-engineering` topic page. |
+| Canonical Awesome directory | In review | [`sindresorhus/awesome#4339`](https://github.com/sindresorhus/awesome/pull/4339) is open with a passing lint check. Respond to maintainer feedback; do not open a duplicate. |
+| Hugging Face dataset | Complete | [`datasets/cy0307/awesome-loop-engineering`](https://huggingface.co/datasets/cy0307/awesome-loop-engineering) carries the structured resource sheet and full project mirror. |
+| English and Chinese launch articles | Ready | Publish [`posts/launch.md`](../posts/launch.md) and [`posts/launch.zh-CN.md`](../posts/launch.zh-CN.md) natively on suitable channels. |
+| Profile pin and social posting | Owner action | Pin the repository, then publish from identity-bound LinkedIn, X, Hacker News, and Chinese-language accounts. |
+
 ## Indexing Basics
 
 - Confirm the repository is public.
@@ -25,9 +38,9 @@ The repository is mirrored to the Hugging Face Hub dataset repo [`datasets/cy030
 
 Discoverability levers that live on GitHub itself, in priority order.
 
-- **Topic page (`github/explore`).** There is no curated page for the [`loop-engineering` topic](https://github.com/topics/loop-engineering) yet. A page is prepared on the fork branch `ChaoYue0307:add-loop-engineering-topic` (file `topics/loop-engineering/index.md`); open a PR from that branch to `github/explore`. This describes the topic, not this repo specifically, so it promotes the concept and helps the whole ecosystem.
-- **sindresorhus/awesome submission.** The canonical awesome-list promotion; opens after the 30-day age rule (~2026-07-09). Use [`AWESOME_SUBMISSION.md`](AWESOME_SUBMISSION.md).
-- **Reciprocal entries on adjacent lists** this repo already cites (harness, context, agent-papers lists). Ready-to-paste entry:
+- **Topic page (`github/explore`).** The [`loop-engineering` topic](https://github.com/topics/loop-engineering) now has a curated page through merged PR [`github/explore#5209`](https://github.com/github/explore/pull/5209). Keep the topic description ecosystem-wide rather than repository-specific.
+- **sindresorhus/awesome submission.** Track the open canonical directory PR at [`sindresorhus/awesome#4339`](https://github.com/sindresorhus/awesome/pull/4339) and respond to maintainer feedback quickly. Use [`AWESOME_SUBMISSION.md`](AWESOME_SUBMISSION.md) for the acceptance criteria.
+- **Editorial submissions to adjacent lists** this repo already cites (harness, context, and agent-paper lists). Submit only where the maintainers explicitly accept related resources. Ready-to-paste entry:
 
   ```md
   - [Awesome Loop Engineering](https://github.com/ChaoYue0307/awesome-loop-engineering#readme) - Recurring AI/coding-agent systems above prompt, context, and harness engineering: patterns, contracts, runnable loops, and curated resources.
@@ -35,7 +48,37 @@ Discoverability levers that live on GitHub itself, in priority order.
 
 - **Pin the repository** on your profile, and add it to your profile README (profile-level promotion).
 - **Custom social preview** (repo Settings, Social preview) so shared links render with the cover image. This is UI-only; it cannot be set through the API.
-- **Releases** notify watchers and appear on the repo; the latest is the cleanest moment to share.
+- **Releases and Discussions** provide a lower-noise subscription path. Recommend `Watch -> Custom -> Releases and Discussions`; do not ask readers to watch every repository event.
+
+Do not use reciprocal-star requests, broad promotional pull requests, or unrelated issue comments. Every directory or newsletter submission should satisfy its normal editorial policy on its own merits.
+
+## Measurement Baseline
+
+GitHub retains repository traffic details for only 14 days. Record a snapshot weekly, using the same definitions each time.
+
+Baseline captured on 2026-07-17 for the API window ending 2026-07-15:
+
+| Metric | Baseline |
+| --- | ---: |
+| Repository views | 333 |
+| Unique visitors | 142 |
+| Clones | 204 |
+| Unique cloners | 81 |
+| Stars | 24 |
+| Forks | 3 |
+| Watchers | 1 |
+
+The repository overview reached 119 unique visitors. The Chinese README was the second-most visited content path with 19 unique visitors. The largest identifiable referrers were Google (17 unique visitors), GitHub (14), Bing (14), and the project site (6); launch and community channels had not yet become material sources.
+
+Working 30-day campaign targets:
+
+- 1,000-1,500 unique visitors;
+- 75-100 total stars;
+- 8-12 forks;
+- 5-8 watchers;
+- at least 5 external contributors.
+
+Treat these as measurement targets, not promises. Log the publication date and canonical URL for each channel, then compare referral traffic and qualified contributions rather than optimizing for raw impressions.
 
 ## Launch Copy
 

meta/MAINTENANCE_CALENDAR.md

@@ -8,6 +8,7 @@ Run the local checks in [MAINTENANCE.md](MAINTENANCE.md#local-verification) befo
 
 - Review the latest Quality workflow run; if the scheduled link check failed, fix or replace the dead link.
 - Triage new issues, pull requests, and discussion posts.
+- Record the 14-day traffic snapshot and referral mix beside the [measurement baseline](DISTRIBUTION.md#measurement-baseline) before GitHub expires the older daily rows.
 - Review candidate resources gathered during the week; add only those that pass [CURATION.md](CURATION.md) and reject the rest with a reason.
 - Confirm no entry drifted off-scope into generic AI-agent, prompt, context, or harness content.
 - Confirm the [Hugging Face dataset mirror](https://huggingface.co/datasets/cy0307/awesome-loop-engineering) is in parity with `main` (the daily routine syncs it; spot-check after manual pushes).
@@ -19,6 +20,7 @@ Run the local checks in [MAINTENANCE.md](MAINTENANCE.md#local-verification) befo
 
 ## Monthly
 
+- Publish one concise Discussions digest covering new resources, corrected annotations, patterns, contracts, and open contributor tasks.
 - Refresh runtime docs: re-verify the Core Loop Primitives and Official Runtime Guides links and annotations against current product docs.
 - Refresh benchmarks and evals: check that cited benchmarks, leaderboards, and eval papers are current and that links resolve.
 - Stale-resource review: replace weak or superseded links with stronger primary sources; remove anything that rotted with no equivalent.
@@ -30,24 +32,15 @@ Run the local checks in [MAINTENANCE.md](MAINTENANCE.md#local-verification) befo
 - Roadmap review: update [ROADMAP.md](../ROADMAP.md) with shipped work and the next pattern, gallery, and runtime priorities.
 - Translation drift review: confirm each translated README still matches the canonical English overview and bump the `last-synced` markers; see [TRANSLATIONS.md](../TRANSLATIONS.md).
 
-## Pre-Submission Checklist (before 2026-07-10)
+## Canonical Awesome Submission Status
 
-The upstream Awesome 30-day rule opens the submission window on 2026-07-10. Before then:
+The 30-day age requirement has passed. [`sindresorhus/awesome#4339`](https://github.com/sindresorhus/awesome/pull/4339) is open and its lint check is passing as of 2026-07-17.
 
-- [ ] Run the full preflight in [AWESOME_SUBMISSION.md](AWESOME_SUBMISSION.md#required-preflight) and fix every actionable finding.
-- [ ] Confirm `awesome-lint` passes locally and against the public GitHub URL.
-- [ ] Confirm the README scope, contribution guide, and license are present and current (note: CI and last-updated badges were deliberately removed per awesome-list guidelines; keep only the Awesome badge).
-- [ ] Review at least four open PRs in `sindresorhus/awesome` with substantive comments.
-- [ ] Draft the `Add Loop Engineering` PR title, entry (URL ending in `#readme`), and PR body.
-- [ ] Confirm a tagged release and a green Quality run on `main`.
-
-## Post-Submission Checklist (after 2026-07-10)
-
-- [ ] Open the `sindresorhus/awesome` PR and comment `unicorn` to confirm the guidelines were read.
-- [ ] Respond to maintainer feedback quickly; keep changes scoped and owner-authored.
-- [ ] Once listed, add reciprocal entries on adjacent lists where appropriate, under your own identity.
-- [ ] Run the distribution steps in [DISTRIBUTION.md](DISTRIBUTION.md): landing page, launch post, and author outreach.
-- [ ] Keep public claims conservative: an early curated field guide, not a finished standard.
+- Do not open a duplicate submission.
+- Respond to maintainer feedback quickly and keep changes scoped and owner-authored.
+- Re-run the full preflight in [AWESOME_SUBMISSION.md](AWESOME_SUBMISSION.md#required-preflight) after any structural README change.
+- If accepted, submit to adjacent directories only where the normal editorial policy permits related lists.
+- Keep public claims conservative: this is an early curated field guide, not a finished standard.
 
 ## See Also