skic-v1-playground/knowledge-wiki
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

wiki: sync 2026-07-20 18:52 UTC — 2 file(s) updated

Browse Source
This commit is contained in:
jarvis-at-skic
2026-07-20 18:52:55 +00:00
parent b0e04a459b
commit 8bb811a855
2 changed files with 108 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
meta/gitea-repository-operations.md
+67
View File
@@ -0,0 +1,67 @@
# Gitea Repository Operations
_Last verified: 2026-07-20 18:30 UTC_
## Status
✅ Hermes has a reusable local skill for general Gitea repository work:
- Skill: `gitea-repository-operations`
- Path: `/opt/data/skills/software-development/gitea-repository-operations/SKILL.md`
- Scope: any organization or repository on `gitea.lego-cloud.eu`, not only Docusaurus projects
The existing `gitea-docusaurus-projects` skill remains the specialist extension for Docusaurus, pnpm, sharp-corner UI conventions, and documentation CI/CD.
## Instance baseline
| Capability | Configuration | Status |
|---|---|---|
| Web UI | `https://gitea.lego-cloud.eu` | ✅ |
| REST API | `https://gitea.lego-cloud.eu/api/v1` | ✅ |
| API credential | `/opt/data/.env` → `GITHUB_TOKEN` | ✅ |
| SSH endpoint | `ssh://git@gitea.lego-cloud.eu:30009/ORG/REPO.git` | ✅ |
| SSH identity | `/opt/data/home/.ssh/id_ed25519` | ✅ |
| Git identity | `Jarvis Jr Hermes <jarvis.at.skic@gmail.com>` | ✅ |
Never publish the API token, embed it in a Git remote, or commit it to a repository.
## Standard workflow
1. Authenticate with `GET /api/v1/user` and confirm the account is active.
2. Discover organization/repository metadata before mutation.
3. Clone via SSH with the explicit identity and `BatchMode=yes`.
4. Fetch and inspect branch divergence before editing an existing clone.
5. Preserve remote work; no force-push or history rewrite without explicit direction.
6. Run repository-specific validation and `git diff --cached --check`.
7. Commit only intended files and push through SSH.
8. Verify local/remote branch SHAs.
9. Read back a distinctive file through the authenticated Gitea API.
10. Report repository URL, branch, commit SHA, validation, and caveats.
## Skill coverage
- Organization and repository discovery/creation
- Safe clone, fetch, branch, commit, and push workflow
- Pagination and authenticated API usage
- Collaborators with `read`, `write`, or `admin` permission
- Issues, pull requests, releases, and tags
- Gitea Actions under `.gitea/workflows/`
- Automated no-op Git synchronization
- Private-repository raw-file verification
- Troubleshooting disabled accounts, SSH keys, API authorization, divergence, and CI runners
## Known operational lessons
- API and SSH access must be tested independently.
- A successful push is not complete verification; read back the requested artifact.
- Repository-level `admin` is not the same as organization ownership.
- Private raw web links may return `404`; use the authenticated API endpoint.
- Gitea account disablement can break both previously valid tokens and SSH keys without requiring key/token replacement after re-enablement.
- Scheduled syncs must not silently accumulate unpushed commits.
## Current Gitea repositories referenced by the wiki
- `skic-v1-playground/knowledge-wiki` — automated wiki mirror
- `world-v1/network-v1` — global network address book and investigation repository
Add future repository-specific details to their project documentation; keep this page focused on reusable operations.
meta/network-v1.md
+41
View File
@@ -0,0 +1,41 @@
# world-v1/network-v1
_Last updated: 2026-07-20 18:49 UTC_
## Status
✅ Public Gitea repository: https://gitea.lego-cloud.eu/world-v1/network-v1
The repository is a source-backed address book and evolving map of the global Internet ecosystem.
## Repository baseline
- 25 ecosystem entities across governance, standards, RIRs, DNS, interconnection, routing, incident response, physical infrastructure, and operator communities.
- Human-readable pages under `address-book/`.
- Canonical CSV datasets under `data/`.
- Methodology and taxonomy under `docs/`.
- Research backlog under `research/`.
- Dependency-free validation through `make validate`.
## IP-network direction
Lego directed Hermes to extend the project from ecosystem organizations into an IP-level network map, beginning with `0.0.0.0` and `1.1.1.1`.
The project must not use one ambiguous `owner` field. Every IP investigation separates:
1. IANA special-purpose classification;
2. registry and registered resource holder;
3. current announced prefix and origin ASN;
4. network/service operator;
5. exact service or function;
6. infrastructure relationships;
7. authoritative sources and verification date.
### Initial findings
- `0.0.0.0` — IANA special-purpose protocol address, not organizationally assigned, not forwardable or globally reachable.
- `1.1.1.1` — covering prefix `1.1.1.0/24` is registered in APNIC RDAP as `APNIC-LABS` to APNIC Research and Development; RIPEstat observes origin `AS13335` Cloudflare; Cloudflare operates the 1.1.1.1 recursive DNS service. APNIC RDAP documents the APNIC–Cloudflare resolver project.
## Next scope
🔲 Add important special-purpose ranges, public resolvers, DNS root identities, RIR exemplars, RPKI evidence, ASN relationships, IXPs/facilities, and selected global networks using explicit criteria rather than blindly enumerating IPv4 space.