Sign-off log gains the design-system rebuild, the scan work, signing from
mmd-fsn-01 and the Intune publish, then the three defects Ben found by looking
at the running application and what was done about each.
Backlog: PDF-07, PDF-08 and PDF-09 go green (built, run and looked at on the
test machine at 800x600), PDF-17 and PDF-18 go green (signed, published), and
PDF-14 goes amber with the reason stated plainly - the copier conversation and
the dialog are proven, the page transfer has never met real hardware.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Three things Ben saw on the running application that all read as "this is still
the tool it was forked from".
1. The upstream 50-page manual was sitting in the repository root as MmdPdf.pdf,
so it was the document on screen whenever it was opened or restored from the
last session - a full-page green upstream logo on black. It was never shipped
in the payload, but it was there to be opened, which is the same thing to
whoever is looking at the screen. Removed, and added to .gitignore so it does
not come back with a source drop. With no document, the application opens on
its own empty view.
2. Scan was in the title bar beside minimise, maximise and close. That is window
chrome, not a tool. It is a toolbar button now, next to Print in the file
group, with a caption in every label mode like every other tool. The band
button style it used has no other user and is gone with it.
3. The footer read v1.7.5, which is the upstream project's version. MMD PDF is
2026.8.1. Not 1.0: the pilot machines already carry a build numbered 1.7.5,
and an upgrade has to sort above what it replaces or Intune would read it as
a downgrade. The Intune detection rule moves with it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kua-agentandClaude Opus 5