docs(w7): record product integration smoke #463

Merged
pdurlej merged 1 commit from codex/w7/closeout into main 2026-05-25 00:25:14 +02:00
Collaborator

Canary status: missing - rely on required Forgejo checks before merge

Canary Context Pack

Product story

Records the actual W7a outcome after pogodowa-babcia went live on RS2000. The important part is honesty: the service is green, but there is still a registry desired-state cleanup and W7b remains.

What changed

  • Added state/cycle/W7-product-integrations-output.md with runtime evidence and follow-ups.
  • Updated state/STATUS_NOW.md from W7-next to W7a-green/W7b-remaining.
  • Updated state/roadmap/current-platform-roadmap.md with the same W7 state.

Why it changed

The overnight deploy found and fixed two real runtime issues: initial arm64 image on amd64 host, then /app/data volume ownership. The service is now healthy on a local RS2000 image built from app commit f03f3e5, but platform registry pinning still needs a follow-up.

Files touched

  • state/cycle/W7-product-integrations-output.md
  • state/STATUS_NOW.md
  • state/roadmap/current-platform-roadmap.md

Runtime evidence

pogodowa-babcia smoke, metadata only:

  • container health: healthy
  • unhealthy containers after smoke: 0
  • internal endpoint statuses: /healthz, /snapshot, /alerts/active, /briefing/today all HTTP 200
  • tailnet endpoint statuses: same four endpoints HTTP 200
  • exposure labels: com.home.exposure=tailnet, ts-allowlist@file,security-headers@file
  • no host-published port for 8787/tcp

Known constraints

Production currently runs home-platform-pogodowa-babcia:f03f3e5-local. Follow-up is to publish f03f3e5-amd64 via the Infisical-held package PAT, update platform digest, and recreate only pogodowa-babcia from the registry artifact.

Explicit out-of-scope

No additional runtime mutation in this PR. No registry PAT use. No claim that all of W7 is closed while #235 remains open.

Requested decision

Approve merge as the durable status artifact for W7a.

Merge blockers

Incorrect runtime evidence, hiding the local-image drift, or declaring W7 globally closed.

Spec sources read

  • state/STATUS_NOW.md
  • state/roadmap/current-platform-roadmap.md
  • RS2000 runtime metadata for home-platform-pogodowa-babcia-1

Follow-up to #458/#462.

Canary status: missing - rely on required Forgejo checks before merge ## Canary Context Pack ### Product story Records the actual W7a outcome after `pogodowa-babcia` went live on RS2000. The important part is honesty: the service is green, but there is still a registry desired-state cleanup and W7b remains. ### What changed - Added `state/cycle/W7-product-integrations-output.md` with runtime evidence and follow-ups. - Updated `state/STATUS_NOW.md` from W7-next to W7a-green/W7b-remaining. - Updated `state/roadmap/current-platform-roadmap.md` with the same W7 state. ### Why it changed The overnight deploy found and fixed two real runtime issues: initial arm64 image on amd64 host, then `/app/data` volume ownership. The service is now healthy on a local RS2000 image built from app commit `f03f3e5`, but platform registry pinning still needs a follow-up. ### Files touched - `state/cycle/W7-product-integrations-output.md` - `state/STATUS_NOW.md` - `state/roadmap/current-platform-roadmap.md` ### Runtime evidence `pogodowa-babcia` smoke, metadata only: - container health: healthy - unhealthy containers after smoke: 0 - internal endpoint statuses: `/healthz`, `/snapshot`, `/alerts/active`, `/briefing/today` all HTTP 200 - tailnet endpoint statuses: same four endpoints HTTP 200 - exposure labels: `com.home.exposure=tailnet`, `ts-allowlist@file,security-headers@file` - no host-published port for `8787/tcp` ### Known constraints Production currently runs `home-platform-pogodowa-babcia:f03f3e5-local`. Follow-up is to publish `f03f3e5-amd64` via the Infisical-held package PAT, update platform digest, and recreate only `pogodowa-babcia` from the registry artifact. ### Explicit out-of-scope No additional runtime mutation in this PR. No registry PAT use. No claim that all of W7 is closed while #235 remains open. ### Requested decision Approve merge as the durable status artifact for W7a. ### Merge blockers Incorrect runtime evidence, hiding the local-image drift, or declaring W7 globally closed. ## Spec sources read - `state/STATUS_NOW.md` - `state/roadmap/current-platform-roadmap.md` - RS2000 runtime metadata for `home-platform-pogodowa-babcia-1` Follow-up to #458/#462.
docs(w7): record product integration smoke
All checks were successful
base-is-main / guard (pull_request) Successful in 1s
canary-required / collect-diff (pull_request) Successful in 4s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s
canary-required / canary (pull_request) Has been skipped
patchwarden-pr-sanity / sanity (pull_request) Successful in 24s
ccc42d0017
Sign in to join this conversation.
No reviewers
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform!463
No description provided.