Connect Projects, Essays, and the CLI into One Discoverable Path

The through-line: make project and content entry points work as one

W32 was less about starting many new capabilities and more about completing the public paths around work that already existed: project pages, essays, npm usage, and weekly reports now connect more clearly for both people and agents.

Restoring the public weekly archive

The missing W30 and W31 reports were restored on both the Chinese and English sides, using the existing weekly collection, detail pages, and JSON APIs. The reports continue to use Git history and docs/dev-log as their evidence base; plans are not presented as completed work.

This also reconnected the full archive path: content files, bilingual mirrors, page routes, and machine-readable endpoints all follow the same schema.

Two projects entered the site

Two existing sites were added to the project index:

• FreeModel Port: a free-model directory and unified routing entry point for local agents. The public directory produces candidates; real request results determine what is actually runnable.
• OpenWorker Chinese site: a Chinese-facing site, localized build, and source analysis for Andrew Ng’s open-source OpenWorker. The project page separates the upstream project, the localized build maintained here, and the source research.

Both projects received Chinese and English entries, detail-page routes, covers, and JSON data. Their limits remain explicit: a unified router is still a high-privilege control plane, local-first does not mean zero external traffic, and an OpenWorker build is not a production guarantee.

The npm / CLI guide went live

The site now has dedicated /npm and /en/npm pages covering installation, npx usage, command groups, and agent use cases for zhanglu-net. The pages also warn readers not to confuse this CLI with the unrelated npm package named zhanglu.

That gives the shorter /agents explanation a clear deep-link, while making the relationship between the CLI, JSON API, llms.txt, and site navigation easier to follow.

Two bilingual essays completed the project context

Each of the two projects received a Chinese and an English essay:

• FreeModel Port: starting from the flawed abstraction of a “free model list,” it explains the trade-offs between public discovery, real requests, unified routing, and streaming fallback.
• OpenWorker Chinese site: showing that localization includes an independent update channel, not just translation, while documenting TurnEngine’s concurrent reads, serialized writes, and permission boundaries.

This week in one line: a personal site becomes more useful when ownership, entry points, limitations, and machine-readable interfaces are explained together. The more content it carries, the more deliberately its boundaries need to be written down.