Phase 10 / Task F3: Push Delivery, Refresh PR #136, and Verify Checks

[Sam-Bolling]

Phase 10 Task

Task ID: F3
Title: Push Delivery, Refresh PR #136, and Verify Checks
Source: Approved Phase 10 Roadmap
Roadmap: P10-ROADMAP.md

---

• Objective: Publish the verified local delivery, make PR D-1: Resolve SystemTypeUris name collision between model.ts and constants.ts #136 accurately describe Phase 10, and confirm the required remote checks.
• Acceptance criteria advanced: P10-E4, P10-E5.
• Complexity/risk: High; reviewer-visible remote mutation.
• Locked decisions: Normal push only; existing base/head remain camptocamp:main and OS4CSAPI:clean-pr; no new maintainer question or dynamic-facade proposal.
• Expected work:
  • reverify local delivery SHA, clean status, remote target, and expected ahead count;
  • push clean-pr normally to OS4CSAPI/ogc-client;
  • verify PR D-1: Resolve SystemTypeUris name collision between model.ts and constants.ts #136 still has the expected base and head;
  • update the PR description with current upstream synchronization, real consumer APIs, CSAPI docs integration, scope limits, and exact verification results;
  • search PR text for obsolete factory and getDataStreams() usage;
  • monitor required checks to completion;
  • record the final PR URL, head SHA, checks, and delivery summary.
• Affected areas: Remote clean-pr and PR D-1: Resolve SystemTypeUris name collision between model.ts and constants.ts #136 metadata only.
• Explicit exclusions: Force-push, new commits after push without returning to the owning task, maintainer questions, live-server claims, unrelated PR edits.
• Automated acceptance gate:
  • remote clean-pr resolves to the F2-verified head;
  • PR metadata reports base camptocamp:main and head OS4CSAPI:clean-pr;
  • PR description contains current endpoint facade, advanced-factory role, CSAPI subpath/docs integration, upstream SHA, and gate summary;
  • obsolete-usage search over PR text returns zero matches;
  • all required PR checks complete successfully.
• Deliverable: Refreshed PR D-1: Resolve SystemTypeUris name collision between model.ts and constants.ts #136 at the verified Phase 10 delivery head with successful checks.
• Closing evidence: Remote head SHA, PR URL, description verification, check URLs/results, changed remote state, deviations or none.

Acceptance Criteria

• The task objective and expected work are complete under the locked decisions.
• Every condition in the automated acceptance gate above passes and its command output is recorded.
• The actual changed-file or evidence set stays within the listed affected areas.
• Every explicit exclusion is respected.
• Required workbench changes and evidence are committed and pushed to phase-10, or the task's stated evidence-only result is linked to an immutable commit.
• The closing comment records the commit SHA or verified immutable SHA, changed files, exact gate results, and Deviation from locked decision: none. or the approved deviation.

Dependencies

Blocked by: #199 — Phase 10 Task F2
Blocks: Nothing; final Roadmap task

Definition of Done / Closing Workflow

This issue is not complete until all three steps occur in order:

1. Edit this issue so every acceptance checkbox is [x].
2. Commit and push/sync all required changes or immutable evidence.
3. Post the required summary comment and close the issue as completed.

Do not close without the summary comment. New findings are recorded separately and are not absorbed into this task.

Operational Constraints

Before starting, review AI_OPERATIONAL_CONSTRAINTS.md and use its required task-entry acknowledgment.

Authority order for this issue:

1. Adopted standards and specifications.
2. Project governance.
3. P10 Contribution Goal and Definition.
4. P10 Implementation Guide.
5. P10 Roadmap.
6. This issue.
7. Existing repository code and documentation.
8. Conversational context.

Preserve minimal diffs, do not refactor adjacent code, do not introduce new features or dependencies, and stop on unresolved scope or architectural conflict.

[Sam-Bolling]

I have reviewed the AI Operational Constraints.
Issue goal: Publish the F2-verified clean-pr, refresh PR #136 accurately, verify its checks, and post the project-owner-requested maintainer notification.
Assumptions requiring confirmation: none. The @jahow comment will notify but will not ask a new question or propose a design change.

[Sam-Bolling]

F3 remote update is published; final closure is waiting on upstream workflow approval.

Completed remote state:

• OS4CSAPI/ogc-client:clean-pr and PR D-1: Resolve SystemTypeUris name collision between model.ts and constants.ts #136 head: 5f7cbd166143be76b60ea54593d6f313c75c3624.
• PR base/head verified as camptocamp/ogc-client:main ← OS4CSAPI/ogc-client:clean-pr.
• PR description refreshed with the current endpoint facade, advanced-factory signature, CSAPI subpath/TypeDoc/VitePress integration, upstream SHA, scope limits, and verification summary.
• Case-sensitive obsolete-use search: 0 matches for createCSAPIBuilder(endpoint, getDataStreams, the superseded factory claim, or the superseded facade-removal claim.
• Project-owner-requested maintainer notification posted: feat: add OGC Connected Systems API (CSAPI) support camptocamp/ogc-client#136 (comment)
• No force-push, new delivery commit, base/head retarget, design question, or live-server claim occurred.

Remaining gate:

• Upstream QA run: https://github.com/camptocamp/ogc-client/actions/runs/33132909335
• Current status: completed / action_required.
• Jobs created: 0.
• GitHub requires an upstream maintainer to approve this fork-originated workflow before the required checks can execute.

Issue #200 remains open until that external approval occurs and the required PR checks complete successfully.

[Sam-Bolling]

AD01 dependency update: canonical upstream advanced after the original Phase 10 delivery push, so this existing F3 issue remains the single final-publication/check task but must not resume until the approved addendum sequence is complete:

#201 → #202 → #203 → #204 → #205 → #200

Task #205 will leave a fully verified local clean-pr merge and durable handoff evidence. At that point, this issue resumes for the normal push, PR #136 mergeability verification, and available check monitoring. No duplicate publication issue was created.

Planning authority: AD01 Roadmap.

[Sam-Bolling]

AD01 dependency handoff is complete: issue #205 is closed with a fully verified local-only delivery merge.

• Prepared local clean-pr: b55d95aa0bd9f0cacf1e8b37953fde1ba14523f9
• Tree: 87fc78c9524aac32c668969ce32f96c84c8b03d9
• Locked upstream: a623911201218bc1e814a9f83c64f3a027031990
• Current remote clean-pr / PR head: 5f7cbd166143be76b60ea54593d6f313c75c3624 (unchanged)
• Exact handoff report
• Issue #205 completion evidence

Issue #200 may now resume with its required pre-push revalidation, one normal non-force push, PR mergeability/check verification, and factual PR-text refresh if needed. No delivery or PR mutation occurred in #205.

[Sam-Bolling]

I have reviewed the AI Operational Constraints.
Issue goal: Publish the AD5-verified clean-pr, refresh PR #136 with only current factual information, and record the resulting check state.
Assumptions requiring confirmation: none.

Resume preflight passed: local clean-pr is clean at $expectedLocal (tree $expectedTree), canonical upstream remains $expectedUpstream, remote clean-pr remains $expectedRemote, the branch is 0 behind / 13 reachable commits ahead with exactly one first-parent local merge, and a normal non-force push dry-run succeeded.

[Sam-Bolling]

AD01 final-publication status after delivery push:

• PR head: �55d95aa0bd9f0cacf1e8b37953fde1ba14523f9
• Delivery used a normal, non-force push; local, tracking, and remote clean-pr matched after publication.
• PR description refreshed in place for upstream baseline �623911, current 90-file/21-commit diff statistics, and the verified 32-path AD01 manifest.
• Existing maintainer notification refreshed in place; no additional maintainer ping or design question was created: feat: add OGC Connected Systems API (CSAPI) support camptocamp/ogc-client#136 (comment)
• PR is technically mergeable (mergeable: true).
• Obsolete public-description pattern counts are all zero: createCSAPIBuilder(endpoint, getDataStreams,
  emove the dynamic-import facade, and
  emove endpoint facade.
• New upstream QA run: https://github.com/camptocamp/ogc-client/actions/runs/33183846206
• GitHub concluded that run as �ction_required with 0 jobs created. This is the external fork-workflow approval gate and requires an upstream maintainer before QA can execute.

All contributor-controlled publication work is complete. Issue #200 remains open because its required-check acceptance criterion cannot be marked complete until the upstream QA workflow is approved and succeeds.