docs: ditc 3.3.0 lockstep wave — full-surface verification (session/mcp restored) #18

Merged
jsutter merged 7 commits from docs/ditc-3.3.0-lockstep into main 2026-09-23 15:15:47 +00:00
Owner

Resolves the 7 promotion-gate findings that blocked the ditc v3.3.0 release, against the RESTORED post-integration surface (dit-client main 4308bc6: session + mcp back, skills correctly absent).

  • All 18 ditc pages re-stamped verified: ditc@3.3.0 against regenerated captures (annotation-level delta vs the 3.2.1-wave captures)
  • 210-install-onboard re-authored onto ditc session login (it still taught the retired onboarding-bundle flow — pre-existing drift the gate would have caught); public deck htdocs/ditc-onboarding.html fixed (3 slides)
  • docs-manifest.json root-cause fix: the 2.4.4-era manifest was why the gate saw stale stamps
  • captures/ditc regenerated (35 paths), htdocs regenerated (74), provenance.json current

Gates (local, CI invocations): promotion-gate OK (10 groups, gate enforce); coverage OK (ditc 8, dito 12, scribe 7, 71 covers); prose clean; lockstep ditc 0 fail 0 warn gate enforce; link-check OK.

Flagged follow-up (out of scope): the dito manual still teaches ditc tenant onboard --bundle — a dito-manual wave.

Resolves the 7 promotion-gate findings that blocked the ditc v3.3.0 release, against the RESTORED post-integration surface (dit-client main 4308bc6: session + mcp back, skills correctly absent). - All 18 ditc pages re-stamped verified: ditc@3.3.0 against regenerated captures (annotation-level delta vs the 3.2.1-wave captures) - 210-install-onboard re-authored onto `ditc session login` (it still taught the retired onboarding-bundle flow — pre-existing drift the gate would have caught); public deck htdocs/ditc-onboarding.html fixed (3 slides) - docs-manifest.json root-cause fix: the 2.4.4-era manifest was why the gate saw stale stamps - captures/ditc regenerated (35 paths), htdocs regenerated (74), provenance.json current Gates (local, CI invocations): promotion-gate OK (10 groups, gate enforce); coverage OK (ditc 8, dito 12, scribe 7, 71 covers); prose clean; lockstep ditc 0 fail 0 warn gate enforce; link-check OK. Flagged follow-up (out of scope): the dito manual still teaches `ditc tenant onboard --bundle` — a dito-manual wave.
Captured from the v3.3.0 tag build (dit-client 95a64bc). The 3.2.1-wave
captures carried the release-line surface (session, mcp); v3.3.0 is cut
from main, which declares skills and neither session nor mcp. The stale
skills captures (2.4.4 headers, content identical to the 3.3.0 binary)
re-stamp to 3.3.0.

Assisted-by: worker:synthetic/hf:zai-org/GLM-5.3-Flash
The v3.3.0 surface (cut from main) declares neither a session nor an mcp
group — both shipped only on the 3.2.1 release line. The two pages taught
commands the promoted binary does not have; the lockstep-reverse coverage
gate fails a covers: entry naming a group the tool lacks. Retirement
cascades: drop the requires edges (pick-tenant, structured-path), the
session and assistant-connection glossary terms, and the connection-model
phrase on structured-path; pick-tenant and structured-path re-stamp to
ditc@3.3.0 after content verification against the regenerated captures.

Assisted-by: worker:synthetic/hf:zai-org/GLM-5.3-Flash
The page rode the sign-in-registers-a-connection story; 3.3.0 carries
ditc skills converge instead (install, refresh, clean — the canonical
skills.md). The page reverts to its pre-3.2.1-wave skills form, updated
for the startup drift notice, takes covers: [ditc skills] — the group
the promotion gate found uncovered — and stamps ditc@3.3.0.
install-onboard drops the install-time claim the converge model does
not support and re-stamps.

Assisted-by: worker:synthetic/hf:zai-org/GLM-5.3-Flash
The 3.2.1→3.3.0 capture delta for these groups is annotation-only
(spec-reference tags added to help text; no command or flag changed),
so the pages' content carries over and the stamps move to ditc@3.3.0.
This resolves the promotion gate's tenant/app/secret/service/
self-update/feedback findings.

Assisted-by: worker:synthetic/hf:zai-org/GLM-5.3-Flash
The committed docs-manifest the stable-promotion gate reads was
2.4.4-era — the root cause of the v3.3.0 gate failure (the 3.2.1 wave
re-stamped src but never regenerated the manifest). This regen carries
the 3.3.0 stamps, the retired pages' removal, and the skills coverage.

Assisted-by: worker:synthetic/hf:zai-org/GLM-5.3-Flash
The v3.3.0 tag moved to 4308bc6 (merge: release/ditc-v3.2.0 into main —
restore the full shipped surface), so the retirement wave built against the
pre-integration cut no longer describes the promoted tool. Un-retire:

- restore 215-session-signin and 930-assistant-connection from main;
- re-cascade what the retirement dropped: the session-signin requires edges
  (pick-tenant, structured-path), the session and assistant-connection
  glossary terms, the 920 connection-model phrase, and 230-assistant-learns
  back onto the sign-in model;
- re-capture the ditc surface from the restored binary (session and mcp
  return, skills leaves — it never shipped on the release line; tenant
  onboard stays gone, the bundle flow retired before 3.2.1 — main's
  tenant--onboard.txt was 2.4.4-stale for a hidden subcommand the walk
  cannot see). Every capture body is content-identical to the 3.2.1-wave
  captures; only the version headers move to 3.3.0;
- re-author 210-install-onboard's onboarding procedure onto the session
  sign-in: its bundle flow taught `ditc tenant onboard`, which the
  restored binary rejects — pre-existing drift the stamp bump would have
  sealed in. The public onboarding deck moves with it;
- re-stamp all 18 ditc pages verified: ditc@3.3.0 against the regenerated
  captures.

Assisted-by: worker:synthetic/hf:zai-org/GLM-5.3-Flash
The regen restores the session and mcp reference pages, drops the skills
reference pages, and re-renders the manual with the restored pages, the
210 onboarding re-author, and the ditc@3.3.0 stamps. docs-manifest.json
and provenance.json follow.

Assisted-by: worker:synthetic/hf:zai-org/GLM-5.3-Flash
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
deepnet/ditdocs!18
No description provided.