KofTwentyTwo/AppKit
2
0 Fork 0
Code Issues 22 Pull Requests 4 Actions Packages Projects Releases 1 Wiki Activity

feat(template): provide repeatable new-repository setup #10

New Issue
Open
opened 2026-10-10 16:58:40 +00:00 by KofTwentyTwo · 5 comments
KofTwentyTwo commented 2026-10-10 16:58:40 +00:00 (Migrated from github.com)
Copy link
Copy source

Problem

Generating code cannot provision required GitHub controls. The current manual onboarding omits complete verified provisioning and references missing hooks.

Acceptance criteria

Provide documented, repeatable setup with preview/validation; create correct rulesets, security settings, check contexts and tag-only release environment; keep secrets out of files/logs; verify a disposable generated project end to end.

Scope

Starter onboarding tooling and docs.

This issue is part of the user-requested AppKit readiness remediation. Local work is not completion until the applicable published/runtime state and checks are verified. Substantial AI assistance: Codex.

## Problem Generating code cannot provision required GitHub controls. The current manual onboarding omits complete verified provisioning and references missing hooks. ## Acceptance criteria Provide documented, repeatable setup with preview/validation; create correct rulesets, security settings, check contexts and tag-only release environment; keep secrets out of files/logs; verify a disposable generated project end to end. ## Scope Starter onboarding tooling and docs. This issue is part of the user-requested AppKit readiness remediation. Local work is not completion until the applicable published/runtime state and checks are verified. Substantial AI assistance: Codex.
KofTwentyTwo commented 2026-10-10 19:55:56 +00:00 (Migrated from github.com)
Copy link
Copy source

Implemented and saved locally in starter commit 3dd5adf89d4f07cd40092151eef9cc44c5a0a969 on fix/template-onboarding. No push, repository creation, settings mutation, merge or publication has been performed.

  • Added offline preview, explicit apply and read-only validation for generated repository controls, with thirteen non-secret API requests.
  • Apply requires the current head of an open bootstrap PR and every required GitHub Actions check to succeed. Rulesets bind contexts to the observed Actions app; main has no bypass; release permits only v* tags. Existing conflicting rules/environment policies are preserved and rejected before writes.
  • Propagated the human-acknowledged current-commit review validator, locked JavaScript tools, lint/signature gates and CodeQL coverage to generated apps. Custom owner/reviewer substitution passes in both CLI variants.
  • Template packages exclude node_modules and worktree Git metadata. Added a complete owner bootstrap/runbook and threat-model boundaries.

Validation: 13 setup boundary tests plus four coverage tests pass; seven Node tests, PowerShell analysis, ESLint, workflow/security/documentation lint and all commit hooks pass. npm verified 83 signatures and 20 attestations. Packed template generation with owner Example produces correct setup/review identities; both CLI/no-CLI generated solutions pass locked restore and zero-warning build.

Remaining acceptance: authorized disposable live repository creation/push, hosted CI, real apply/readback and failing-PR enforcement; inventory/public template publication and human review acknowledgement. The issue remains open for that evidence. Substantial AI assistance: Codex (GPT-6).

Implemented and saved locally in starter commit `3dd5adf89d4f07cd40092151eef9cc44c5a0a969` on `fix/template-onboarding`. No push, repository creation, settings mutation, merge or publication has been performed. - Added offline preview, explicit apply and read-only validation for generated repository controls, with thirteen non-secret API requests. - Apply requires the current head of an open bootstrap PR and every required GitHub Actions check to succeed. Rulesets bind contexts to the observed Actions app; main has no bypass; release permits only v* tags. Existing conflicting rules/environment policies are preserved and rejected before writes. - Propagated the human-acknowledged current-commit review validator, locked JavaScript tools, lint/signature gates and CodeQL coverage to generated apps. Custom owner/reviewer substitution passes in both CLI variants. - Template packages exclude node_modules and worktree Git metadata. Added a complete owner bootstrap/runbook and threat-model boundaries. Validation: 13 setup boundary tests plus four coverage tests pass; seven Node tests, PowerShell analysis, ESLint, workflow/security/documentation lint and all commit hooks pass. npm verified 83 signatures and 20 attestations. Packed template generation with owner Example produces correct setup/review identities; both CLI/no-CLI generated solutions pass locked restore and zero-warning build. Remaining acceptance: authorized disposable live repository creation/push, hosted CI, real apply/readback and failing-PR enforcement; inventory/public template publication and human review acknowledgement. The issue remains open for that evidence. Substantial AI assistance: Codex (GPT-6).
KofTwentyTwo commented 2026-10-10 20:57:45 +00:00 (Migrated from github.com)
Copy link
Copy source

Locally signed starter commit 90af2f7 adds the real Windows installation/channel job to source and both generated workflow variants, and adds ci / installed-updates to the bootstrap module's required contexts and contributor checklist. The bootstrap must observe successful checks before applying protection; all 13 bootstrap tests and the complete 30-test tooling suite pass. No live repository settings were changed; the new context must actually run after the authorized rollout.

Locally signed starter commit `90af2f7` adds the real Windows installation/channel job to source and both generated workflow variants, and adds `ci / installed-updates` to the bootstrap module's required contexts and contributor checklist. The bootstrap must observe successful checks before applying protection; all 13 bootstrap tests and the complete 30-test tooling suite pass. No live repository settings were changed; the new context must actually run after the authorized rollout.
KofTwentyTwo commented 2026-10-10 23:14:28 +00:00 (Migrated from github.com)
Copy link
Copy source

Committed starter d8cea35cdf971ae327d69adc7ab222a1e7d891e3 (signed/DCO): the bootstrap plan now requires GitHub's actual standalone job names installed-updates, powershell and javascript; the template source additionally requires template. Generated apps omit that source-only packaging gate.

A new regression reads standalone job names from the actual ci.yml/scripts.yml workflows. It failed against the old plan (13 passed, one failed), then passed after correction. The source and both renamed, custom-owner variants generated from the real packed template each pass all 41 script tests. No manual synchronization of generated files. Source/generated workflow syntax and offline security, docs, Node seven-case review tests/ESLint and applicable commit hooks pass. Generated policies contain 16 actual contexts; source has 17.

Propagated AppKit's full-rule file-by-file analyzer workflow. Individual source/generated checks pass, but the pinned analyzer still occasionally crashes internally before emitting findings; file-by-file execution is not a proven complete cure. No rule/error suppression or retry wrapper is added. #26 remains open for that tool stability and license acceptance. Earlier complete installed runtime evidence covers unchanged UI/application code; this commit changes only administration/tests/docs and the analysis job.

Live disposable-repository setup and hosted starter gates still require public rollout/settings authorization. #10 remains open against that deployed acceptance requirement. Original sibling checkout is preserved; starter topic branch has no origin and has not been pushed.

Committed starter d8cea35cdf971ae327d69adc7ab222a1e7d891e3 (signed/DCO): the bootstrap plan now requires GitHub's actual standalone job names installed-updates, powershell and javascript; the template source additionally requires template. Generated apps omit that source-only packaging gate. A new regression reads standalone job names from the actual ci.yml/scripts.yml workflows. It failed against the old plan (13 passed, one failed), then passed after correction. The source and both renamed, custom-owner variants generated from the real packed template each pass all 41 script tests. No manual synchronization of generated files. Source/generated workflow syntax and offline security, docs, Node seven-case review tests/ESLint and applicable commit hooks pass. Generated policies contain 16 actual contexts; source has 17. Propagated AppKit's full-rule file-by-file analyzer workflow. Individual source/generated checks pass, but the pinned analyzer still occasionally crashes internally before emitting findings; file-by-file execution is not a proven complete cure. No rule/error suppression or retry wrapper is added. #26 remains open for that tool stability and license acceptance. Earlier complete installed runtime evidence covers unchanged UI/application code; this commit changes only administration/tests/docs and the analysis job. Live disposable-repository setup and hosted starter gates still require public rollout/settings authorization. #10 remains open against that deployed acceptance requirement. Original sibling checkout is preserved; starter topic branch has no origin and has not been pushed.
KofTwentyTwo commented 2026-10-10 23:46:50 +00:00 (Migrated from github.com)
Copy link
Copy source

Completed the focused onboarding fix in signed/DCO starter commit bb310f3208c9e4203ad42c007bf1671933a843be (local fix/template-onboarding; not published).

Apply and read-only Validate now resolve the official GitHub Actions app and require its ID on every required context. Missing/wrong bindings and another bootstrap producer fail before writes. The reviewed caller plan stays unchanged and reusable. Existing conflicting rules are preserved.

Evidence: retained RED reproduces wrong/missing bindings and input mutation (3 failures); full source and both actual packed/generated CLI and GUI-only variants each pass 54/54 Pester cases, zero failures/skips. Both changed PowerShell files pass the configured full analyzer rules; both docs pass Markdown lint; diff checks and signed-commit hooks pass. The generated-test processes ended exit 0. Official app lookup was read-only (github-actions, owner github, ID 15368).

This proves the local tool behavior, not a live repository bootstrap. No GitHub settings were changed and the starter has no public remote. Live apply/readback, whole-starter review, owner acknowledgement and publication remain outstanding. No release/signing claim or broad issue closure.

Completed the focused onboarding fix in signed/DCO starter commit bb310f3208c9e4203ad42c007bf1671933a843be (local fix/template-onboarding; not published). Apply and read-only Validate now resolve the official GitHub Actions app and require its ID on every required context. Missing/wrong bindings and another bootstrap producer fail before writes. The reviewed caller plan stays unchanged and reusable. Existing conflicting rules are preserved. Evidence: retained RED reproduces wrong/missing bindings and input mutation (3 failures); full source and both actual packed/generated CLI and GUI-only variants each pass 54/54 Pester cases, zero failures/skips. Both changed PowerShell files pass the configured full analyzer rules; both docs pass Markdown lint; diff checks and signed-commit hooks pass. The generated-test processes ended exit 0. Official app lookup was read-only (github-actions, owner github, ID 15368). This proves the local tool behavior, not a live repository bootstrap. No GitHub settings were changed and the starter has no public remote. Live apply/readback, whole-starter review, owner acknowledgement and publication remain outstanding. No release/signing claim or broad issue closure.
KofTwentyTwo commented 2026-10-11 00:06:05 +00:00 (Migrated from github.com)
Copy link
Copy source

New publication/setup evidence under the owner's explicit commit/push/configure authorization:

  • Created public KofTwentyTwo/windows-app-template, initial main bb310f3 and signed onboarding topic now 758e773. Draft PR #1: https://github.com/KofTwentyTwo/windows-app-template/pull/1.
  • Marked as a template; applied 13 restrictive repository/security/Actions/environment/ruleset requests. Official GitHub Actions producer IDs bind all 17 required contexts. Read-only Validate returned SettingsVerified=true; release allows only v* tags; NUGET_USER is set to KofTwentyTwo.
  • Hosted initial-main CI run 38096509791 passed build/core coverage, format, UI, actual template generation and installed stable/dev updates. PR fac10a7 CI 38096578936 also completed SUCCESS. Current 758e773 scripts run 38097053573 passes.
  • Live selected-actions policy initially rejected the two digest-pinned scanner containers. Fixed the plan/tests/guide in 758e773 and configured only the exact published Gitleaks/Trivy references. Source and generated Windows application each pass 55/55 script cases; changed files pass full analyzer rules, guide lint and signed hooks. Current security run 38097053934 and dispatch 38097129462 succeed, all three security jobs. Earlier startup failures retained; no policy broadening to arbitrary containers.

The required-check readback defect (#27) is implemented and published on starter main; its scoped acceptance is complete. Broader #10/#20 acceptance still includes owner review acknowledgement, remaining hosted bootstrap/negative-PR evidence, inventory and publication conditions. No merge, tag/release, NuGet template publication, signing proof or claim of full standards compliance.

The owner explicitly cleared the old all-AppKit-issues goal and set a new goal: build MarkdownViewr.Windows using AppKit. The new public GUI-only scaffold is at https://github.com/KofTwentyTwo/MarkdownViewr.Windows; its build has zero warnings, 20 core tests pass at 100% coverage and the feature plan is recorded. Its greeting remains scaffold content, not a finished Markdown viewer. Azure retries remain deferred.

New publication/setup evidence under the owner's explicit commit/push/configure authorization: - Created public KofTwentyTwo/windows-app-template, initial main bb310f3 and signed onboarding topic now 758e773. Draft PR #1: https://github.com/KofTwentyTwo/windows-app-template/pull/1. - Marked as a template; applied 13 restrictive repository/security/Actions/environment/ruleset requests. Official GitHub Actions producer IDs bind all 17 required contexts. Read-only Validate returned SettingsVerified=true; release allows only v* tags; NUGET_USER is set to KofTwentyTwo. - Hosted initial-main CI run 38096509791 passed build/core coverage, format, UI, actual template generation and installed stable/dev updates. PR fac10a7 CI 38096578936 also completed SUCCESS. Current 758e773 scripts run 38097053573 passes. - Live selected-actions policy initially rejected the two digest-pinned scanner containers. Fixed the plan/tests/guide in 758e773 and configured only the exact published Gitleaks/Trivy references. Source and generated Windows application each pass 55/55 script cases; changed files pass full analyzer rules, guide lint and signed hooks. Current security run 38097053934 and dispatch 38097129462 succeed, all three security jobs. Earlier startup failures retained; no policy broadening to arbitrary containers. The required-check readback defect (#27) is implemented and published on starter main; its scoped acceptance is complete. Broader #10/#20 acceptance still includes owner review acknowledgement, remaining hosted bootstrap/negative-PR evidence, inventory and publication conditions. No merge, tag/release, NuGet template publication, signing proof or claim of full standards compliance. The owner explicitly cleared the old all-AppKit-issues goal and set a new goal: build MarkdownViewr.Windows using AppKit. The new public GUI-only scaffold is at https://github.com/KofTwentyTwo/MarkdownViewr.Windows; its build has zero warnings, 20 core tests pass at 100% coverage and the feature plan is recorded. Its greeting remains scaffold content, not a finished Markdown viewer. Azure retries remain deferred.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
accessibility
Barrier affecting people with disabilities
 bug
Something isn't working
 deferred
Agreed follow-up, unscheduled
 dependencies
Pull requests that update a dependency file
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 needs-owner
Blocked on the owner
 priority
Work this first
 quality
Tests, gates, and code quality
 question
Further information is requested
 refactor
Internal restructuring, no behavior change
 release
Release and packaging
 wontfix
This will not be worked on
No labels enhancement quality
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/AppKit#10