0.83.0

Needs DirXMLDev 0.59.0.

Fixed

• A large project no longer runs the server out of memory on the schema and provisioning pages
  (#177). Each of their requests read and parsed the whole tree again, and a page sends several at
  once. They now read the tree the outline keeps, read again only when its files change.
• The warning that hosted.properties "is readable by other users" no longer shows on a folder
  that ignores chmod, such as a Windows folder mounted into the container, where its advice
  can't be followed (DirXMLDev 0.59.0).

Changed

• The server may use three quarters of the container's memory (-XX:MaxRAMPercentage=75); Java's
  default is a quarter. IDM_JAVA_OPTS in idmweb.env still overrides it (-Xmx4g). The first
  log line says how much it has (heap up to … MB), and the quickstart and hosted install say
  what to do when the log shows OutOfMemoryError.

0.82.0

Needs DirXMLDev 0.58.0.

Added

• Library objects that live in another Library of the vault (DirXMLDev #111) are marked
  read-only:

  • Outline and Developer view: a badge, with the Library's DN on hover.
  • The object's page: the source only. There's no Rename, Delete or structured editor, and a
    note says where the object lives.

  Links to it keep its DN, compare and deploy leave it alone, and the core refuses an edit to it.

Changed

• Pins DirXMLDev 0.58.0:
  • vault.deploy-schema --yes is behind the agent write gate;
  • the idm CLI in the image refuses arguments a command doesn't take, and a flag no longer
    takes the next word;
  • driver.query is gated, and driver.migrate --dry-run isn't.

0.81.0

Needs DirXMLDev 0.57.0.

Fixed

• Importing a Designer project that holds two objects of one name (a driver set using Libraries in
  two containers, or a package upgrade's leftover) no longer gives a project where nearly every
  page fails with duplicate artifact path (#174). The import keeps one, and the page now waits
  on the result, saying which one it kept and what was left out, until you open the workbench. The
  first commit's message records it too. A project imported before this loads again, and
  validation names the duplicate.

Changed

• "An internal error" says where the server log is (docker logs idmweb, or the terminal that
  runs the server); the quickstart's Day to day says so too.

0.80.0

Needs DirXMLDev 0.56.0.

Added

• The GCV tab on a driver set served by several servers (#134). Each server holds its own copy of a
  driver's GCVs, and the tab showed the primary's without saying so. Now:

  • the Value column is headed Value on (primary), and a note above the table names the
    servers that follow it;
  • each of the driver's own GCVs has a field per other server, outlined where that server holds a
    value of its own and not defined where its copy lacks the GCV. Typing sets that server's value
    (gcv.set --server, through the review); emptying it puts the primary's back;
  • a GCV only another server defines is listed, not defined on , with no delete button.

  GCVs from a resource or the driver set are the same on every server and have no server fields.

Changed

• README screenshots retaken on the current page, from one lab driver set; the GCV shot shows the per-server field.

DirXMLDevWeb 0.79.0

Needs DirXMLDev 0.55.0.

Added

• Compare projects: pairing on the page. Pair with … proposes the map (look-alike
  drivers, the nearest-named servers) or shows the pair's file, compares with it as you edit it,
  and lets you leave differences pending or accept them as known. Then it writes the map (as
  written), the first record and the known differences into a new branch, promote/<project>-pair-<time>,
  committed and pushed for review. GET /api/promote/map, POST /api/promote/pair,
  GET /api/promote/compare?map=.
• Known differences on the page: accept a difference as known (intended, or to decide later),
  or a known one as no longer known. The decisions go with the next promotion, or alone in a
  branch of their own (known, forget on POST /api/promote/apply).
• Cases move with their driver: when both projects have simulator cases, their files compare
  and promote as cases/<path>, with driver= written as this project names the driver.
• Agents: MCP compare_projects (each difference with its bucket and changed lines) and
  promote_changes (dry run by default; the branch otherwise). GET /api/promote/compare?brief=true,
  dryRun on POST /api/promote/apply.
• Docs: compare-projects.md (pairing, known differences, cases, agents, a first time
  through), agents.md (the two tools), the tutorial's next steps. git-workflow.md opens with the
  two ways to keep environments side by side, and when to choose which. features.md lists
  Compare projects.

DirXMLDevWeb 0.78.0

Needs DirXMLDev 0.54.0.

Added

• Compare projects (docs/compare-projects.md), for teams that
  keep a project per environment:
  • The comparison: this project and another, both read from their base branch as the
    repository has it, in this project's terms (the pair's map, promotions/<source>.properties).
  • The list: by driver, each difference sorted by the pair's promotion record into pending,
    both changed, this project's own, not paired yet, known and unchanged. Values that differ are
    listed apart and never make their file look changed.
  • The review: each file side by side, this project's against what promoting writes (the
    other project's logic with this project's values), merged line by line if you want.
  • Promote: the ticked files and values go into a new branch, promote/<source>-<time>,
    made from the base. The result is validated, committed as you with the promotion record and a
    Promoted-from: trailer, and pushed. The page then opens the branch, where the bar offers
    the pull request. A promotion that wouldn't validate, or that adds a file without its
    manifest, is refused before any branch is made.
  • The audit log records each one as promote.
  • API: GET /api/promote/projects, GET /api/promote/compare, POST /api/promote/apply.

DirXMLDevWeb 0.77.0

Needs DirXMLDev 0.52.0 (was 0.50.0).

Changed

• DirXMLDev 0.52.0 in the server and the image (the container's idm reports 0.52.0). It builds
  against trace-core 1.10.0, the version the image already carried since 0.76.0, and adds
  Vault.open over a caller's own connection for Directory Console. Nothing changes on the page or
  in the CLIs' behaviour.

DirXMLDevWeb 0.76.0

Needs DirXMLDev 0.50.0. Uses DirXML Trace Viewer's dirxml-trace-core 1.10.0 (was 1.8.0).

Fixed

• Live trace lines carry the vault's time. Each line of the Trace view is stamped with the time
  eDirectory reports for the event, not the time it reached the server, so it lines up with the
  engine's own trace files. With several servers, each line carries its own server's clock. A server
  that sends no time falls back to ours. (trace-core 1.10.0, from @klasen's PR there.)
• Server and driver names with escaped commas. A name such as cn=Smith\, John, or one with an
  escaped equals sign, plus sign or UTF-8 escape, showed wrongly in the trace's server and driver
  lists, and the check for which server a connection reaches could miss it. DNs are read the LDAP way
  now (trace-core 1.10.0).

DirXMLDevWeb 0.75.0

Needs DirXMLDev 0.50.0.

Changed

• The audit log is rotated by size (#161); a change in default behaviour. Before a line would
  take audit.log past audit.maxBytes (default 10MB), it moves to audit.log.1 and the older
  ones up by one; past audit.keep (default 10) the oldest is deleted, so the log takes at most
  about 110 MB. audit.keep=0 deletes nothing, audit.maxBytes=0 never rotates (the old
  behaviour). An existing audit.log larger than the limit is rotated on the first line after the
  upgrade; nothing is deleted then. The Audit view reads the files newest first, from their ends,
  and stops as soon as it has its lines, instead of reading the whole log for every request.
• Docs brought up to date.
  • pull-requests.md and multi-user.md are user references now, not design notes, each with its
    API fields.
  • data-model.md has people's own connections, Git and agent tokens, sessions, the overrides
    file's names, servers and jobs, and known differences.
  • design.md is marked historical (W7 built; rollback, secrets and driver deletion are on the
    page), and connections-ui.md says it is built.
  • limits.md gives the trace view's real buffer (50,000 records, 15,000 shown, adjustable), and
    development.md the release steps as they are.
  • hosted-install.md no longer describes Point Blue's own lab.

Fixed

• The Audit view's since compares times as times. Times are written with 3, 6 or 9 fraction
  digits, and compared as text a later line could sort before an earlier one and end the list too
  soon. A partly typed time (2026-10-07, 2026-10-07T09:30) is the start of that period, in UTC.

Removed

• Design notes for features that are built: docs/architecture-view.md, docs/trace-viewer.md,
  docs/simple-install.md and docs/event-logger.md. What they describe is in features.md,
  quickstart.md and upgrading.md; the two event-logger steps still to build are issues #164 (the
  logger as a catalog package) and #165 (pbt-eventlog.js, capture samples at a stage). Git
  history keeps the notes.
• docs/hosted.md, the hosted-mode design note of 2026-10-05: its body described the design before it
  was built (one shared vault bind, compare-page pull requests, no merging on the page, decisions
  still open), and hosted-mode.md, hosted-install.md, security.md, multi-user.md,
  git-workflow.md and pull-requests.md cover what was built. Git history keeps it. The audit log's
  rotation, which it promised and which wasn't built, is issue #161.

DirXMLDevWeb 0.74.0

Needs DirXMLDev 0.50.0.

Changed

• Tutorial: do it again with an agent (docs/tutorial.md §9): make a token, connect Claude Code,
  run the setup prompt, then have the agent make the change on a branch, plan and deploy it with
  the environment's name typed by you, and find its lines in the audit log.

Fixed

• The agent tokens dialog wraps the token, the command and the setup prompt instead of cutting
  their long lines off.