Merge remote-tracking branch 'origin/main' into feat/registry
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Successful in 1m8s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Successful in 8s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 5s
PR Check / AI code review (opencode) (pull_request) Successful in 49s
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Successful in 1m8s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Successful in 8s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 5s
PR Check / AI code review (opencode) (pull_request) Successful in 49s
# Conflicts: # OKF_Nuxt/log.md
This commit is contained in:
commit
c3445ad55d
13 files changed
+487
-15
No files matched your search
@@ -6,6 +6,13 @@
|
||||
* **Review follow-up** (PR #19, 1 BLOCKER + 4 WARN + 2 NIT): applied the strict `vMAJOR.MINOR.PATCH` check, the newest-release rule for `latest`, a smoke test that starts the image and requires 2xx on `/`, and `timeout-minutes: 20`. Rejected with evidence: the `.dockerignore` leak (`.env*`, `*.pem`, `.git` are excluded) and the Docker-client/daemon API mismatch (20.10.24 client against a 29.9.2 daemon built successfully over the socket).
|
||||
* **Second review follow-up** (PR #19): the job now runs on the dedicated `publish` label instead of `ubuntu-latest`, so the host socket it needs can never be shared with PR jobs - the earlier version required a runner configuration its own trust boundary forbade. Added the immutability guard (registry v2 `manifests/<version>`: `200` aborts, `404` continues) after measuring that `docker manifest inspect` fails on OCI indexes with the pinned 20.10 client; the smoke test now also requires a rendered body (10 kB floor) rather than a bare 2xx. `.github/actionlint.yaml` declares the custom label, and the hook passes it with `-config-file` because this repo keeps workflows in `.gitea/`.
|
||||
|
||||
## 2026-10-23 (profile data in the terminal)
|
||||
* **Creation**: [Profile data](profile.md) - imported the LinkedIn export `Profile.pdf` into `app/data/chapters.ts`: PreZero active; Defifort, Alignerr, Outlier, freelance and 42 finished. Each row carries a context label (Enterprise, Web3 startup, AI Developer, Freelance, Education). The terminal now shows 1 active / 5 sealed / 14 rebounds; the export has no entry for `dreambit`, `ongoing-studies` or `apprenticeship`, so those rows are gone. `uptime` and `rebounds` remain mock.
|
||||
* **Update**: [backend endpoints](backend-endpoints.md) - examples and totals now match the real six-chapter list; the source frontmatter points at the export.
|
||||
|
||||
## 2026-10-23 (homepage metrics contract)
|
||||
* **Update**: [backend endpoints](backend-endpoints.md) - added `GET /api/metrics`: the chapter rows plus the terminal footer totals (`active`, `sealed`, `rebounds`) in one response. The homepage terminal is meant to show measurements, not mockup copy, so the gateway should own them; `/api/chapters` stays the row list for the life map. The old note that the counters are computed in the browser is gone.
|
||||
|
||||
## 2026-10-23 (PR #16 review checked, three findings applied)
|
||||
* **Update**: [pr-checker.yml](../.gitea/workflows/pr-checker.yml) - the review prompt now states that `pnpm-lock.yaml` is excluded from `.pr-review-diff.patch` on purpose. The reviewer read the exclusion as an uncommitted lockfile and raised a false BLOCKER; the lockfile is in the PR and matches `package.json`.
|
||||
* **Fix**: `scripts/generate-favicon.mjs` - `BACKGROUND = null` now writes alpha 0 instead of opaque black, matching the transparency the comment promises. The committed icons are unchanged (regenerated byte-identical).
|
||||
|
||||
Reference in new issue
Block a user