drop the hive's push of the legacy core/meta repo
Nothing reads core/meta: builds come from internal/meta. Remove push_meta, ensure_meta_remote, meta_read_access, ensure_repo, the per-agent forge sync that only served them, and the git commit path in meta.rs; remove_permission_files now just deletes the seed files.
This commit is contained in:
parent
dd2f0d3ece
commit
b6b568e97e
15 changed files with 81 additions and 518 deletions
|
|
@ -122,9 +122,7 @@ Two things live in the `agent-configs` Forgejo organization:
|
|||
[config-changes.md § Config changes](../agent-lifecycle/config-changes.md#config-changes)).
|
||||
hive-c0re pushes nothing to this org; it only reads from it.
|
||||
Repos stay private, so an agent can't read another
|
||||
agent's config. (Agents remain read-only collaborators on the legacy
|
||||
`core/meta`, the hive's old permission-seed repo.)
|
||||
The agent's **persistent meta flake input** is this repo's `main` head,
|
||||
agent's config. The agent's **persistent meta flake input** is this repo's `main` head,
|
||||
pinned by sha in `internal/meta` (`agent-<n>.url =
|
||||
git+<forge>/agent-configs/<n>.git?rev=<sha>`; see
|
||||
[config-changes.md § Meta flake](../agent-lifecycle/config-changes.md#meta-flake)).
|
||||
|
|
|
|||
Loading…
Reference in a new issue