docs: activate Claude TASK-006A handoff
This commit is contained in:
parent
57d1c090b1
commit
965d55d760
@ -76,3 +76,13 @@ This is the append-only implementation and handoff record shared by Codex and Cl
|
||||
- Known limitations: Mailboxes coordinate repository-based handoff and do not provide real-time notification; agents must inspect them at task start.
|
||||
- Next recommended task: Claude implements TASK-006A only and hands its commit to Codex for review.
|
||||
- Next owner: Claude.
|
||||
|
||||
## 2026-08-25 — TASK-012 review closure and activation
|
||||
|
||||
- Agent and role: Codex, finding resolver and handoff owner; Claude, independent read-only reviewer
|
||||
- Commit/diff: reviewed package commit `57d1c09`; immutable activation ref `handoff/task-006a-ready`
|
||||
- Findings resolved: Canonical delivery sequence now explicitly permits independent TASK-006A before the TASK-004/005 remainder; TASK-006A authorizes only its completion-log append; both mailbox directions share symmetric immutable templates and unique correction filenames; completed OAuth evidence is synchronized.
|
||||
- Checks and results: Documentation cross-references and task dependencies inspected; `git diff --check` passed before activation; no Android production file or external infrastructure changed.
|
||||
- Review result: No handoff activation occurs until the tag resolves to the committed metadata state. Claude checks out the tag, creates a `claude/` branch, implements TASK-006A only, and then stops for Codex review.
|
||||
- Known limitation: Repository mailboxes are asynchronous and must be checked manually at task start.
|
||||
- Next owner: Claude for TASK-006A.
|
||||
|
||||
@ -26,6 +26,7 @@ Filename format:
|
||||
```text
|
||||
Question: YYYYMMDD-HHMM-TASK-###-short-topic.md
|
||||
Answer: <exact-question-stem>-answer.md
|
||||
Answer correction: <exact-question-stem>-answer-correction-YYYYMMDD-HHMM.md
|
||||
```
|
||||
|
||||
### Common question template
|
||||
@ -56,6 +57,7 @@ Answer: <exact-question-stem>-answer.md
|
||||
- Responds to: <exact repository-relative question path>
|
||||
- Task: TASK-###
|
||||
- Decision authority: task contract | existing ADR | human decision required
|
||||
- Supersedes: <exact repository-relative prior answer path; correction only>
|
||||
|
||||
## Answer
|
||||
|
||||
@ -64,7 +66,7 @@ Answer: <exact-question-stem>-answer.md
|
||||
## Required checks or next action
|
||||
```
|
||||
|
||||
An answer uses the exact question stem with `-answer.md` appended and repeats the exact repository-relative question path under `Responds to`. A correction is a new normally named file with `Supersedes: <exact repository-relative path>` in its metadata; the old file remains unchanged. One file contains one bounded question or answer. Secrets, tokens, authorization codes, cookies, personal data, and source-file contents from private repositories must never be copied into these files.
|
||||
An initial answer uses the exact question stem with `-answer.md` appended and repeats the exact repository-relative question path under `Responds to`. An answer correction uses `<question-stem>-answer-correction-YYYYMMDD-HHMM.md`, keeps the original `Responds to`, and adds `Supersedes: <exact repository-relative prior answer path>`; the old file remains unchanged. A question correction uses a new timestamped question filename and adds `Supersedes` pointing to the prior question. One file contains one bounded question or answer. Secrets, tokens, authorization codes, cookies, personal data, and source-file contents from private repositories must never be copied into these files.
|
||||
|
||||
## Ownership
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
# UBGitea current status and development roadmap
|
||||
|
||||
Last updated: 2026-08-25
|
||||
Reviewed implementation baseline: `fc9d78a` plus TASK-012 documentation
|
||||
Reviewed handoff package commit: `57d1c09`
|
||||
Claude activation ref: `handoff/task-006a-ready`
|
||||
Active branch: `codex/repository-browser-foundation`
|
||||
|
||||
## Completed and verified
|
||||
@ -35,7 +36,7 @@ Active branch: `codex/repository-browser-foundation`
|
||||
|
||||
## Immediate serial handoff
|
||||
|
||||
Claude may now implement `TASK-006A` only.
|
||||
Claude may implement `TASK-006A` only from immutable Git tag `handoff/task-006a-ready`. The tag must resolve to a commit containing this status, task scope, prompt, mailbox rules, and review closure.
|
||||
|
||||
- Outcome: classify already-loaded source bytes as bounded text, binary, Git LFS pointer, unsupported encoding, or oversized content.
|
||||
- Writable scope: only the paths listed in `tasks/006a-code-content-classifier.md`.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
# TASK-006A: Classify source content safely
|
||||
|
||||
Status: awaiting exact TASK-012 handoff commit
|
||||
Status: ready — start from immutable Git tag `handoff/task-006a-ready`
|
||||
Owner: Claude
|
||||
Reviewer: Codex
|
||||
|
||||
@ -11,7 +11,7 @@ Classify already-loaded repository content into bounded text, binary, Git LFS po
|
||||
## Contract freeze
|
||||
|
||||
- Shared domain contract commit: `0929282`.
|
||||
- Claude starts from the reviewed application baseline `fc9d78a` plus the TASK-012 documentation handoff commit; no shared domain file may differ from `0929282` without an approved contract change.
|
||||
- Reviewed handoff package commit: `57d1c09`. Claude starts from immutable activation tag `handoff/task-006a-ready`; no shared domain file may differ from `0929282` without an approved contract change.
|
||||
- Input contracts: `SourceContent`, `SourceFile`, `RepositoryPath`, and `RepositoryRef` from TASK-003.
|
||||
- This task must not change the frozen domain contracts. Required changes use the request format in `docs/workstreams.md`.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
# TASK-012: Establish the Codex-Claude handoff workspace
|
||||
|
||||
Status: implemented — review findings being resolved
|
||||
Status: complete — package `57d1c09`, activation tag `handoff/task-006a-ready`
|
||||
Owner: Codex
|
||||
Reviewer: Claude
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user