Clarify human-paced deposits and MCP independence

[Wonderforge-Lab]

A contributor handle and human approval do not by themselves prevent overlapping writes. The operating instructions need to say who may deposit, when the turn ends, and what counts as a completed deposit.

This patch documents one active deposit at a time per live workspace while allowing parallel reading and preparation. It distinguishes session identity from write authorization and a writing turn, requires verification at the intended local/GitHub destination, and preserves failed or uncertain work for human-directed recovery.

Changes:

• Update the README, AI entrypoint, visitor checklist, routine deposit quickstart and first-use quickstart, with matching Simplified Chinese changes.
• State that simultaneous deposits, including agent swarms, are unsupported and that humans sharing a workspace coordinate turns across sessions, tools and publishing copies.
• Make completion cover artifacts, required JSON records and regenerated views; report publication, checks and missing/unverified work accurately.
• Require checking what landed before an authorized retry, without blind replay, overwriting conflicting work or force-push recovery.
• Clarify that LabNote neither includes nor requires an MCP server; an assistant may still use an external MCP connector to access files or GitHub.
• Align the existing routine relay step with the entrypoint's content-plane boundary: use messages/notifications rather than editing the lobby noticeboard.

This is an operating-rule and documentation patch. It adds no technical lock, queue, dependencies, schema changes or mandatory branch workflow for routine deposits. Canonical maintenance created no runtime records.

Validation:

• GitHub Registry validation: PR run and branch push run both passed.
• Registry validation and validator smoke tests: pass (16 invalid invariants).
• Generated-view checks and smoke test: pass.
• Markdown links: pass.
• Locale invariants: pass (21 mapped surfaces).
• Locale freshness and regressions: pass (48 paired surfaces).
• Bridge configuration, tag-promotion tests and change-set guard: pass.
• Git whitespace check: pass.
• Published tree matches the locally checked tree: b7e5c603c033b97530b3950bcef3c66c2cfe27a0.

Paired English/zh-CN text review:

Scenario	Documented outcome
One authorized deposit	Verify the whole bundle at its intended destination, report completion, then end the turn.
Two agents with distinct handles	Handles identify contributors; the human must still assign separate writing turns.
Several humans/tools sharing a workspace	Coordinate turns across all writers and copies publishing to it.
Local-only workspace	Verify local files and required views; no remote push is required.
Both local and GitHub requested	Verify and report each destination separately.
Rejected or partial publication	Preserve work, report confirmed and missing items, and stop for human direction.
Uncertain publication	Inspect the destination before retrying; do not replay or declare success blindly.
Assistant uses MCP	External access remains usable; LabNote does not supply or require an MCP server.

The scenario review is a static review of the paired instructions, not a fresh-agent behavioural test. Merge remains subject to maintainer review.