Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions project/ticket-281/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Ticket 281: Refresh Goal automation lock

- **ID**: ticket-281
- **Owner**: agent:codex-heyasa-audit
- **Status**: IN_PROGRESS
- **Workflow state**: PUBLICATION

SESSION_EXECUTION_AUTHORIZATION: user approved the bounded controller/source/Goal repair on2026-11-06 and requested autonomous continuation. The independently integrated Autonom PR206 was deployed first, then the authenticated controller released exact owned expired279 and granted actual281 editing ownership. No direct protected lease-state mutation was used.

## Result

The automation lock now uses Goal2.2.11, matching the existing catalog. This changes only that package record; the other122records, runtime requirements, Python markers and dependency declarations stay identical. It resolves the pre-existing freshness blocker for Planfile PR342.

## Acceptance criteria

- [x] AC-01: Resolve existing Goal package2.2.10 to2.2.11 and prove all other122package records are unchanged.
- [x] AC-02: Native uv lock --check, catalog freshness and managed governance pass. All8requiredCIchecks and independent OneDev/Validator publication remain required.

The accepted intent and base are preserved. Implementation scope is uv.lock only, plus this ticket metadata. Source279 and foreign280 remain untouched. Production publication is represented by the protected external receipt; this ticket stays IN_PROGRESS/PUBLICATION until that receipt.
81 changes: 81 additions & 0 deletions project/ticket-281/intent.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
{
"schema": "new-project.intent/v3",
"ticket": "ticket-281",
"summary": "Refresh the Goal automation lock required by dependency freshness",
"workstream": "integration",
"classification": {
"kind": "BUG",
"priority": "P1",
"origin": "health"
},
"allowedPaths": [
"project/ticket-281/**",
"TODO.md",
"project/TICKETS.md",
"uv.lock"
],
"forbiddenPaths": [
"project/ticket-*/user-*.md"
],
"stacks": [],
"dependsOn": [],
"conflictsWith": [],
"integrationTicket": null,
"delivery": {
"acceptedBaseSha": "edfa131b22ae8f6081d9c90489d9689f5075337a",
"targetBranch": "main",
"outcome": "Refresh only Goal2.2.10 to2.2.11 in uv.lock so existing required dependency freshness passes and unblocks native279/PR342.",
"nonGoals": [
"No dependency/catalog/workflow/check waiver",
"No native279 code change or unmerged-work discard",
"No other package update or Python minimum change"
],
"complexity": "S",
"estimatedMinutes": 15,
"budgets": {
"maxImplementationFiles": 1,
"maxAffectedComponents": 1,
"maxPublicInterfaceChanges": 0,
"maxRuntimeDependencies": 0
},
"architecture": {
"status": "accepted",
"decision": "Use existing uv resolver for the automation dependency and preserve all other123package records and Python>=3.12 automation group.",
"components": [
{
"name": "Automation dependency lock",
"paths": [
"uv.lock"
]
}
],
"responsibilityChanges": false,
"interfaceChanges": [],
"dataChanges": [],
"ui": {
"impact": "none",
"states": [],
"evidence": []
},
"rollback": "A separately validated revert of the lock delta; preserve native279 candidate and prior package metadata."
},
"runtimeDependencies": [],
"validation": [
{
"criterion": "AC-02",
"commands": [
"uv lock --check",
"goal dependencies --catalog .github/internal-dependencies.json --check"
],
"evidence": "Isolated exact-base proposal resolves123packages and freshness=true; actual source validation pending own fenced grant."
},
{
"criterion": "AC-03",
"commands": [
"./project/governance-check.sh"
],
"evidence": "Pending canonical native281 source check and independent required CI."
}
]
}
}
6 changes: 3 additions & 3 deletions uv.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading