Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 73 Pull Requests 9 Actions Packages Projects Releases Wiki Activity

Make Gitea Wiki publication a required repo readiness gate #224

New Issue
Closed
opened 2026-07-05 20:15:36 -05:00 by jcwalker3 · 2 comments
jcwalker3 commented 2026-07-05 20:15:36 -05:00
Owner
Copy Link
Copy Source

Problem

The project has had prior wiki-related work, including docs/wiki policy and Gitea Wiki sync helper discussions, but the actual Gitea Wiki was never reliably added/populated on the repository pages as requested.

This creates a mismatch:

  • docs/wiki/ may exist in the repo.
  • A sync helper or mirror policy may exist.
  • But the Gitea Wiki tab itself may still be empty, missing, stale, or not verified.

That does not satisfy the requirement. The user explicitly wants the Gitea Wiki to be present and useful on the Gitea repo page, not only stored as markdown inside the source tree.

Required outcome

Every active MCP Control Plane repo must have a visible, usable Gitea Wiki populated from the canonical project documentation.

At minimum, each repo wiki should include:

  • Home
  • Project overview
  • Current workflow / operating model
  • Role and capability rules
  • PR review rules
  • Issue workflow rules
  • Known hard walls / guardrails
  • Runbooks or links to repo-tracked runbooks
  • Links back to canonical docs/wiki/ source files, when applicable

Source-of-truth rule

The repo-tracked docs/wiki/ directory should remain the canonical source of truth unless a repo explicitly documents otherwise.

The Gitea Wiki should be treated as the published/readable mirror.

A PR should not be accepted as “wiki complete” unless both are true:

  1. The source docs exist in the repo.
  2. The Gitea Wiki has been created or updated and verified on the Gitea repo page.

Guardrail requirement

Add a durable process wall so future LLMs cannot close wiki issues after only creating markdown files or helper scripts.

The wall should require proof such as:

  • Wiki URL exists.
  • Wiki Home page exists.
  • Required wiki pages exist.
  • Wiki content matches or clearly mirrors docs/wiki/.
  • Verification output is pasted into the issue or PR.
  • Reviewer checklist includes “Gitea Wiki visible and populated.”

Acceptance criteria

  • Inventory all active MCP-related repos that should have a Gitea Wiki.
  • For each repo, determine whether the Gitea Wiki exists and whether it has content.
  • Create or update canonical docs/wiki/ content where missing.
  • Publish or sync the content into the actual Gitea Wiki.
  • Add verification instructions for checking the Gitea Wiki page.
  • Add a reviewer checklist item requiring visible Gitea Wiki verification.
  • Add a process rule that wiki issues cannot be closed based only on repo markdown.
  • Update the old wiki-related issues/PRs with a comment explaining that helper/policy work was insufficient without actual Gitea Wiki publication.
  • Provide final proof links for every repo wiki page created or updated.

Regression to prevent

Do not allow future LLMs to say “wiki complete” when they only added:

  • docs/wiki/
  • markdown documentation
  • a sync helper
  • a mirror policy
  • a README link

Those are necessary but not sufficient. The actual Gitea Wiki must be populated and verified.

## Problem The project has had prior wiki-related work, including docs/wiki policy and Gitea Wiki sync helper discussions, but the actual Gitea Wiki was never reliably added/populated on the repository pages as requested. This creates a mismatch: * `docs/wiki/` may exist in the repo. * A sync helper or mirror policy may exist. * But the Gitea Wiki tab itself may still be empty, missing, stale, or not verified. That does not satisfy the requirement. The user explicitly wants the Gitea Wiki to be present and useful on the Gitea repo page, not only stored as markdown inside the source tree. ## Required outcome Every active MCP Control Plane repo must have a visible, usable Gitea Wiki populated from the canonical project documentation. At minimum, each repo wiki should include: * Home * Project overview * Current workflow / operating model * Role and capability rules * PR review rules * Issue workflow rules * Known hard walls / guardrails * Runbooks or links to repo-tracked runbooks * Links back to canonical `docs/wiki/` source files, when applicable ## Source-of-truth rule The repo-tracked `docs/wiki/` directory should remain the canonical source of truth unless a repo explicitly documents otherwise. The Gitea Wiki should be treated as the published/readable mirror. A PR should not be accepted as “wiki complete” unless both are true: 1. The source docs exist in the repo. 2. The Gitea Wiki has been created or updated and verified on the Gitea repo page. ## Guardrail requirement Add a durable process wall so future LLMs cannot close wiki issues after only creating markdown files or helper scripts. The wall should require proof such as: * Wiki URL exists. * Wiki Home page exists. * Required wiki pages exist. * Wiki content matches or clearly mirrors `docs/wiki/`. * Verification output is pasted into the issue or PR. * Reviewer checklist includes “Gitea Wiki visible and populated.” ## Acceptance criteria * [ ] Inventory all active MCP-related repos that should have a Gitea Wiki. * [ ] For each repo, determine whether the Gitea Wiki exists and whether it has content. * [ ] Create or update canonical `docs/wiki/` content where missing. * [ ] Publish or sync the content into the actual Gitea Wiki. * [ ] Add verification instructions for checking the Gitea Wiki page. * [ ] Add a reviewer checklist item requiring visible Gitea Wiki verification. * [ ] Add a process rule that wiki issues cannot be closed based only on repo markdown. * [ ] Update the old wiki-related issues/PRs with a comment explaining that helper/policy work was insufficient without actual Gitea Wiki publication. * [ ] Provide final proof links for every repo wiki page created or updated. ## Regression to prevent Do not allow future LLMs to say “wiki complete” when they only added: * `docs/wiki/` * markdown documentation * a sync helper * a mirror policy * a README link Those are necessary but not sufficient. The actual Gitea Wiki must be populated and verified.
jcwalker3 added the status:in-progress label 2026-07-06 00:36:20 -05:00
jcwalker3 commented 2026-07-06 00:37:09 -05:00
Author
Owner
Copy Link
Copy Source

Live Gitea Wiki publication — Gitea-Tools (operator-confirmed)

Operator wiki sync completed for Scaled-Tech-Consulting/Gitea-Tools.

Implementation PR

PR #230: branch feat/issue-224-gitea-tools-wiki-bootstrap (head 342974f)

Delivers: docs/wiki/ (10 pages), scripts/sync-gitea-wiki.sh, PR template gate (#224), tests/test_wiki_sync.py (11 passed).

Bootstrap + sync

  1. Bootstrapped wiki via API (Home page) — wiki git repo did not exist yet.
  2. Operator-confirmed sync: 
    GITEA_WIKI_SYNC_CONFIRM="SYNC WIKI Gitea-Tools" scripts/sync-gitea-wiki.sh --push
  3. Re-synced after updating docs/wiki/Repositories.md publication status.

Proof links (acceptance criterion 6)

  • Wiki Home: https://gitea.prgs.cc/Scaled-Tech-Consulting/Gitea-Tools/wiki/Home
  • Page listing (10): History, Home, Identity-and-Profiles, MCP-Tools, Open-Decisions, Operator-Guide, Repositories, Runbooks, Safety-and-Gates, Workflow
  • Wiki git log: 
    11549ee docs: sync from repo docs/wiki (source of truth)
440f186 docs: bootstrap Gitea-Tools wiki from docs/wiki (issue #224)

Cross-repo status map

mcp-control-plane PR #94 updated to record Gitea-Tools as published (4e63190).

Remaining: merge PR #230 (repo prerequisites) and PR #94 (shared Repositories map). Live wiki is already populated and verified.

## Live Gitea Wiki publication — `Gitea-Tools` (operator-confirmed) Operator wiki sync completed for `Scaled-Tech-Consulting/Gitea-Tools`. ### Implementation PR **PR #230:** branch `feat/issue-224-gitea-tools-wiki-bootstrap` (head `342974f`) Delivers: `docs/wiki/` (10 pages), `scripts/sync-gitea-wiki.sh`, PR template gate (#224), `tests/test_wiki_sync.py` (11 passed). ### Bootstrap + sync 1. Bootstrapped wiki via API (Home page) — wiki git repo did not exist yet. 2. Operator-confirmed sync: ```bash GITEA_WIKI_SYNC_CONFIRM="SYNC WIKI Gitea-Tools" scripts/sync-gitea-wiki.sh --push ``` 3. Re-synced after updating `docs/wiki/Repositories.md` publication status. ### Proof links (acceptance criterion 6) - **Wiki Home:** https://gitea.prgs.cc/Scaled-Tech-Consulting/Gitea-Tools/wiki/Home - **Page listing (10):** History, Home, Identity-and-Profiles, MCP-Tools, Open-Decisions, Operator-Guide, Repositories, Runbooks, Safety-and-Gates, Workflow - **Wiki git log:** ``` 11549ee docs: sync from repo docs/wiki (source of truth) 440f186 docs: bootstrap Gitea-Tools wiki from docs/wiki (issue #224) ``` ### Cross-repo status map `mcp-control-plane` PR #94 updated to record Gitea-Tools as published (`4e63190`). **Remaining:** merge PR #230 (repo prerequisites) and PR #94 (shared Repositories map). Live wiki is already populated and verified.
sysadmin removed the status:in-progress label 2026-07-06 00:40:46 -05:00
jcwalker3 commented 2026-07-06 00:42:17 -05:00
Author
Owner
Copy Link
Copy Source

Closure proof — Issue #224 complete

All acceptance criteria satisfied with live Gitea Wiki evidence for both in-scope MCP Control Plane repositories.

Merged PRs

Repo PR Merge commit
Gitea-Tools #230 09a766be5db7eea010ef02c11a9e2eab7fe22ee5
mcp-control-plane #94 3f06e8959558b3f8a60cc6b82e668a1f39f85ff7

Scaled-Tech-Consulting/Gitea-Tools

  • Wiki Home: https://gitea.prgs.cc/Scaled-Tech-Consulting/Gitea-Tools/wiki/Home
  • Pages (10): History, Home, Identity-and-Profiles, MCP-Tools, Open-Decisions, Operator-Guide, Repositories, Runbooks, Safety-and-Gates, Workflow
  • Wiki git log: 
    d1f0693 docs: sync from repo docs/wiki (source of truth)
11549ee docs: sync from repo docs/wiki (source of truth)
440f186 docs: bootstrap Gitea-Tools wiki from docs/wiki (issue #224)
  • Repo source: docs/wiki/ (10 pages) + scripts/sync-gitea-wiki.sh on master

Scaled-Tech-Consulting/mcp-control-plane

  • Wiki Home: https://gitea.prgs.cc/Scaled-Tech-Consulting/mcp-control-plane/wiki/Home
  • Pages (10): History, Home, Identity-and-Profiles, MCP-Tools, Open-Decisions, Operator-Guide, Repositories, Runbooks, Safety-and-Gates, Workflow
  • Wiki git log: 
    eabca1a docs: sync from repo docs/wiki (source of truth)
5f99a14 docs: sync from repo docs/wiki (source of truth)
6f76ce9 docs: bootstrap Gitea wiki from docs/wiki (issue #87)
  • Status table: docs/wiki/Repositories.md on master records both repos as published

Gate deliverables

  • Reviewer checklist gate: .gitea/pull_request_template.md (#224 / #87)
  • Closure prevention: documented in wiki Runbooks + tests
  • Source-of-truth rule: stated on each repo Wiki Home page

Closing with live-Wiki proof. Markdown/helper work alone would not satisfy this gate.

## Closure proof — Issue #224 complete All acceptance criteria satisfied with live Gitea Wiki evidence for **both** in-scope MCP Control Plane repositories. ### Merged PRs | Repo | PR | Merge commit | |---|---|---| | `Gitea-Tools` | #230 | `09a766be5db7eea010ef02c11a9e2eab7fe22ee5` | | `mcp-control-plane` | #94 | `3f06e8959558b3f8a60cc6b82e668a1f39f85ff7` | ### `Scaled-Tech-Consulting/Gitea-Tools` - **Wiki Home:** https://gitea.prgs.cc/Scaled-Tech-Consulting/Gitea-Tools/wiki/Home - **Pages (10):** History, Home, Identity-and-Profiles, MCP-Tools, Open-Decisions, Operator-Guide, Repositories, Runbooks, Safety-and-Gates, Workflow - **Wiki git log:** ``` d1f0693 docs: sync from repo docs/wiki (source of truth) 11549ee docs: sync from repo docs/wiki (source of truth) 440f186 docs: bootstrap Gitea-Tools wiki from docs/wiki (issue #224) ``` - **Repo source:** `docs/wiki/` (10 pages) + `scripts/sync-gitea-wiki.sh` on `master` ### `Scaled-Tech-Consulting/mcp-control-plane` - **Wiki Home:** https://gitea.prgs.cc/Scaled-Tech-Consulting/mcp-control-plane/wiki/Home - **Pages (10):** History, Home, Identity-and-Profiles, MCP-Tools, Open-Decisions, Operator-Guide, Repositories, Runbooks, Safety-and-Gates, Workflow - **Wiki git log:** ``` eabca1a docs: sync from repo docs/wiki (source of truth) 5f99a14 docs: sync from repo docs/wiki (source of truth) 6f76ce9 docs: bootstrap Gitea wiki from docs/wiki (issue #87) ``` - **Status table:** `docs/wiki/Repositories.md` on `master` records both repos as published ### Gate deliverables - Reviewer checklist gate: `.gitea/pull_request_template.md` (#224 / #87) - Closure prevention: documented in wiki Runbooks + tests - Source-of-truth rule: stated on each repo Wiki Home page **Closing with live-Wiki proof. Markdown/helper work alone would not satisfy this gate.**
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#224