DCD-001 (UC-001) and DCD-002 (consolidated project model): design classes refining DM-001, class table, method traceability to OC-001 and SD-001, pattern annotations, dependency check and the mapping of each class to src/lib
SD-001 aligned with the DCD method signatures; three lines of SD-001 damaged by an earlier edit are restored
Dictionary, registry and traceability matrix updated
2. MIL-005 plan (RC-020, Go)
The script asks for a credential that .env does not provide (GITEA_TOKEN, and GITHUB_PAT and GITHUB_USER when GitHub is chosen) and, after a yes, creates the new project's own .env: only the needed keys, owner-only, excluded from git, never replaced without a yes
Business Case objective 9; objective 6 and success criterion 1 are amended: a token may now be written to exactly one file, the new project's .env, after a yes. A risk row records the plain-text token on disk and its mitigations
US-001.05, UC-001 extensions 2b, 9c and 9d, SSD, OC, SD, DM-001, DM-002, dictionary, DCD-001, DCD-002 and the Project Plan changed to match
Milestone MIL-005 (9 Go/No-Go criteria, 5 tasks); issues #35 to #39 are synced to Gitea
Not done: the PlantUML blocks were not rendered (no PlantUML server is configured; action item in RC-021).
Documents only, no code.
**1. Design Class Diagrams (RC-021, Go)**
- DCD-001 (UC-001) and DCD-002 (consolidated project model): design classes refining DM-001, class table, method traceability to OC-001 and SD-001, pattern annotations, dependency check and the mapping of each class to `src/lib`
- SD-001 aligned with the DCD method signatures; three lines of SD-001 damaged by an earlier edit are restored
- Dictionary, registry and traceability matrix updated
**2. MIL-005 plan (RC-020, Go)**
- The script asks for a credential that `.env` does not provide (`GITEA_TOKEN`, and `GITHUB_PAT` and `GITHUB_USER` when GitHub is chosen) and, after a yes, creates the new project's own `.env`: only the needed keys, owner-only, excluded from git, never replaced without a yes
- Business Case objective 9; objective 6 and success criterion 1 are amended: a token may now be written to exactly one file, the new project's `.env`, after a yes. A risk row records the plain-text token on disk and its mitigations
- US-001.05, UC-001 extensions 2b, 9c and 9d, SSD, OC, SD, DM-001, DM-002, dictionary, DCD-001, DCD-002 and the Project Plan changed to match
- Milestone MIL-005 (9 Go/No-Go criteria, 5 tasks); issues #35 to #39 are synced to Gitea
**Not done:** the PlantUML blocks were not rendered (no PlantUML server is configured; action item in RC-021).
No issue closed: this PR only plans the work.
Refs #35
Refs #36
Refs #37
Refs #38
Refs #39
🤖 Generated with [Claude Code](https://claude.com/claude-code)
- DCD-001 (UC-001): design classes refining DM-001, with class table,
method traceability to OC-001 and SD-001, patterns and dependency check,
and the mapping of each class to src/lib.
- DCD-002: the consolidated project-level model, created from DCD-001.
- SD-001: messages aligned with the DCD method signatures; cites DCD-001.
- Dictionary, registry and traceability matrix updated.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Add objective 9 to the Business Case (and amend objective 6 and success
criterion 1: a token may be written only to the new project's .env after a
yes), US-001.05, UC-001 extensions 2b, 9c and 9d, with the SSD, OC, SD,
DM-001, DM-002 and dictionary in step. Add the classes CredentialCollector,
EnvFileWriter and EnvFile to DCD-001 and DCD-002, and both ends'
multiplicities to every association. Restore three lines of SD-001 damaged
by an earlier edit.
Add milestone MIL-005 (9 Go/No-Go criteria, 5 tasks) and its phase in the
Project Plan. Accept the planning set and the two DCDs; reviews recorded in
RC-020 and RC-021.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Documents only, no code.
1. Design Class Diagrams (RC-021, Go)
src/lib2. MIL-005 plan (RC-020, Go)
.envdoes not provide (GITEA_TOKEN, andGITHUB_PATandGITHUB_USERwhen GitHub is chosen) and, after a yes, creates the new project's own.env: only the needed keys, owner-only, excluded from git, never replaced without a yes.env, after a yes. A risk row records the plain-text token on disk and its mitigationsNot done: the PlantUML blocks were not rendered (no PlantUML server is configured; action item in RC-021).
No issue closed: this PR only plans the work.
Refs #35
Refs #36
Refs #37
Refs #38
Refs #39
🤖 Generated with Claude Code