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

Refresh stale wiki proof-head citation in Repositories map (#224 follow-up) #232

New Issue
Closed
opened 2026-07-06 00:54:25 -05:00 by jcwalker3 · 1 comment
jcwalker3 commented 2026-07-06 00:54:25 -05:00
Owner
Copy Link
Copy Source

Problem

docs/wiki/Repositories.md (merged via PR #230) cites the Gitea-Tools wiki git log head as 11549ee, but the live wiki head is d1f0693 (the re-sync that ran after the publication-status update). The table's own rule says to update it whenever a wiki is published, re-synced, or found stale.

Scope (docs-only)

  • Update the Gitea-Tools proof row in docs/wiki/Repositories.md to cite the current live wiki head (d1f0693 at task start, or newer if another sync lands first).
  • Run scripts/sync-gitea-wiki.sh dry-run, then operator-confirmed push, and record live-head proof honestly.
  • No code, tests, templates, helper scripts, or unrelated wiki content.

Acceptance

  • Repositories map cites the verified live Gitea-Tools wiki head.
  • Publication statuses remain truthful.
  • Wiki sync dry-run output and post-sync live wiki log recorded on this issue or the PR.
  • Docs-only PR merged by a reviewer session (no self-merge).

Related: #224 (readiness gate), PR #230 (bootstrap), mcp-control-plane #87/PR #94 (shared Repositories map).

## Problem `docs/wiki/Repositories.md` (merged via PR #230) cites the Gitea-Tools wiki git log head as `11549ee`, but the live wiki head is `d1f0693` (the re-sync that ran after the publication-status update). The table's own rule says to update it whenever a wiki is published, re-synced, or found stale. ## Scope (docs-only) - Update the Gitea-Tools proof row in `docs/wiki/Repositories.md` to cite the current live wiki head (`d1f0693` at task start, or newer if another sync lands first). - Run `scripts/sync-gitea-wiki.sh` dry-run, then operator-confirmed push, and record live-head proof honestly. - No code, tests, templates, helper scripts, or unrelated wiki content. ## Acceptance - [ ] Repositories map cites the verified live Gitea-Tools wiki head. - [ ] Publication statuses remain truthful. - [ ] Wiki sync dry-run output and post-sync live wiki log recorded on this issue or the PR. - [ ] Docs-only PR merged by a reviewer session (no self-merge). Related: #224 (readiness gate), PR #230 (bootstrap), mcp-control-plane #87/PR #94 (shared Repositories map).
jcwalker3 added the status:in-progress label 2026-07-06 00:54:51 -05:00
jcwalker3 commented 2026-07-06 01:00:51 -05:00
Author
Owner
Copy Link
Copy Source

Resolution — superseded by PR #231, live state verified

While this issue's branch (feat/issue-232-refresh-wiki-proof-heads, head eb97060) was being prepared, a parallel session landed the same refresh via PR #231 (feat/issue-224-wiki-proof-refresh, merge commit 4dd32bb, merged 2026-07-06T00:57:29-05:00) — with a richer mcp-control-plane proof row. No PR was opened from this issue's branch: its diff against post-#231 master would have regressed that row.

Live-state verification (this session)

  • docs/wiki/Repositories.md on master (4dd32bb) cites Gitea-Tools wiki head d1f0693 and mcp-control-plane wiki head ef3dec2 — acceptance met.
  • Wiki sync: dry-run passed (10 pages), then GITEA_WIKI_SYNC_CONFIRM="SYNC WIKI Gitea-Tools" scripts/sync-gitea-wiki.sh --push run twice: once from this issue's branch (wiki head 6b6f5ae), then re-run from master 4dd32bb after PR #231 landed, to restore the wiki as an exact master mirror.
  • Current live wiki git log: 
    8c6ab83 docs: sync from repo docs/wiki (source of truth)   <- current head, mirrors master 4dd32bb
6b6f5ae docs: sync from repo docs/wiki (source of truth)
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)
  • Verified diff of live wiki Repositories.md vs master:docs/wiki/Repositories.md: identical. 10 pages live.
  • Note (inherent one-behind): the table cites the head verified at edit time (d1f0693); each re-sync necessarily creates a newer wiki head (now 8c6ab83).

Cleanup follow-up

Branch feat/issue-232-refresh-wiki-proof-heads (eb97060) is redundant and can be deleted by a session with branch-delete capability; this author profile has none.

Closing: acceptance criteria satisfied by merged master state + live-wiki proof above.

## Resolution — superseded by PR #231, live state verified While this issue's branch (`feat/issue-232-refresh-wiki-proof-heads`, head `eb97060`) was being prepared, a parallel session landed the same refresh via **PR #231** (`feat/issue-224-wiki-proof-refresh`, merge commit `4dd32bb`, merged 2026-07-06T00:57:29-05:00) — with a richer mcp-control-plane proof row. No PR was opened from this issue's branch: its diff against post-#231 master would have regressed that row. ### Live-state verification (this session) - `docs/wiki/Repositories.md` on master (`4dd32bb`) cites Gitea-Tools wiki head `d1f0693` and mcp-control-plane wiki head `ef3dec2` — acceptance met. - Wiki sync: dry-run passed (10 pages), then `GITEA_WIKI_SYNC_CONFIRM="SYNC WIKI Gitea-Tools" scripts/sync-gitea-wiki.sh --push` run twice: once from this issue's branch (wiki head `6b6f5ae`), then re-run from master `4dd32bb` after PR #231 landed, to restore the wiki as an exact master mirror. - **Current live wiki git log:** ``` 8c6ab83 docs: sync from repo docs/wiki (source of truth) <- current head, mirrors master 4dd32bb 6b6f5ae docs: sync from repo docs/wiki (source of truth) 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) ``` - Verified `diff` of live wiki `Repositories.md` vs `master:docs/wiki/Repositories.md`: identical. 10 pages live. - Note (inherent one-behind): the table cites the head verified at edit time (`d1f0693`); each re-sync necessarily creates a newer wiki head (now `8c6ab83`). ### Cleanup follow-up Branch `feat/issue-232-refresh-wiki-proof-heads` (`eb97060`) is redundant and can be deleted by a session with branch-delete capability; this author profile has none. Closing: acceptance criteria satisfied by merged master state + live-wiki proof above.
jcwalker3 removed the status:in-progress label 2026-07-06 01:01:23 -05:00
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#232