Repository navigation
Description
Owner-reported operating context — 12 November 2026 (Asia/Bangkok)
Ash reports that protected files and branch protection have been removed, main is now the default branch, and work is taking place directly on main. These are owner-reported changes, not independently verified repository or settings evidence. The exact removed-file inventory remains unspecified.
The earlier instruction below not to edit main directly conflicts with the reported operating mode. Record the conflict without treating either source as authorisation for repository operations. October inventories and guard/list observations remain historical evidence, not a current-file inventory. Preserve the direct .github/ configuration scope, dependency-updater continuity supplement, TOA-454 coordination, npm boundary and independent approval controls.
This notice leaves the original description below, acceptance criteria, checklist states and all native properties unchanged. It authorises no repository operations, direct commits, settings changes, implementation, reopening, closure or acceptance. Independent approval requirements remain applicable.
Proposed direct-main decision — not adopted
Scope: lightspeedwp/ThisOneTimeOnAcidCom only.
- Record direct-on-
mainas Ash’s stated working practice. Do not treat it as blanket authorisation for automated or delegated implementation. - For Ash’s own work, propose superseding the previously recorded “Do not edit
maindirectly” restriction. Retain that instruction as historical evidence. - For future separately authorised implementation, explicitly establish whether direct-on-
mainwork is permitted. Without that permission, do not infer it from the default branch, removed protection or Ash’s practice. - Where repository instructions still prohibit direct edits, pause the affected operation until the conflict is resolved. This proposal neither changes nor overrides those sources.
- Preserve independent approvals for scope, file changes, settings, automated writes, spending, merging and deployment.
- Optional branches and pull requests remain available. Their naming-validation scope is a separate, currently unadopted proposal.
- No restoration of guards or branch protection is implied.
Decision status: proposal only; not adopted. Saving this text would record the proposal, not supersede repository instructions, grant direct-main implementation permission or authorise repository changes. Current repository instructions have not been independently verified for this proposal.
Supporting audit reference
README audit and Spec Kit review — ThisOneTimeOnAcidCom — historical README audit and bounded Spec Kit findings. Human acceptance remains pending. This reference does not expand this issue’s scope or authorise implementation.
Dependency-updater disposition and continuity evidence — 11 November 2026
This evidence supplements the direct-file manifest assessment. Earlier inventories below remain historical; their inclusion of Dependabot configuration does not describe the inspected main revision.
At book main revision f6a83750306b36eef3b9199bcb8299579c826042, Renovate configuration exists and Dependabot configuration is absent. Inspected develop revision e971ff39daf71c25224d2746d71817349dd0dfe2 retains Dependabot configuration and has no Renovate configuration. Do not describe the migration as applied to both branches.
The local configuration references github>lightspeedwp/.github:renovate. Its named preset source was absent from the inspected shared-repository revision. Runtime resolution was not observed; this is a source discrepancy, not a verified updater outage.
Enrolment, effective inherited policy and successful replacement operation remain unverified. No Renovate-authored update PR surfaced in the bounded searches; this does not prove the App is uninstalled.
Scope coordination — 11 November 2026
This issue owns direct-configuration disposition: purpose, consumer, preset reference, dependencies and maintenance responsibility. Its enrolment, policy, operational-evidence and recovery checklist items below require recording the relevant findings or explicit evidence gaps—not independently performing activation or operational acceptance.
TOA-454 owns residual Renovate implementation verification and whole-updater operational acceptance. Reuse its evidence here rather than duplicate that work. Any local configuration correction still requires an exact approved change; workflow changes, shared-preset publication, App activation, permissions and root/npm work remain outside this issue’s implementation scope.
This clarification introduces no blocking dependency, native relationship, ownership change or new approval authority.
Proposed direct-configuration acceptance clarification, pending approval:
- Record the updater configuration’s disposition, actual consumer, preset source and maintenance responsibility.
- Evidence enrolment and effective npm/Actions update policy, including target branch, schedules, grouping, cooldowns and security-update behaviour.
- Record operational evidence or explicitly retain continuity as unverified.
- Identify coherent recovery requirements without assuming configuration deletion disables GitHub security alerts.
Workflow consumers introduce coordination gaps: dependency validation filters main/master and routes Renovate through self-hosted ephemeral runners, while the updater guide describes a develop target. The inspected managed auto-merge workflow excludes public repositories; it is not operational acceptance evidence for this public repository.
These observations do not expand this issue into workflow implementation, shared-preset publication, App activation, permissions changes or root/npm tooling. Preserve existing guard-removal direction and independent approval controls. No commands, tests or operational changes were performed.
Current delivery and branch audit — 24 October 2026
This current snapshot supersedes conflicting earlier branch instructions and implementation-status claims below. Earlier dated notes remain historical evidence, not current acceptance. No status, hierarchy, native PR association or repository change is proposed by this description patch.
- Outcome: Approve the direct-.github manifest and verify actual consumers/maintenance.
- Recorded status: In Progress. Accepted whole-child completion is not established.
- Verified implementation position: CODEOWNERS and protection guide exist. Current direct files include BUDGET_CONTROLS.md, GOVERNANCE.md, PROTECTED_FILES.txt, VALIDATION.md and dependabot.yml; .github/README.md is absent but docs/GITHUB_DIRECTORY.md exists. Older local-template docs: repository - Add agent and contributor guidance #2 wording conflicts with ci: repo-governance - Configure shared PR template reuse #248 shared-only clarification; current local PR templates are absent.
- Outstanding acceptance: Approve reuse/adapt/omit/defer for exact direct files, resolve template-policy wording and owner identity; distinguish declarations from effective protection.
Branch instructions
Assessment: 11 November 2026. Replace the October branch/file-plan recommendation only; preserve governance approvals, subsequent guard-removal direction and all unrelated content.
- Repository:
lightspeedwp/ThisOneTimeOnAcidCom. - Implementing target: this existing issue; GitHub counterpart #257 independently checked. Scope is direct configuration disposition and consumers—not workflows or root/npm tooling.
- Parent context: coordination only; no parent implementation branch.
- Allowed closing targets: none certified.
- Branch state: unresolved; no existing branch recommended for reuse.
- Branch: exact recommendation withheld pending contribution classification and template-routing resolution.
- Base:
main, confirmed by current primary instructions atff9b152f6b57dadb08d672acac9f1690d59988d4; refresh before authorised operations. Do not editmaindirectly. - Naming policy: the same repository, contributor, validator and organisation sources cited in the current CI assessment were inspected.
build/is a candidate for configuration implementation; a documentation-only manifest contribution requires separate classification. No validator was executed. - PR template: unresolved. The local router maps
build/to Chore; the shared routing map selects CI. Do not silently choose or copy templates locally. - PR scope: one approved direct-file manifest and bounded consumer corrections. Keep workflow changes, shared-preset publication, App activation and root tooling separate.
- Constraints: preserve valid approvals and the direction not to restore removed guards. No settings, permissions, bot activation, branch operations, repository changes, merge or closure authorised.
- Unresolved: residual branch guidance, template routing, dispositions, ownership, preset resolution and operational continuity.
Expected file changes
Plan status: provisional; paths inspected at ff9b152f6b57dadb08d672acac9f1690d59988d4.
| Operation | Path | Intended change | Approval/dependency |
|---|---|---|---|
| Edit | Directory guide | Record approved dispositions, consumers and maintenance boundaries. | Approved manifest and documentation placement. |
| Edit | Renovate configuration | Conditional correction of its reference or local policy after source/ownership resolution. | Verified source and exact protected-configuration approval; no shared publication. |
- Out of scope: workflows, folder migrations, shared preset creation, activation and root/package changes.
- Remaining discovery: approved dispositions and operational consumer evidence. Ownership/governance edits are not prescribed merely because files exist.
- Scope-change gate: revised approval before materially different files or operations.
Evidence and handoff packet
- Recipient/request: Ash; description preview only.
- Selected record: this issue; preserve the saved continuity supplement, npm boundary and guard-removal direction.
- Criteria: approved direct-file dispositions with purpose, consumer, dependencies and maintenance evidence.
- Sources: current primary instructions, local/shared routing, directory guide, Renovate configuration and shared root at
b63f9bbb0c186f68b0a1cf6cad1b30c89be38f5c. - Branch/PR evidence: historical merged work and current open PRs do not establish suitable reuse or whole-issue acceptance.
- Associations: counterpart checked; no new relationship or closing target.
- Approval: unsaved preview; approved persistence may sync to docs: repo-governance - Record direct GitHub configuration manifest #257. Fresh baseline/read-back required; no duplicate GitHub write or implementation authorised.
Create a single approved manifest for files directly inside .github/, drawing from the shared repository only where applicable.
Package-manager scope boundary
PKG-001 is decided: npm-only. #258 owns remaining package-manager reconciliation: pnpm artefact and override review, npm lockfile alignment, hooks and documentation, actual deployment configuration, and installation/test/deployment verification. Do not duplicate that implementation in this .github/ root-file issue.
Use the agreed npm policy when documenting consumers of direct .github/ files. Existing progress notes report Node 24 and Jest/SWC changes merged; this note does not claim remaining cleanup or verification is complete. Existing scope, acceptance criteria, status and ownership are unchanged.
Approved governance decisions — 17 October 2026
Owner approved all nine governance decisions. Governance decisions document.
- Fix invalid package name in package.json causing Netlify deploy error #1: DECIDED — Enable GitHub Discussions with templates.
- docs: repository - Add agent and contributor guidance #2: DECIDED — Keep local PR templates for workflow-specific routing needs.
- bug: netlify - Fix unreadable redirects output and validate routing #3: DECIDED — Enable CODEOWNERS and branch protection.
CODEOWNERS and setup guidance have merged; template-policy reconciliation, direct-file acceptance and applied protection verification remain outstanding. The approved decisions supersede conflicting template/discussion proposals below, without expanding folder implementation boundaries. Explicit shared references: issue templates and pull request templates. Review these references when tailoring local configuration; retain approved workflow-specific PR routing. Changes to locked shared templates require human review, not routine agent edits. Link implementation PRs to their respective decision issues.
Acceptance criteria
Layout proposal — .github/ root configuration
This issue owns one grouped manifest for files directly inside .github/; it does not implement folder migrations, workflow changes or repository-root tooling. The broader layout proposal is recorded on the parent epic. Decisions below are proposals, not completion claims.
Add
- Propose
.github/README.mddocumenting the directory map, inherited community resources, generated artefacts and maintenance boundaries. - Maintain an allowlist for other direct
.github/files. Each selected file must have a purpose, actual consumer, dependencies and maintenance owner direction; classify reference files as reuse, adapt, omit or defer.
Keep and adapt
- Preserve the two centrally managed dependency workflows; workflow implementation belongs to the workflow workstream.
- Keep executable scripts at root, with managed Spec Kit/Gemini tooling in
.specify/and.gemini/. - Respect target-repository instructions before applying conventions from the shared repository.
Omit or defer
- Do not copy labels, issue types, routing, merge automation or other organisation-level configuration blindly.
- Omit
.github/scripts/and unrelated shared metrics, phase orchestration, Qodo and control-plane machinery unless separately justified. - Use the shared issue and PR template directories linked above as explicit references. docs: repository - Add agent and contributor guidance #2 approves retaining local PR templates for workflow-specific routing; local issue-template configuration still requires care because it can suppress inherited templates.
- Fix invalid package name in package.json causing Netlify deploy error #1 approves GitHub Discussions with templates, superseding the earlier deferral. Reference shared saved replies instead of assuming native synchronisation.
Folder and root-file boundaries
- Folder-owned work covers
.github/specs/, workflows, community templates, and conditional migrations of plan/reports/prompts/tasks. Amend repository guidance and references before migration. Do not create these folders as part of this root-file issue. .github/tests/is conditional tooling support only; Jest tests remain colocated in__tests__/beside the code they cover.- Repository-root configuration is owned by the separate grouped issue: VERSION, Jest, ESLint, Babel, ignore files, EditorConfig, Git attributes, npm/Node, Prettier, Markdownlint and CodeRabbit. Do not duplicate implementation here.
Verification
Record keep/move/add/omit decisions in the manifest; validate selected direct-file consumers and document exclusions. Final implementation depends on the approved directory map and relevant tooling decisions.
References: target instructions, shared placement policy.
- Every reference file is classified as reuse, adapt, omit or defer
- Selected files have a purpose, consumer and maintenance owner direction
- Organisation-wide routing, labels and automation assumptions are not copied blindly
- Folder-owned files are excluded from this issue’s implementation scope
- Selected configuration validates without changing shared locked files
Target: book .github directory. Reference: shared .github directory.
Source-note references and scope
Owner direction — 25 October 2026: remove the repository locked/protected-file guard workflows and .github/PROTECTED_FILES.txt; do not restore them. At develop revision 6fa38aaa02e70650190f5b2e95d0991acbb694c8, .github/workflows/locked-files-guard.yml and .github/workflows/protected-files-guard.yml are absent, but .github/PROTECTED_FILES.txt and scripts/validation/check-locked-file-approval.cjs remain. The list-removal statement therefore conflicts with this revision; record the direction without claiming that deletion is present on develop. Removing those artefacts does not waive independent owner instructions, shared locked-file review, content safeguards, workflow ownership or separately required approvals.
Historical reference, omitted by owner direction: locked-files-guard.yml. Evaluation reference: ruleset-drift.yml.
Assess surviving policy, residual list consumers and applicable branch-protection declarations without reopening the guard-removal direction. Approved CODEOWNERS/branch-protection decisions do not establish that enforcement is implemented or tested. This issue remains a direct .github/ file-manifest workstream; it does not gain workflow implementation ownership. Any drift-workflow proposal remains a separate implementation decision; do not propose guard restoration. Locked shared files, protection settings and credentials require their specific human approval.
Current implementation and remaining acceptance — 19 October 2026
Reviewed against develop revision 4ecdb26d9655a48bf000a7c89da2f70383edce87. No tests, interface submissions, settings changes or metadata mutations were performed during this review. Merged changes are partial evidence, not automatic completion.
Delivered: #307 added CODEOWNERS; #301 contributed protection setup/inventory. The direct-file directory guide and complete disposition manifest remain outstanding.
Unmerged evidence: draft PR #346 revises ownership/guard material; that does not assign workflow implementation to this issue.
Remaining acceptance: approve reuse/adapt/omit/defer entries with consumers, dependencies and maintenance direction; verify owners/applied protection; reconcile template policy.
Boundary: npm implementation remains with root configuration; do not duplicate it here.
Metadata
Metadata
Assignees
Type
Fields
Priority
Activity
linear-code commentedon Oct 16, 2026
TOA-261
[-]build: repo-governance - Tailor GitHub root configuration[/-][+]docs: repo-governance - Record direct GitHub configuration manifest[/+]