docs-drift: dito@6.1.2-rc.3 #28
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: dito 6.1.0 → 6.1.2-rc.3
Added commands
operator list— List the operator roster from the master tenant's identity provider (read-only: username, email, operator groups, last sign-in) — pages: src/dito/420-operators.mdoperator show— Show one operator identity and their master-IdP groups (read-only) — pages: src/dito/420-operators.mduser list— List the tenant's ditc identities from its identity provider (read-only: username, email, groups, sign-in source, last sign-in, forge seat presence) — pages: src/dito/430-users.mduser show— Show one ditc identity: groups, seat state, app access, and the apps whose manifests declare them owner (read-only) — pages: src/dito/430-users.mdmsp— The managed service provider: show (the msp declaration of record — identity, master tenant, operator services, role bindings) — pages: src/dito/460-msp-declaration.mdmsp show— Show the MSP declaration of record: identity, master tenant, operator services, the dashboard entry, the role bindings, and the known sibling MSPs (read-only, from the infra flake's mspInventory) — pages: src/dito/460-msp-declaration.mdAuthor dispatch complete: no new dispatch — duplicate re-fire.
This ticket's body is byte-identical to #26 (docs-drift: dito@6.1.2-rc.3), whose repair merged as PR #27 (commits
4e24c1e,8237dd7,56efadf— verified ancestors of main). #26 was closed 2026-10-08T14:08:50Z, one minute after the merge; the 2026-10-09 nightly re-filed the identical report because the drift baseline (the two most-recentcaptures/ditocommits,7489311vs6cb7f68, dito 6.1.0 → 6.1.2-rc.3) has not moved.Coverage re-verified against the six change-list lines:
operator list/operator show— src/dito/420-operators.md, "See who operates the platform" (verified: dito@6.1.2)user list/user show— src/dito/430-users.md, "See who holds a seat" (verified: dito@6.1.2)msp/msp show— src/dito/460-msp-declaration.md (verified: dito@6.1.2)tools/check-lockstep.py --manual dito --synthesize: 0 fail.tools/check-coverage.py: dito 13 groups covered.Not dispatched: a fresh author pass would re-edit already-repaired pages and die at the dispatcher's first acceptance gate regardless —
tools/build-docs.pyis red at main (src/ditc/940-walkthrough.md introduces 'walkthrough', absent from the ditc glossary), and the contract'sverified: dito@6.1.2-rc.3stamp violates the FRESHNESS format rule (<tool>@<major>.<minor>.<patch>).Known consequence: with the captures baseline unmoved, the next nightly (04:37 UTC) re-fires this ticket. The re-fire loop needs either a closed-aware dedup in tools/file-drift-ticket.py (skip when a closed same-title ticket carries the dispatch-complete marker) or a dito captures refresh. Escalated to the Operator.