coulomb/qonto-assistant
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: point at RMASTER-WP-0019 after master prefix rename

Browse source
This commit is contained in:
tegwick 2026-08-14 14:29:19 +02:00
parent 5255077ac4
commit efdf00352a
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
workplans/QONTO-WP-0004-security-hardening-and-scale-to-zero.md
View file

@ -37,7 +37,7 @@ dependencies are tracked explicitly per task rather than assumed away; the
As of Sunday, July 26, 2026, the cross-repo framework direction for that path
is tracked in
`railiance-master/workplans/RAILIANCE-WP-0019-knative-qonto-runtime-on-reef-railiance.md`.
`railiance-master/workplans/RMASTER-WP-0019-knative-qonto-runtime-on-reef-railiance.md`.
Tasks already marked `done` below remain valid as ownership-repo hardening and
migration input; the remaining open tasks are now about handing the runtime
path into `reef-railiance`, `rail-knative`, and `rapp-qonto`.
@ -178,7 +178,7 @@ This task should define, from `qonto-assistant`'s point of view:
- which parts of `docs/SecurityPractice.md` need rewriting now that the target
runtime path is explicit
**Depends on:** `RAILIANCE-WP-0019` defining the cross-repo architecture
**Depends on:** `RMASTER-WP-0019` defining the cross-repo architecture
boundary, plus the future `rail-knative` bootstrap work that will follow from
it.
@ -256,7 +256,7 @@ At minimum, this task must name:
- which current files are migration input only and must stop growing in place
Done when: the extraction and handoff boundary is written; the dependency on
`RAILIANCE-WP-0019` is explicit; and no new direct
`RMASTER-WP-0019` is explicit; and no new direct
`deploy/k8s/qonto-assistant` implementation starts without an explicit
exception note.