docs-drift: ditc@3.3.0 #20
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Drift report: ditc 3.3.0 → 3.3.0
Added commands
session— Sign in with your work account and manage the session (federated login).loginstarts a device-code sign-in against a tenant;showreports who is signed in and until when;logoutrevokes and clears — pages: src/ditc/215-session-signin.md, src/ditc/230-assistant-learns.mdsession login— Sign in to a tenant with your work account (browser-first). Fetches the tenant's discovery document, then signs in with the flow the environment supports: the PKCE loopback browser flow opens the browser (single click, zero typed codes) when a local browser is plausible; the RFC 8628 device flow covers headless and SSH seats — it prints the sign-in URL and code, and the code completes on any device. Under--jsononependingenvelope line prints as soon as the chosen flow's sign-in reference exists, then the final line — pages: src/ditc/215-session-signin.md, src/ditc/230-assistant-learns.mdsession show— Report the current session for a tenant: identity, email, expiry, and which store holds the material. Reads the[session]config table only — never the credential store, never material — pages: src/ditc/215-session-signin.md, src/ditc/230-assistant-learns.mdsession logout— Revoke the session at the tenant's secret store and delete the local material (both store keys and the[session]config table). Idempotent: with nothing held, reportsnothing-to-doand exits 0 — pages: src/ditc/215-session-signin.md, src/ditc/230-assistant-learns.mdmcp— Serve ditc's verbs as MCP tools over stdio for a local agent harness; guidance rides the same connection as prompts and resources. Exempt from the first-run refusal; the auto-update check still runs first — pages: src/ditc/930-assistant-connection.mdRemoved commands
tenant onboard— Install per-tenant credentials from an onboarding bundle — pages: src/ditc/220-pick-tenant.mdskills— Manage agent skills: converge embedded SKILL.md files into detected harnesses — pages: noneskills converge— Converge embedded skills into detected harnesses: install missing copies, refresh drifted ones, and clean stale files (canon 4.0.0 — the formerexportand driftcheckfold into one idempotent verb) — pages: noneThis ticket's drift was already repaired on main before an author dispatch could be justified — evidence, checked against the shipped surface today:
session/session login/session show/session logout— documented on src/ditc/215-session-signin.md (merged in #16, full-surface re-verified through #18).mcp— src/ditc/930-assistant-connection.md coversditc mcp(merged #18).tenant onboard(removed) — no ditc page teaches the removed command; the retired-flow remediation appears on 220-pick-tenant.md.skills/skills converge(removed, pages: none) — no page coversditc skills; exempt from narrative coverage.state/state list/worktree/worktree list(dito-adjacent listings in the #20 report header aside, pages: none) — exempt via site.yaml coverage.exempt_groups.Every covering ditc page carries
verified: ditc@3.5.0(the surface that includes all of the above; #22), and the ditc gate is enforcing and green today:check-lockstep.py --manual ditc --synthesize→ 0 fail, 0 warn.Dispatching a re-authoring pass against a 3.3.0 contract would regress
verifiedbelow the already-covered surface and re-edit proven-green pages for no drift. Closing as already-covered; no dispatch was run for this ticket. The stale re-file traces to the drift job filing against an old release boundary — if these recur, the filer's previous-release resolution needs a look (drift-ticket dedup only checks OPEN issues by exact title).