docs: record Windows viewer bootstrap and repository identity

Preserve the generated repository name in setup examples and record actual foundation validation, hosted run IDs and remaining viewer/release requirements.

Refs: #1

Co-Authored-By: Codex (GPT-6) <noreply@openai.com>
Signed-off-by: James Maes <jmaes@dmdbrands.com>
This commit is contained in:
James MaesandCodex committed 2026-10-10 19:06:41 -05:00
1 parent ea234917fa
commit 85004f1d1f
2 files changed
+30 -1

No files matched your search

+29
View File
@@ -2,6 +2,35 @@
Updated: 2026-10-10
## Published scaffold checkpoint
Public repository: [MarkdownViewr.Windows](https://github.com/KofTwentyTwo/MarkdownViewr.Windows).
Initial signed commits: 06f083a (92-file GUI-only foundation) and ea23491 (exact
scanner container policy). Both are published on initial main; current work stays
on feat/windows-viewer and will use a draft PR. Implementation tracked by issue #1.
All 13 restrictive setup requests were applied. Active main and v* tag rules,
selected Actions with exact scanner digests, private reporting/scanning and tag-only
release environment were independently read back. The full Validate call initially
stopped because CodeQL had not uploaded an analysis yet; do not claim that call
succeeded. Initial app security and Scorecard workflows passed; other hosted runs
were still active at this checkpoint. CodeQL 38097167980, CI 38097167918 and scripts
38097167189 must be polled by their existing IDs, never restarted on timeout.
Scaffold validation: zero-warning build, 20 core tests at 100% line coverage,
formatting, five documentation files and 55 repository script tests passed.
Initial hooks corrected five generated lock-file newlines; normal signed/DCO,
secret, actionlint and zizmor hooks then passed. No new local GUI tests.
Starter configuration correction at 758e773 is pushed in draft PR #1. Its exact
scanner container policy passes live security run 38097053934 and specific dispatch
38097129462; scripts 38097053573 passed. Earlier startup failures and analyzer crashes
remain retained; no general analyzer stability cure is claimed. Existing AppKit and
standards drafts remain unmerged. Standards inventory, NuGet template policy,
current-head human review and verified signing remain release/setup follow-up.
Azure retries stay deferred. Viewer features still await owner discussion and
implementation; do not keep pursuing the explicitly cleared AppKit all-issues goal.
Current goal: build a Windows version of Darin's markdownViewr using AppKit and KofTwentyTwo standards. The previous AppKit all-issues goal was explicitly cleared.
Owner chose MarkdownViewr / MarkdownViewr.Windows / markdownviewr-windows. Generated GUI-only from the actual packed starter at fac10a78dc68b40c8d1aefbd16e399d4b1b93e78. Published AppKit 0.1.0 is used; unpublished 0.2.0 APIs are not substituted. Fresh initial restore created NuGet locks. Solution build: zero warnings/errors. Existing core: 20/20 tests, zero skipped; 100% line coverage. No GUI input tests were run for this new application.
+1 -1
View File
@@ -9,7 +9,7 @@ hooks, and run [CONTRIBUTING.md](../CONTRIBUTING.md)'s checks. Node 24 and Power
The default command works offline and writes thirteen non-secret API requests:
```powershell
./build/Initialize-GitHubRepository.ps1 -Repository KofTwentyTwo/windows-app-template
./build/Initialize-GitHubRepository.ps1 -Repository KofTwentyTwo/MarkdownViewr.Windows
Get-Content artifacts/repository-setup.json
```