dshseek

seek://news/awesome-170-additions-zero-delist

awesome-dsh-plugin Adds 170, No Delist (Nov 1, 2026)

Nov 1, 2026ecosystem#ecosystem #awesome-list← All news

TL;DR

Between 2026-10-31 20:26 and 2026-11-01 20:26 UTC the awesome-dsh-plugin list merged 170 entries in a trickle and three bursts and deleted none — the second zero-delist window in three days. Twelve names doubled from one entry to two, five multi-entry fronts grew by one, and two names shrank by rename. The window's 279 commits hold no merge at all, and both tracked fronts stay at 16 and 14.

awesome-dsh-plugin Adds 170 in a Trickle and Three Bursts with No Delist and No Merge — Twelve Names Double, Five Multi-Entry Fronts Grow, One In-Window Entry Changes Owner by Rename, and the Tracked Fronts Hold at 16 and 14.

The previous window closed at 20:26 UTC on October 31 with 184 additions and a single swap-shaped delist. The day that follows holds 170 new entries between 2026-10-31 20:26:01 UTC and 2026-11-01 20:26:42 UTC — again inside the band this series has been printing (141, 173, 21, 330, 234, 153, 203, 184, now 170). What separates the window is what it does not contain: not one deletion and not one merge commit.

A trickle and three bursts, none of them merged

The window holds 279 commits, 65 of them the automated regenerate READMEs from data/plugins chores — and zero merges. Every one of the 170 additions landed as a direct commit to the catalog. The trickle opened the evening: zrrrrrrr77/dsh-breather (#11007) at 23:24:39 UTC and Rayle8/dsh-aside-note (#11003) at 23:24:49 UTC on October 31, ten seconds apart. The first burst put down 132 entries across 131 commits between 16:58:00 and 17:30:40 UTC on November 1. The second added 19 entries across 18 commits between 17:59:29 and 18:11:50 UTC. The third closed the books with 17 entries across 17 commits between 20:22:18 and 20:25:18 UTC. The tree arithmetic closes around them: 8,105 yml entries at the boundary, 8,275 at the window’s last commit, the +170 net exactly the additions minus the zero deletions.

Per-commit counting sees 173 add-rows against the cumulative diff’s 170, and the three extras are the successor paths of the window’s renames — the same reconciliation class the previous two windows documented, with no merge-commit inflation to subtract this time.

The empty columns: no delist, no merge

Two days ago the series recorded a window with no delist at all; yesterday’s carried one deletion, the owner swap that folded a standalone sidebar rebuild into its successor pack. This window’s deletion column is empty again — the second zero-delist window in three days. And the merge column, which yesterday held exactly one entry (Haitang-Hub’s dsh-infinite-canvas, delivered by PR #10965), holds none: the window’s 279 commits are all direct-to-main catalog work. The contrasts are observational, not evaluative — the list states no policy behind either shape, and none is invented here.

Three renames, one of them same-day

Renames traveled in a tight band between 17:03 and 17:30 UTC. taoziliyouchong’s dafeiyu_dsh_pdf_jump became dsh-pdf-jump (#11072, 17:03:09 UTC), a legacy underscored filename giving way to the dsh-prefixed form. Yuuyuko-uu’s dsh-qq-bridge became dsh-qq-link (#11052, 17:29:48 UTC) — a rename that shrinks the dsh-qq-bridge name from four entries to three and mints dsh-qq-link at one. Between them, at 17:16:02 UTC inside a batch-fixes commit, liyuxuan20111101’s stronger-dsh entry — added to the catalog itself at 17:07:20 UTC, nine minutes earlier — moved to the nothurry owner. That last one is the add-then-rename class this series has now caught at 63 seconds, 35 seconds, seven and a half minutes and eight minutes forty-two seconds: the entry never exists at HEAD under its birth name, so the cumulative diff records only the arrival of the renamed form.

The ledger: twelve doublings, five growing fronts

Twelve names went from one entry to two in a single window: dsh-app-updater, dsh-archive-delete, dsh-archived-sessions, dsh-chat-history, dsh-douyin-agent, dsh-memory-palace, dsh-memory-plugin, dsh-mobile-shell, dsh-model-visibility, dsh-mood, dsh-peak-valley and dsh-sidebar-sections. Five already-multi fronts grew by one: dsh-remote 4 to 5, dsh-git-panel 3 to 4, dsh-opencode-usage 2 to 3, dsh-rules 2 to 3, and mattpocock-skills-dsh 2 to 3 — the last welcoming a third entry under the same name. The two fronts this series tracks held: entries named exactly dsh-session-delete stayed at 16 and dsh-memory at 14, both frozen for a second consecutive window.

Review machinery alongside

Five fix commits ran beside the waves: prerequisites and platform notes from batch review at 17:24:13 UTC; post-merge entry corrections from batch review at 17:34:31 UTC; dsh-design and firefly-pet prerequisites at 18:10:25 UTC; WHOOP prerequisite and firefly wording at 20:25:38 UTC; and the window’s last commit 3c2da440 at 20:26:42 UTC — batch 02 prerequisites, fork disclosure and routing wording. One data commit at 20:25:38 UTC carried a different kind of maintenance: it applies three PRs that had conflicted on GitHub — #11211 updating dsh-opencode-palette’s tarball to v2.1.12, #11114 trimming the dsh-git-graph-sidebar intro, and #10500 correcting dsh-autorestart 0.8.5’s description to say restores cover only verified safe backups — as a direct 3-file, 5-insertion, 5-deletion commit. The update side also moved version pins the series has followed: DeepSeek Cost Meter to 0.3.0 (#11208), dsh-moa-native to 4.3.11/4.3.12 with enforced subagent gating and an anonymized model face (#11213), dsh-power-switch to v0.1.5 (#11167), and the ds-harness-remote listing (#11205).

More in this series

Official references