302 commits

Author	SHA1	Message	Date
codex	3fb32b2e89	feat(workplan): add CUST-WP-0067 T07 fleet port-map repoint, T08 central MCP ... Remote repointing turned out to be larger than a config change. The port map is prose copied into ~120 AGENTS.md files with no generator behind it, and the Helm chart deploys no MCP server on central, so remote dev-hub exists only as a reverse tunnel to the workstation. Global agent instructions repointed to the in-cluster ClusterIP; the two reverse tunnels stay until T07 and T08 remove what depends on them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-24 22:40:28 +02:00
codex	1da94a207f	chore(workplan): record CUST-WP-0067-T02 local hub retirement ... Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-24 22:30:51 +02:00
codex	bd8f02b785	feat(workplan): rescope CUST-WP-0067 to retire the local hub instance ... Operator decision 2026-08-24: rather than making two hub instances coexist safely, retire the second one. The local postgres+uvicorn instance is what impersonates central and is redundant with ADR-010 decision 3 plus Repo Manager's file-derived index. With it gone, state-hub-primary binds 127.0.0.1:8000 unchanged and every existing default becomes correct with no call-site edits. Adds the cache-only recovery export (44 records) as the T05 source. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-24 22:24:01 +02:00
repo-manager	9dbd1f7ff9	chore(registrar): assign State Hub identifiers	2026-08-24 22:07:01 +02:00
codex	c7d67aba84	feat(workplan): open CUST-WP-0067 hub target resolution ... ADR-010 documented two hub instances sharing port 8000 separated only by IP family; the condition was never remediated. Repo onboarding from the workstation has landed in the local cache since 2026-07-08 — 122 cache repos vs 78 central, a strict subset with 0 central-only records. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-24 22:01:55 +02:00
repo-manager	1f56ce55fe	chore(registrar): assign State Hub identifiers	2026-08-23 14:54:34 +02:00
codex	d113b5c0f1	fix(canon): qualify daily ad-hoc identifiers	2026-08-23 14:45:26 +02:00
codex	ff334f1a40	feat: automate classification convergence	2026-08-23 13:05:47 +02:00
codex	6adafd25b7	workplans: project first owner classification	2026-08-23 12:44:04 +02:00
codex	b641123505	workplans: record registrar compatibility proof	2026-08-23 12:36:21 +02:00
repo-manager	d792318f82	chore(registrar): assign State Hub identifiers	2026-08-23 12:26:59 +02:00
codex	2462abf61d	workplans: record classification projection repair	2026-08-23 11:34:56 +02:00
codex	450b4b80b0	canon: distinguish sector domains from project identity	2026-08-23 01:47:39 +02:00
codex	bd063eb6c3	workplans: record CUST-WP-0065 registrar boundary	2026-08-23 01:33:50 +02:00
codex	b9f3238953	workplans: close stale intakes and start classification migration	2026-08-23 01:31:29 +02:00
codex	f0591bda24	workplans: record bounded scheduled SBOM proof	2026-08-23 00:49:54 +02:00
codex	8a481414ec	workplans: record controlled SBOM canary	2026-08-23 00:29:37 +02:00
codex	d2705f1769	workplans: record controlled SBOM implementation checkpoint ... Assistant: codex	2026-08-23 00:05:56 +02:00
codex	cb62de1b7e	docs: select controlled SBOM source contract ... Assistant: codex	2026-08-22 23:57:53 +02:00
codex	03e28cecf5	workplans: record sbom runtime residuals	2026-08-22 23:06:58 +02:00
repo-manager	9751923028	chore(registrar): assign State Hub identifiers	2026-08-22 22:58:35 +02:00
codex	c1756de260	workplans: close sbom extraction coordination	2026-08-22 22:56:52 +02:00
repo-manager	01e7c7b4e4	chore(registrar): assign State Hub identifiers	2026-08-22 22:38:30 +02:00
codex	8bda6e28b4	canon: resolve work-record governance packets	2026-08-22 22:35:37 +02:00
codex	5331f9af68	chore(consistency): record CUST-WP-0062 hub IDs ... Write back the workplan and task UUIDs from fix-consistency so the sbom-nexus extraction plan stays indexed in WORK-RECORDS.md.	2026-08-18 09:52:20 +02:00
codex	8916515a0c	docs(CUST-WP-0062): extract sbom-nexus and bound daily SBOM catch-up ... Coordinate moving SBOM out of State Hub into sbom-nexus, then replace the weekly stale-repo flood with a daily oldest-N update (default N=3).	2026-08-18 09:49:08 +02:00
codex	780618efbe	docs(canon): define prj- project repository flavor ... Publish project-repository-flavor_v0.1 with naming, GOAL.md (not durable INTENT.md), authority boundary, lifecycle, residuals, and archive rules. Close ADR-005 deferred naming and CUST-WP-0050 D1a; cross-link from the repo classification standard.	2026-08-09 17:24:07 +02:00
codex	97db2a972f	CUST-WP-0061 finished: closure review (6/6 tasks done, same-day) ... Stage 3 delivered end-to-end: intake hub entity (T01), fix-consistency registration (T02), the promotion transition (T03, the actual point of this workplan), generated per-repo index (T04), queue closures retargeted to it (T05), suggestions retired with a real-data migration (T06). All live-verified against the running API/DB, not just tests -- including catching and fixing a real bug in T03 (silent false-success on a missing repo_id). 563 tests green throughout. Carried forward, not blocking: full transclusion rendering (markitect, T04 follow-on), an engagement hub entity (T02's honest deferral), the pre-existing sync_schedules bug found 2026-07-20 (TD f29e49eb, out of scope), and the 10 migrated intake findings needing their actual domain owners to pick them up. The reconciliation that started with AWQ-010 is complete. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-21 01:57:25 +02:00
codex	d55097cd97	CUST-WP-0061-T05: mark done (queue closures retargeted to WORK-RECORDS.md, pushed)	2026-07-21 01:54:51 +02:00
codex	f7c2932e37	CUST-WP-0061-T06: mark done (suggestions retired, migrated, tested, pushed)	2026-07-21 01:52:12 +02:00
codex	7ecc433be9	CUST-WP-0061-T04: mark done (generated index live, tested, pushed)	2026-07-21 01:25:38 +02:00
codex	874ec08c0b	CUST-WP-0061-T03: mark done (promotion transition live, tested, pushed)	2026-07-21 01:06:12 +02:00
codex	12959294dc	CUST-WP-0061-T02: mark done (C-32 registration live, tested, pushed)	2026-07-21 00:48:49 +02:00
codex	67fc4bd7a7	CUST-WP-0061-T01: mark done (intake entity live, tested, pushed)	2026-07-21 00:27:59 +02:00
codex	90477f3f0d	Pause daily-todo-md-stale-review: sole source of the 5 closed Forgejo issues ... Traced the origin of the-custodian issues #1-5 (opened 2026-07-08, all reviewed and closed 2026-07-20): this ActivityDefinition's matched rule always produces a TaskSpec (rules/actions.py::_task_spec_for_rule), and RunActivityWorkflow unconditionally routes TaskSpecs through emit_tasks -> the deployment-wide IssueSink (ISSUE_SINK_TYPE=rest -> issue-core -> Forgejo). It is the fleet's only consumer of the task_template rule action -- confirmed via grep across activity-definitions/. Per current policy (Forgejo issue tracking is not the fleet coordination mechanism), paused rather than left to recreate the same sidetrack daily: enabled: false, status: paused, re-enable path documented in the file (needs a new activity-core report-sink authoring a kind: intake work record instead of an IssueSink task spec). Added as item 6 to CUST-WP-0060's stage-3 successor seed, including the reminder to grep the fleet for any other task_template consumer before stage 3 ships. This is the ADR-001 file-level fix; the live activity-core DB row and Temporal schedule pick it up on the next Railiance-deployed 'make sync-activity-definitions' run -- not something I have credentials or standing to trigger directly from this session. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-20 23:52:54 +02:00
codex	6db7497e07	CUST-WP-0060 finished: closure review + stage-3 seed (7/7 tasks done) ... Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-20 02:11:17 +02:00
codex	5ccf5fcd90	canon drafts + CUST-WP-0060: work-record canonization stages 1-2 ... - canon/standards/work-record-types_v0.1.md (+ machine registry .yaml): work-record umbrella, closed kind registry (workplan/task/intake/ decision/engagement/register-entry), UUIDv7-internal + canonical-name layering, abstract lifecycles incl. intake, promotion as first-class transition, source-anywhere + generated index, tags, budgets, reconciliation loop. status: draft pending ratification - canon/standards/autonomy-lanes_v0.1.md: binky AutonomyPolicy lane model promoted to fleet canon; lane as mandatory spine field; hub-owned time-boxing; attention as WIP-limited workstation. status: draft - workplans/CUST-WP-0060 (hub 4555741c, T01-T07): ratification, terminology v0.2 extension, per-kind schemas, Forgejo CI validation, fix-consistency sidetrack detector (C-25), binky-control pilot with grandfathered ids, stage-3 handoff. Ratification pending as hub decision f4640f9e Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-20 01:54:10 +02:00
codex	435731231a	CUST-WP-0059: finish — T05 verified Forgejo CI + publish ... Green kaizen ci #29 and tag publish #30 (v1.4.0 → Forgejo PyPI 200). Documented substrate/secret fixes and mark workplan finished (6/6).	2026-07-18 18:13:34 +02:00
codex	9b4056bb28	CUST-WP-0059: T06 done (promote doc); T05 de-risked ... Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-16 14:45:57 +02:00
codex	defd85bf7a	chore(consistency): write state-hub ids into CUST-WP-0059 [auto] ... Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-16 14:36:42 +02:00
codex	1a8ba74941	CUST-WP-0059: Forgejo CI/publish cutover — retire residual gitea workflows ... Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-16 10:36:25 +02:00
codex	99f25b6427	chore: archive finished CUST-WP-0057 hub ecosystem consolidation	2026-07-11 01:30:57 +02:00
codex	aab187937b	docs(ecosystem): complete hub stack consolidation (CUST-WP-0057) ... Publish ecosystem architecture, event mapping, capability bridge, and async-base decision docs; add cross-repo regression script; update extraction boundary and bootstrap status; archive WP-0058 touch-ups.	2026-07-11 01:26:53 +02:00
codex	3f94308e2f	CUST-WP-0058: closeout — finished and archived ... All 8 tasks done. Handoffs delivered to fin-hub, core-hub, vergabe-teilnahme, ops-hub, railiance-apps (backup HIGH), NetKingdom. coulomb.social rebuild seeded (docs/coulomb-social-rebuild-seed.md). SCOPE.md Current State updated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-10 10:34:47 +02:00
codex	51e40f1b52	CUST-WP-0058-T07: delivery-lane conformance snapshot — 4 gaps, 1 HIGH ... Lane already live (f95de14 @ vergabe-teilnahme.whywhynot.de). PASS: standalone shape, commit-SHA image, registry, TLS ingress, smoke. FAIL: tenant keying (§1.3), ops-hub registration (§4.1), cnpg backups (§4.2 — missing on ALL four prod DB clusters, railiance-apps alerted), fin-hub cost attribution (§5.1). Evidence bundle under docs/evidence/. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-10 09:28:41 +02:00
codex	e61c7ed15c	CUST-WP-0058: T04 approved, T05 client-hub scoping, T06 fin-hub gap done ... Service contract v0.1 accepted (Bernd 2026-07-10). Client-hub scoped as core-hub extension (client/engagement/app_instance/support_state, CLNT-WP skeleton). fin-hub gap assessment: 5 gaps, FIN-WP-0002 skeleton posted to fin-hub lane (msg 9c8e8ed4); recommendation fin-hub stays reporting-only. Remaining: T07 delivery-lane pilot, T08 closeout. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-10 01:28:57 +02:00
codex	8c838bf38a	CUST-WP-0058-T04: draft business-app service contract v0.1 (proposal) ... Standalone-app shape, instance-per-client tenancy with consolidation-ready data model (DR-1 C), app-local identity with bounded auth module (DR-3 A), build/release evidence, ops-hub and fin-hub obligations, data-protection baseline. Applies to client apps and Binky Hedgehog's own apps alike (DR-2 B client-#1 model). Awaits canon review. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-10 01:17:03 +02:00
codex	5fb5855cbd	CUST-WP-0058: T04/T05 unblocked to todo (DB + file aligned) ... Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-10 01:13:55 +02:00
custodian-sync	9db2461de4	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-10: - CUST-WP-0058-T05: todo → wait	2026-07-10 01:12:46 +02:00
custodian-sync	d0ea0d7820	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-10: - CUST-WP-0058-T04: todo → wait	2026-07-10 01:12:46 +02:00